Financial Regulation Ontology Tutorial chapter two – loading the law

20 Instance details in the resource formWe can introspect all details of “Private Fund Exception” in the Form tab. The top of the window shows path and name of the open OWL file. FinRegOnt sets the prefix as cfr , title and part of the code of federal regulations. The import generates a URI for the instance: cfr :r-0-9. “r” denotes resource. The numbers are generated based on the hierarchy level. We use an import generated URI, because the CFR XML doesn’t come with an ID element. For United States Code we use the element Identifier in the XML. The composite index means that section “§ (m)-1” is the 17th child element under the parent (Part 275). Under composite:child we find section number, subject and paragraphs. We expand paragraph (1) – “Acts solely as an investment adviser to one of more private funds ….” Again, the child elements have a composite index. We use the index number to query the paragraphs in the right order. All text fragments are stored as sxml:TextNode, a generic Semantic-XML class with text and composite index. We use will the index number to concatenate the text fragments into the full text of a paragraph. To use the data warehousing ETL analogy, this is just an Extract of into simple Staging classes. rather than ontology design. There are no semantics and it is hard and error prone to SPARQL query the data. We will transform the staging structure and load into LKIF classes. First we revisit the reference ontology and extend the design. Then we use SPIN rules to move the instances. © Jayzed Data Models Inc. 2016

21 CFR to FRO/LKIF Physical Transform ModelThe Physical Load model shows the source files and target files in the Financial Regulation Ontology. Prerequisite of the Semantic ETL is a mapping from CFR_FDSys_Schema.ttl to the target classes in Code_Federal_Regulations.ttl. The target ontology imports US_Legal_Reference.ttl, an ontology common to CFR and USC and Legal_Reference.ttl, common to international regulations. Legal_Reference.ttl imports LKIF. https://finregont.com/fro/cfr/ https://www.estrellaproject.org/lkif-core Map source classes to target OWL (TTL) RDF/OWL (TTL) Code_Federal_Regulations US_LegalReference LegalReference lkif-extended CFR_FDSys_Schema owl:imports owl:imports Transform complex structures We create a target instance ontology file for very staging file. E.g. FRO_CFR_Title12_part_275.ttl for CFR-2012-title17-vol-3-part275.ttl The target files only contain class and property instances. They all import the common schema, Code_Federal_Regulations.ttl RDF/OWL (TTL) OWL (TTL) CFR-2015-title12-vol2-part217 CFR-2015-title12-vol3-part225 CFR-2013-title12-vol4-part252 CFR-2012-title17-vol3-part275 FRO_CFR_Title_12_Part_217 FRO_CFR_Title_12_Part_225 FRO_CFR_Title_12_Part_252 FRO_CFR_Title_17_Part_275 Execute Load from source to target instance © Jayzed Data Models Inc. 2016

22 Identifying and extending the LKIF target for CFRWe extend the model of the US Legal Context, described in previous slides to accommodate the CFR elements. Slide SEC Mandate in context defined the SEC as a LKIF Executive Body and Financial Regulation as an outcome of its Rulemaking. fro-cfr:CodeFederalRegulations is a subclass of Financial Regulation. CFR_Component is a collection class for all CFR element classes. The top class, CFR_Title is also member of the Document Edition, described in Codification of the Law in the ontology. The object property fro-leg-ref:divides creates the hierarchy of CFR_Components. Paragraphs divide the Sections. Section divides the Part. Part divides the Chapter and finally Chapter divides the Title. We create a class restriction: CFR_Paragraph divides some CFR_Section Next pages show, how to transform the staging data and load into LKIF classes. First we look at ETL in the Semantic world. How to use SPARQL and TopBraid SPIN 2 rules to move the instances. © Jayzed Data Models Inc. 2016

23 Mapping Rules in SPARQLThe CONTRUCT statement is the equivalent of the INSERT in a relational database. We use SPARQL CONTRUCT statements to load the data into our target classes. “The CONSTRUCT query form returns an RDF graph. The graph is built based on a template which is used to generate RDF triples based on the results of matching the graph pattern of the query.” (W3C SPARQL Query Language for RDF) CONSTRUCT { ?targetInstance fro-cfr:hasParagraphText ?text . } WHERE { ?this composite:child ?text_node . ?text_node a sxml:TextNode . ?text_node sxml:text ?text . BIND (spinmap:targetResource(?this, cfr-context-spin:P-CFR_Parapraph) AS ?targetInstance) . The example creates triples (an RDF graph) for the hasParagraphText property. We have two variables: ?targetInstance of our destination fro-cfr:CFR_Paragraph ?text The actual text that we and to construct for the CFR_Paragraph instance. The WHERE clause specifies the result set from our Source ontology classes. This is similar to SQL “INSERT … AS SELECT”. ?this is a special variable that refers to the current instance of this class that is being evaluated by the inference rule. For every instance of our source “cfr-fdsys-s:P” we navigate to “sxml:TextNote” and assign the “sxml:text” property to our ?text variable. The BIND keyword assigns the value of an expression to a variable. In this case, we call a function to convert the URI of ?this to the target URI. Jayzed Data Models © 2016

24 SPIN – SPARQL Inferencing NotationWith TopBraid Composer as ontology editor, we use SPARQL Inference Notation, SPIN to define mapping rules. “SPIN is a W3C Member Submission that has become the de-facto industry standard to represent SPARQL rules and constraints on Semantic Web models. SPIN also provides meta-modeling capabilities that allow users to define their own SPARQL functions and query templates. Finally, SPIN includes a ready to use library of common functions.” (http://spinrdf.org/ ) “SPINMap is a SPARQL-based language to represent mappings between RDF/OWL ontologies. These mappings can be used to transform instances of source classes into instances of target classes.”3 There are no mapping spreadsheets or proprietary ETL files. The mapping file is in Ontology Web Language. That means, we can query target schema and data joined with the mapping to their source. Source Target CFR-2012-title17-vol-3-part275 FRO_CFR_Title_17_Part_275 owl:imports owl:imports Mapping file (TTL) CFR17_275spinFRO We create a new RDF/SPIN mapping file, CFR17_275spinFRO.ttl in TopBraid Composer. The mapping file imports the required SPIN MAP elements, to support mapping rules and editor. Next we import the source ontology, CFR-2012-title-17-vol-3-part275.ttl and target, FRO_CFR_Title_17_Part_275.ttl Now we have visibility of source and target classes in our mapping ontology. We invoke the mapping editor. Jayzed Data Models © 2016

25 SPIN – SPARQL Inferencing NotationWith TopBraid Composer as ontology editor, we use SPARQL Inference Notation, SPIN to define mapping rules. The diagram shows the CFR Paragraph mapping from staging, cfr-fdsys-s:P to target fro-cfr:CFR_Paragraph: We connect the two classes with a “change namespace” mapping rule. For every source instance, this will create a target instance with the URI namespace The second rule copies data property composite:index to the target fro-leg-ref:hasSequenceNumber. The mapping contexts for CFR Paragraph, Section and Note are stored as an instance of spinmap:Context. Jayzed Data Models © 2016

26 SPIN mapping context connecting classesConnecting a source to a target class invokes the mapping rule dialog. The Target Function specifies how to create the target URI. For CFR Paragraph we simply change the namespace. The Preview window shows how source instances are converted to target URI. The Result column shows the prefix fro-cfr-t17-p275 and instances r , r The SPARQL Expression is the WHERE clause for the CONSTRUCT statement. The first BIND extracts the local name (right of the colon) of the source URI. The second BIND concatenates the local Name to the target namespace. © Jayzed Data Models Inc. 2016

27 SPIN rules populating properties (1)Once defined, the mapping context will be used to populate data and object properties. The spinmap-rules can be examined and customized at the source class’ Form tab. The inference engine (reasoner) will trigger the rules for every instance of the class. The rules “Map into” the mapping context with a “derive” rule: Derive the target fro-leg-ref:hasSequenceNumber from source composite:index, cast the value to xsd:integer. Likewise spin-rules show at the source class’ Form tab. Spin-rules are free form SPARQL that we the inference engine to execute. In this case we want to CONSTRUCT the fro-cfr:hasParagraphText data property. The WHERE clause navigates from the ?this instance to the sxml:TextNode. The BIND statement assigns the target instance using the Mapping Context. © Jayzed Data Models Inc. 2016

28 SPIN rules populating properties (2)Templates facilitate reuse of common SPARQL rule statements. All FinRegOnt instances have an object property to point to their source instance: fro-leg-ref:hasSourceInstance. The CONSTRUCT sets the domain target instance and ?this variable range. The WHERE clause assigns the ?targetInstance variable. The first BIND extracts the local name (right of the colon) of the source URI. The second BIND concatenates the local Name to the target namespace. © Jayzed Data Models Inc. 2016

29 Running the Inference EngineThe inference engine executes SPIN-rule alongside standard reasoning. An inference engine is a software able to infer new facts from a set of asserted facts and rules. Non-ontology Inference engines are also to derive decision based on business rules (rules engine). The reasoner generalizes the concept with a richer, ontology based semantic. Input Asserted Triples are facts in the included staging file CFR-2012-title17-vol-3-part275.ttl. The TopSPIN (SPARQL Rules) are in the mapping file: CFR17_275spinFRO.ttl We run the engine from the TopBraid composer Menu or Button. The engine iterates trough standard reasoning for class subsumption. That is to infer that an instance must be type of a class based on its asserted properties. Chapter I of the tutorial touched how the defined class drives the reasoner. Chapter III will explain the central role of reasoning for financial compliance. The TopSPIN engine will also execute the SPIN rules. The status window shows rule “STEP001: set Paragraph Text” on cfr-fdsys-s:P For all instances of cfr-fdys:P the engine will execute the SPARQL and CONSTRUCT output triples. The iteration (7) means that this is the seventh pass of the engine. As configured the reasoner will iterate until there are no more new triple inferred. © Jayzed Data Models Inc. 2016

30 Inferencing Output TriplesThe Inferences tab shows the output triples in three columns, subject, predicate, and object. We scroll down the Subject column fro-cfr-t17-p275:r , the Private Fund Adviser paragraph and Look at Predicate column for object and data properties of the paragraph: Object Property hasSourceInstance, links to the CFR FDSys original (Object column). Paragraph text is sub property of Component Text. The engine infers a triple for the component text. It has a sequence number: 3 It has a text: “Acts solely ….” The paragraph is a fro-cfr:CFR_Paragraph © Jayzed Data Models Inc. 2016

31 Validating target instance – class browserOnce the inferencing is complete, the class browser will indicate the number of triples next to the Code of Federal Regulations Classes. This is the first consistency check. The number of target instances should match the number of elements in the CFR XML. Title 17 Part 275 has 2 Chapters, 44 Sections, 757 paragraphs and 16 Notes. We select CFR_Section and the instances tab shows the individual sections. Scope: FinRegOnt does not import everything from the CFR XML source. For our purpose of Legal Reasoning, we are interested in the text and structure of the regulation. The lowest level is the paragraph or note that we want to link via object properties to a Legal Expression. We do not need the XML table of contents and formatting. However, the hasSourceInstance property links to the source instance, where all details remain available for querying. © Jayzed Data Models Inc. 2016

32 Validating target instances – Resource FormThe Resource Form displays all details of a class instance. This is the next step in checking consistency of the rule output. We double click on Section 17, § (m)-1 in resource list to launch the resource from. The class instance has a citation, [76 FR 39703, July6, 2011]. Note that SECTION has a SPIN-rule to populate the citation from its composite:child cfr-fdsys-s:CITA. The section number § (m)-1 , populated from cfr-fdsys-s:SECTNO The section subject “Private fund adviser exemption, populated from cfr-fdsys-s:SUBJECT Section 17 is divided_by many paragraphs (only 3 are displayed here). A rule on SECTION constructs from SECTION composite:child with type of cfr-fdsys-s:P The section divides Part 275 of the Code of Federal Regulations. The construct is static, because there is only one CFR Part in our source XML. The component name is parent property of section subject. Siblings are Part text, Volume text, Chapter text and Title text. This facilitates queries across CFR Components. The value is inferred automatically. We do not need a rule. A rule sets the source instance to the original cfr-fdsys-s:SECTION resource. Section 17 has a note. The object property fro-leg-ref:refers_toNote links to the fro-cfr:CFR_Note instance. The FinRegOnt documentation has definitions for all classes and properties on the website: © Jayzed Data Models Inc. 2016

33 Validating target instances – the GraphThe Semantic Data Management provides complete traceability and linage. Everything is a triple. We can navigate and query data instance, Section § (m)-1 to Source, Mapping and Reference Data. We start with the Section fro-cfr-t17-p275:r-1-17, “Private fund adviser exemption”. The object property fro-leg-ref:divides navigates to the higher CFR components, Part, Chapter and Title. Regulation instance fro-cfr:CFR_Title-17 has object properties to the Reference Data. Title 17 is a lkif-mereo:member_of the CFR edition. lkif-mereo:bears the Securities & Exchange Commission expression of the regulation. The two anchor points let us query all information described in the Legislative Contact. Reference Data: Links to Legislative environment Source: Section and Paragraph Imported GPO XML file Regulation instances: Section data imported from the Source ontology The section instance has the object property fro-leg-ref:has SourceInstance pointing to its original Section. With it we can join to all imported CFR FDSys classes and properties. The rdf:type of the section instance is spinmap:targetClass for the mapping. From here we navigate to the spinmap:sourceClass. Mapping: CFR context has the mapping © Jayzed Data Models Inc. 2016

34 Querying the meta data We can query the graph joining our section with reference-, source, and mapping data. SPARQL query The query traverses the complete meta-data graph, starting with the section. Variables “?” and object properties perform the joins. Query Result Set The query is a star “*”, so all query variables show in the result set. The query can be customized to include more or even all sections. (modify or omit the BIND statement). Because everything is a triple within the ontology, we have a whole meta-data repository at hand. SELECT * WHERE { BIND (fro-cfr-t17-p275:r-1-17 AS ?froSection) . #reference data ?froSection fro-leg-ref:divides ?froPart . ?froPart fro-leg-ref:divides ?froChapter . ?froChapter fro-leg-ref:divides ?froTitle . ?froTitle lkif-expr:bears ?definitionalExpression . ?froTitle lkif-mereo:member_of ?edition . # source ?froSection fro-leg-ref:hasSourceInstance ?source . ?source composite:child ?cfrNumber . ?cfrNumber a cfr-fdsys-s:SECTNO . # mapping ?froSection a ?froTargetClass . ?spinContext spinmap:targetClass ?froTargetClass . ?spinContext spinmap:sourceClass ?cfrSourceClass } [froSection] fro-cfr-t17-p275:r-1-17 froPart fro-cfr:CFR_Title-17_Part-275 froChapter fro-cfr:CFR_Title-17_Chapter-2 froTitle fro-cfr:CFR_Title-17 definitionalExpression fro-leg-ref:Definitional_Expression_US_AdvisorRegulation edition fro-cfr:CFR_Annual_Edition_2016_Title_17 source

cfrNumber

§ (m)-1

froTargetClass fro-cfr:CFR_Section spinContext cfr-context-spin:SECTION-CFR_Section cfrSourceClass cfr-fdsys-s:SECTION © Jayzed Data Models Inc. 2016

35 Asserting the mapped triplesThe populated FRO instances are still inferences. To make them permanent, we assert them to the target file. Dynamic/volatile Data should be inferred at runtime An ontology that needs the populated sections and paragraphs can simply import the mapping file. That means the mapping rules will be executed every time we invoke the reasoner. This is desired for volatile information. The triples are temporary and ‘lost’ when we close the file. Dynamic strategies keep the target ontology in sync with the source. The cost is computing time of the inference engine. For CFR we assert the triples to a new file: FRO_CFR_Title_12_Part_275.tll All ontology environments have routines to export inferences, results to a new graph. A challenge is to separate wanted from unwanted inferences. See our earlier example, fro-cfr-t17-p275:r , the Private Fund Adviser paragraph: We only want the rules output, new FRO class instances and their properties. We do not want derived inferences, like subsumption to parent classes and properties. They should be inferred in the target ontology, because the target schema may change. For the Financial Regulation Ontology, we explicitly move triples using SPARQL Motion. Static and slowly changing data should be asserted For data that does not change often, we don’t want to spent reasoner time. This pertains to static reference data, transactions, and history. The reasoner does not have to re-compute the transformation rules. The triples are permanent. This means that changes to the source are not reflected in the target ontology automatically. Jayzed Data Models © 2016

36 SPARQL Motion – scripting language“SPARQLMotion is an RDF-based scripting language with a graphical notation to describe data processing pipelines.”3 CONSTRUCT { ?section a fro-cfr:CFR_Section . } WHERE { “The basic idea of SPARQLMotion is that individual processing steps can be connected, so that the output of one step is used as input to the next. RDF graphs are the basic data structure that is passed between the steps, but named variables pointing to RDF nodes and XML documents can also be passed between steps. The behavior of each module is typically driven by SPARQL queries, for example to iterate through result sets, to construct new RDF triples and to perform updates to RDF data sources.” SPARQL Motion is quite powerful and flexible – similar to ETL environments. The diagram shows a subset of the script to load the CFR rule inferences. Input for the script is an import of the CFR mapping file with inferences. RDF Processing elements are SPARQL CONSTRUCT statements that operate on the input triples. For example: CONSTRUCT { ?section a fro-cfr:CFR_Section .} WHERE { ?section a fro-cfr:CFR_Section The constructed triples become input for the next step. The final Export step specifies to write the output to FRO_CFR_Title_17_Part275.ttl © Jayzed Data Models Inc. 2016

37 Querying the Code of Federal RegulationsThe CFR “everything query” contains the main Code of Federal Regulations classes and data properties. We use the query to validate the data import for FRO resource files. The select joins the section with Reference data Section sequence number, source instance and subject. Section Notes and Citation Paragraph sequence number and text and enumeration text. We sort by section sequence than paragraph sequence. The query selects (almost) everything in FRO related to the Code of Federal Regulations. Besides validation, we run the query to export data into csv/MS-Excel format. Query file and Excel are in the website directory: SELECT * WHERE { ?edition fro-leg-ref:hasEditionText ?edition_text . ?edition lkif-mereo:member ?title . ?title fro-leg-ref:hasTitleText ?title_text . ?chapter fro-cfr:hasChapterText ?chapter_text . ?part fro-leg-ref:divides ?chapter . ?part fro-cfr:hasPartText ?part_text . ?section fro-leg-ref:divides ?part ; fro-leg-ref:hasSequenceNumber ?sectionSequence ; fro-cfr:hasSectionNumber ?sectionNumber ; fro-leg-ref:hasSourceInstance ?section_source ; fro-cfr:hasSectionSubject ?sectionSubject . OPTIONAL {?section fro-cfr:hasSectionCitation ?sectionCitation . } OPTIONAL { ?section fro-leg-ref:refers_toNote ?note . ?note a fro-cfr:CFR_Note . ?note fro-cfr:hasNoteText ?note_text . } ?para fro-leg-ref:divides ?section ; fro-leg-ref:hasSequenceNumber ?paraIndex ; fro-leg-ref:hasSourceInstance ?para_source ; fro-cfr:hasParagraphText ?paraText . OPTIONAL {?para fro-cfr:hasParagraphEnumText ?paraEnumText} } ORDER BY ?sectionSequence ?paraSequence © Jayzed Data Models Inc. 2016

38 CFR Section § 275.203(m)-1 query resultsThis is an excerpt of the query output Excel spreadsheet, filtered for section sequence number 17. We hide technical column to focus on the regulation content. Below section information is the same for all 1035 record. To the right, we see the Paragraphs. This query reconstitutes the text of the regulation as it is in the GPO PDF download. This concludes the tutorial on loading the Code of Federal Regulations. The United States Code is next. paraEnumText paraText United States investment advisers. (a) For purposes of section 203(m) of the Act (15 U.S.C. 80b-3(m)), an investment adviser with its principal office and place of business in the United States is exempt from the requirement to register under section 203 of the Act if the investment adviser: (1) Acts solely as an investment adviser to one or more qualifying private funds; and (2) Manages private fund assets of less than $150 million. Non-United States investment advisers. (b)For purposes of section 203(m) of the Act (15 U.S.C. 80b-3(m)), an investment adviser with its principal office and place of business outside of the United States is exempt from the requirement to register under section 203 of the Act if: (1) The investment adviser has no client that is a United States person except for one or more qualifying private funds; and (2) All assets managed by the investment adviser at a place of business in the United States are solely attributable to private fund assets, the total value of which is less than $150 million. Frequency of Calculations. (c)For purposes of this section, calculate private fund assets annually, in accordance with General Instruction 15 to Form ADV (§ of this chapter). Definitions. (d)For purposes of this section: Assets under management -1 means the regulatory assets under management as determined under Item 5.F of Form ADV (§ of this chapter). Place of business (2)has the same meaning as in § (a). Principal office and place of business (3)of an investment adviser means the executive office of the investment adviser from which the officers, partners, or managers of the investment adviser direct, control, and coordinate the activities of the investment adviser. Private fund assets (4)means the investment adviser's assets under management attributable to a qualifying private fund. Qualifying private fund -5 means any private fund that is not registered under section 8 of the Investment Company Act of 1940 (15 U.S.C. 80a-8) and has not elected to be treated as a business development company pursuant to section 54 of that Act (15 U.S.C. 80a-53). For purposes of this section, an investment adviser may treat as a private fund an issuer that qualifies for an exclusion from the definition of an “investment company,” as defined in section 3 of the Investment Company Act of 1940 (15 U.S.C. 80a-3), in addition to those provided by section 3(c)(1) or 3(c)(7) of that Act (15 U.S.C. 80a-3(c)(1) or 15 U.S.C. 80a-3(c)(7)), provided that the investment adviser treats the issuer as a private fund under the Act (15 U.S.C. 80b) and the rules thereunder for all purposes. Related person (6)has the same meaning as in § (4)-2(d)(7). United States (7)has the same meaning as in § (l) of this chapter. United States person -8 means any person that is a U.S. person as defined in § (k) of this chapter, except that any discretionary account or similar account that is held for the benefit of a United States person by a dealer or other professional fiduciary is a United States person if the dealer or professional fiduciary is a related person of the investment adviser relying on this section and is not organized, incorporated, or (if an individual) resident in the United States. part_text Part RULES AND REGULATIONS, INVESTMENT ADVISERS ACT OF 1940 sectionSequence 17 sectionNumber § (m)-1 sectionSubject Private fund adviser exemption. sectionCitation [76 FR 39703, July 6, 2011] note_text A client will not be considered a United States person if the client was not a United States person at the time of becoming a client. © Jayzed Data Models Inc. 2016

39 United States Code - Physical Load ModelThe USC Lead Model mirrors the CFR steps, however the structure of the law is more complex than regulations. There are many more components and variations in the hierarchy. https://finregont.com/fro/usc/ XSD Import XML Schema Export RDF graph Strip generic classes RDF/OWL (TTL) USLM USC_USLM_Schema xsi:schemaLocation owl:imports XML RDF/OWL (TTL) Open as Semantic XML Document Export RDF Graph Import CFR_FDSys Strip schema elements usc12_17 usc12_53 usc15_2D USC-2015-title12-chapter17 USC-2015-title12-chapter53 USC-2015-title15-chapter2D The Office of the Law Revision Council provides one XML file per USC Title (usc12.xml, usc15.xml). FRO only needs individual chapters - not the whole title. We used XMLSpy to spit the XML into chapter files. The XSD is called United States Legislative Model (USLM). We adopt the abbreviation for FinRegOnt staging schema. © Jayzed Data Models Inc. 2016

40 Understanding the USC XML headerThe USC header contains version, the schema include, and metadata about the document. The import into Financial Regulation Ontology Staging retains this information, but we only need selected elements for LKIF/FRO. The only XMLSpy edit to the was to remove chapters that we don’t need. The section has the document title, number. Publisher is the Office of the Law Revision Council (OLRC). The Publication name refers to the OLRC release point The files is as of The document body starts with the

tag. Just like in CFR, top-level component is the Title. The id field (see title and note) provides a unique identifier for all components. , that we will use to construct the URIs in FinRegOnt. Title 15 USCTitle 15 OLRC T08:37:20 USCConverter 1.1

<num value="15">Title 15—</num> <heading>COMMERCE AND TRADE</heading> <note topic="miscellaneous" id="idcfab2c6a-0c74-11e6-aa53-e455a13f2ad9"> Current through © Jayzed Data Models Inc. 2016 41 Understanding the USC XML main structureThe USC main structure has more levels and content elements than CFR. Our Private Fund Manager Exception is contained in a Subsection of 15 U.S. Code § 80b–3. The XML has a rich set of formatting styles and a table of contents. Both is not needed in FRO for our purpose of Legal Reasoning and we don’t import them. They remain available in the staging RDF. We do import: id The unique element identifier identifier The human readable index of the element heading The name/title of the element. Section § 80b–3, breaks down into 14 subsections. Subsection b/1 defines exception to the registration requirement. The chapeau is an introductory text for the following lower levels. In this case a heading for the 7 paragraphs. Finally the content element contains the text. <section style="-uslm-lc:I80" id="idd04f5b5e-0c74-11e6-aa53-e455a13f2ad9" identifier="/us/usc/t15/s80b–3"> <num value="80b–3">§ 80b–3.</num> <heading> Registration of investment advisers</heading> <subsection style="-uslm-lc:I19" class="indent2 firstIndent-2" id="idd04f5b5f-0c74-11e6-aa53-e455a13f2ad9“ identifier="/us/usc/t15/s80b–3/a"> </subsection> … id="idd04f5b60-0c74-11e6-aa53-e455a13f2ad9" identifier="/us/usc/t15/s80b–3/b"> <num value="b" class="bold">(b)</num> <heading class="bold"> Investment advisers who need not be registered</heading> <chapeau>The provisions of subsection (a) shall not apply to—</chapeau> <paragraph style="-uslm-lc:I12" class="indent1" id="idd04f5b61-0c74-11e6-aa53-e455a13f2ad9" identifier="/us/usc/t15/s80b–3/b/1"> <num value="1">(1)</num> <content> any investment adviser, other than an investment adviser who acts as an investment adviser to any private fund, all of whose clients are residents of the State within which such investment adviser maintains his or its principal office and place of business, and who does not furnish advice or issue analyses or reports with respect to securities listed or admitted to unlisted trading privileges on any national securities exchange;</content> </paragraph> © Jayzed Data Models Inc. 2016 42 Imported USC USLM classes & propertiesThe ontology browser shows USC-2015-title15-chapter2D.ttl Classes and Properties. The XML header elements, creator, publisher, title, and type have been imported as classes with the “dc:” prefix. The namespace refers to the Dublin Core resource metadata standard. We create the namespace “uslm” (=United States Legislative Model, showing left of the colon on the classes/properties). We use a collection class, USC_USLM_Schema as a superclass for all USLM classes. More than 10,000 instances have been created. The properties list starts with object property composite:child/parent and the index - just like the CFR import. © Jayzed Data Models Inc. 2016 43 Comparing the USC USLM § 80b–3 graphThe diagram shows the instance graph for the Private Fund Exemption XML. The instance box text starts with the class name, for example “<uslm:section “. The connecting arrows, object property instances of composite:child show the hierarchy from Section via Subsection to Paragraph. Section and Subsection have a heading, “Registration of Investment Advisers”. The “num” instance, child of section has numbering text § 80b–3. Section also shows the Source Credit and a Note. The Subsection also has a Num and Heading “Investment Advisers who need not to be registered”. The Chapeau “Provisions of subsection (a) shall not apply to …” precedes the list of paragraphs. Paragraphs have a Num value and content. The Num value helps to list the exceptions in the right order. Content can be a simple text or more complex structure as we shall see on transformation and query slides. © Jayzed Data Models Inc. 2016 44 USC USLM Section § 80b–3 form detailsA double click on the section instance invokes the details dialog. The instance is a uslm:section. The uslm:id-section is a unique identifier coming with the OLRC XML. We will use this ID to generate the FinRegOnt URL. The uslm:identifier-section is the human readable ID. It is structured as an index into the United States Code. We ignore the uslm:style-section. The formatting can be retrieved from FinRegOnt Staging via the SourceInstance property. The import generates the composite:index. As in CFR it sorts child elements with the same parent instance. I.e. our section is the 4th child of parent chapter instance. The composite:child part shows all elements under our section. The uslm:num value is the human readable “number” of the element, § 80b–3. The heading is a short name/text for the element, “Registration of investment advisers. Next children are all subsections. (CFR doesn’t have subsections). We expand subsection “b”. Just like sections, subsections have type, id, identifier, style and composite index. The composite:child part shows num value and heading. The uslm:chapeau is an introductory text for the following sub-elements, the paragraphs. The Subsection uslm:paragraph contain the text of Private Fund exemptions to the registration requirement. © Jayzed Data Models Inc. 2016 45 USC to FRO/LKIF Physical Transform ModelThe Physical Load model is similar to CFR. The target ontology schema is United_States_Code.ttl. We map the staging classes from USC_USLM_Schema.ttl to the target classes in United_States_Code.ttl. The target ontology imports US_Legal_Reference.ttl, Legal_Reference.ttl and lkif-extended.ttl. The imported LKIF, Legal Reference and US Legal Reference files are the same for law and regulations. https://finregont.com/fro/usc/ https://www.estrellaproject.org/lkif-core Map source classes to target OWL (TTL) RDF/OWL (TTL) United_States_Code US_LegalReference LegalReference lkif-extended USC_USLM_Schema owl:imports owl:imports Transform complex structures We create a target FRO instance ontology file for very staging file. The design challenge for the FRO USC target ontology lies in the complexity of the USLM structure. For example: What elements can have a USLM Paragraph? Where do Clause and Sub clause appear? What elements are composite child of Section? RDF/OWL (TTL) OWL (TTL) USC-2015-title12-chapter17 USC-2015-title12-chapter53 USC-2015-title15-chapter2D FRO_USC_Title_12_Chapter17 FRO_USC_Title_12_Chapter53 FRO_USC_Title_15_Chapter2D Execute Load from source to target instance © Jayzed Data Models Inc. 2016 46 Analyzing the populated USC structure.To answer questions about the USC structure we query and pivot population of classes and the composite:child relationship. The SPARQL SELECT returns Parent, Child class and the number of instances. The first line in the WHERE clause populates all 10,261 instances of the composite:child object property into ?parent and ?child variables. The next two lines navigate to the ?parent_class and ?child_class. The last line in the WHERE clause limits the result-set to subclasses of our USLM collection class, uslm:uscDoc. We GROUP the results BY parent and child class. We run the query against the Investor Adviser Act staging ontology, USC-2015-title15-chapter2D.ttl The result set show: 3 chapeaus have a note 10 chapeaus have a date element. 45 chapeaus have a reference This analysis drives how we design the FRO class for chapeau. For instance, we can put an OWL restriction on chapeau and the parent classes. The actual population will also drive the validation query. The next slide shows an MS Excel pivot of the complete result set. The top row shows the USLM parent classes. The left column has the child classes Cells contain the number of relationship per pair. SELECT ?parent_class ?child_class (COUNT(*) AS ?instances) WHERE { ?parent composite:child ?child . ?parent a ?parent_class . ?child a ?child_class . ?parent_class rdfs:subClassOf uslm:uscDoc . ?child_class rdfs:subClassOf uslm:uscDoc . } GROUP BY ?parent_class ?child_class © Jayzed Data Models Inc. 2016 47 USC USLM Title 15, Chapter 2D element pivotSum of total Parent Child chapeau chapter clause column content continuation header heading inline item layout main meta note notes p paragraph proviso quotedContent section sourceCredit subchapter subclause subparagraph subsection title toc tocItem uscDoc Grand Total 14 59 8 1 42 85 209 126 6 597 603 111 4 427 23 39 218 175 997 10 5 38 date 2 263 7 233 558 docNumber docPublicationName 289 84 93 50 809 i 3 21 24 56 19 9 309 82 num 514 40 295 1358 271 685 956 17 483 25 ref 45 367 197 11 1278 20 644 2566 92 36 261 286 sup 230 62 540 234 993 1595 1355 696 878 97 709 1351 10261 © Jayzed Data Models Inc. 2016 48 Extending LKIF Norm-Statute for USC USLMJumping ahead, the class and property browser show the outcome of our LKIF extensions. The next pages will explain the design and population. Refer to the documentation for definitions of classes and properties: Financial Regulation Ontology classes have the prefix fro-usc. The United States Code is a LKIF Statute. Both Statute and Regulation are LKIF Legal Documents* rolling up to Medium. The fro-usc:USC_Component is collection class for Level and Text entities. 11 USC_Level classes establish the hierarchy via the fro-leg-ref:divides object property. 4 USC_Text Element classes extend or annotate components via the fro-leg-ref:refers_to property, a subPropertyOf of lkif-mereo:part_of. USLM Schema and User Guide available on the OLRC website (http://uscode.house.gov/download/download.shtml) and the pivot table is in the FinRegOnt query directory. They define the requirements for the design. For each USLM element we considered: Major elements have a semantic importance indicated in the USLM documentation or have sufficient number of instances. They become USC Components. The distinction between Level and Text is structural in the XML Source. USC Level elements have and Identifier, the human readable index. USC Text Elements do not have an ID. Minor elements have population of < than 10 instances. Denormalized into data and/or object properties. Examples are the Notes collection and Content class. Out of scope for FRO. We do not need table of content and formatting attributes. We skipped some elements with low population and unclear USLM definitions. * Europe’s Alternative Investment Managers Directive (AIFMD) is a lkif-norm:Directive © Jayzed Data Models Inc. 2016 49 FRO USC class graph (1) Title to SubsectionThe United States Code hierarchy is more complicated than the Code of Federal Regulations. The graph shows the USC levels from Title to Subsection. USC Subchapter divides the Chapter, which in turn divides the Title. However, both Chapter and Subchapter can have Sections. Therefore the class restriction on USC_Section states OR. fro-leg-ref:divides some (fro-usc:USC_Chapter or fro-usc:USC_Subchapter) The Restriction refers to a UNION (or) of the classes. fro-usc:USC_Chapter or fro-usc:USC_Subchapter The UNION is a list of entities “[]”, referencing to Chapter and Subchapter. We read the graph as follows: Section divides Chapters or Subchapters. The Section can be broken down further into Subsections. The Subsection divides the Section (nothing else here). © Jayzed Data Models Inc. 2016 50 FRO USC class graph (2) Section to SubparagraphThe lower elements in the USC hierarchy follow the same pattern. Both Section and Subsection can have Paragraphs. The Paragraph divides a Section or a Subsection. Paragraphs can be further broken down into Subparagraphs. The Subparagraph divides a Paragraph. © Jayzed Data Models Inc. 2016 51 FRO USC class graph (3) leaf level elementsThe lowest level hierarchy elements are Clause, Subclause and Item. The Clause is a text, usually preceded with a lower case roman numeral. Subsection and Subparagraph can contain clauses. The Subclause divides a Clause or a Paragraph. The Item is a text fragment in a list, such as a numbered or bullet point list. Both Clause and Subclause may contain Items. This completes the USC hierarchy in the Financial Regulation Ontology. The FRO USC Text Elements, Chapeau, Continuation, Note and Quoted Content are not dividing the hierarchy. They are text elements that annotate any type of USC Level element. FRO does not define class restriction on them. We continue with transformations to populate our target ontology. © Jayzed Data Models Inc. 2016 52 Mapping the USLM schema to FRO-USCThe steps defining the rules to transform USLM instance data and load into USC are similar to CFR mapping. Create a new RDF/SPIN mapping file USC_15_2DspinFRO.ttl Import the source and target ontologies: USC-2015-title15-chapter2D.ttl and FRO_USC_Tile_12_Chapter_2D.ttl Define a mapping context for each of the 15 FRO target classes in the Mapping Editor. Connect data properties for simple 1:1 population. Create SPIN-rules for complex data and object property transformations Validate the results with introspection and queries. To map the Paragraph we pull source and target class into the mapping editor. Then we connect the classes to invoke the Context dialog. For CFR our context was change namespace, but for USC we want to build the URI from the USLM ID. © Jayzed Data Models Inc. 2016 53 Create the class mapping contextThe dialog shows the selected mapping function, argument, template, a preview of results and the SPARQL expression. The Preview Results list box shows the target URIs - a concatenation of the namespace, prefix fro-usc and the value of the USLM ID data property. The Target function, buildURI1 takes one argument. The other buildURI functions operate with multiple arguments, as in a composed key. We use the default template, fro-usc:(?1). The variable, “?1” is a placeholder for the first argument. The SPARQL expression returns the target IRI. The first BIND assigns the value based ?source, an instance of uslm:Paragraph and the name of the data property. The Second BIND calls the SPIN function to constructs a URI based on template and argument. © Jayzed Data Models Inc. 2016 54 USC USLM mapping context GraphThe mapping context is stored as an instance of spinmap:Context. The mapping diagram is the graph of context instances with their source and target class. (We only display 5 of the 15 contexts here). We locate spinmap:Context in the class browser and click on the instance tab. We select an instance and choose the Graph tab in the upper window. This will populate the graph with an instance. For example: usc-15-2D-spin:paragraph-USC_Paragraph. We expand the graph for source class and target class. This will populate ulsm:paragraph and fro-usc:USC_Paragraph. We can expand the class for rdfs:subClassOf to display uslm:uscDoc and fro-usc:USC_Level. © Jayzed Data Models Inc. 2016 55 USC USLM mapping context queryUnderstanding the graph, we formulate a simple SPARQL to display the mapping information. The query selects all spinmap:Context with their source and target classes. SELECT ?source_class ?context ?target_class WHERE { ?context a spinmap:Context ; spinmap:sourceClass ?source_class ; spinmap:targetClass ?target_class . } [source_class] context target_class uslm:chapeau usc-15-2D-spin:chapeau-USC_Chapeau fro-usc:USC_Chapeau uslm:chapter usc-15-2D-spin:chapter-USC_Chapter fro-usc:USC_Chapter uslm:clause usc-15-2D-spin:clause-USC_Clause fro-usc:USC_Clause uslm: continuation usc-15-2D-spin:continuation-USC_Continuation fro-usc:USC_Continuation uslm:item usc-15-2D-spin:item-USC_Item fro-usc:USC_Item uslm:note usc-15-2D-spin:note-USC_Note fro-usc:USC_Note uslm:paragraph usc-15-2D-spin:paragraph-USC_Paragraph fro-usc:USC_Paragraph uslm:quotedContent usc-15-2D-spin:quotedContent-USC_QuotedContent fro-usc:USC_QuotedContent uslm:section usc-15-2D-spin:section-USC_Section fro-usc:USC_Section uslm:sourceCredit usc-15-2D-spin:sourceCredit-USC_SourceCredit fro-usc:USC_SourceCredit uslm:subchapter usc-15-2D-spin:subchapter-USC_Subchapter fro-usc:USC_Subchapter uslm:subclause usc-15-2D-spin:subclause-USC_Subclause fro-usc:USC_Subclause uslm:subparagraph usc-15-2D-spin:subparagraph-USC_Subparagraph fro-usc:USC_Subparagraph uslm:subsection usc-15-2D-spin:subsection-USC_Subsection fro-usc:USC_Subsection uslm:title usc-15-2D-spin:title-USC_Title fro-usc:USC_Title Everything is within the ontology. Everything is a triple. © Jayzed Data Models Inc. 2016 56 Transformations for USC ParagraphWe run the inference engine and take a look at the populated instance for the Investment Adviser exemption paragraph. This is the record populated from the § 80b–3 XML we examined earlier. The USC_Paragraph class has 6 data properties: fro-leg-ref:SequenceNumber: 3 Direct copy of the source value in composite:index fro-usc:hasId: idd04f5b61-0c74-11e6-aa53-e455a13f2ad9 Direct copy from uslm:id-paragraph fro-usc:hasIdentifierText: /us/usc/t15/s80b–3/b/1 Direct copy from uslm:identifier-paragraph fro-usc:hasNumberText: (1) Custom Spin function to denormalize the uslm:num class instance into a data property fro-leg-ref:hasComponentText: “any investment adviser, other than …” This is not an ETL rule. Fro-usc:hasContentText is rdfs:subPropertyOf this data property. Population is an automatic inference. fro-usc:hasContentText: “any investment adviser, other than …” Custom SPIN-rule to denormalize the uslm:content class instance into a data property. Object Properties: fro-leg-ref:hasSourceInstance: “<uslm:paragraph style="-uslm-lc:I12" identifier="/us/usc/t15/s80b–3/b/1" id="idd04f5b61-0c74-11e6-aa53-e455a13f2ad9" ...> Custom SPIN function to set the source instance to ?this. (see CFR SPIN rule) for-leg-ref:divides: idd04f5b60-0c74-11e6-aa53-e455a13f2ad9 The URI of the section that hold the Paragraph. A custom SPIN rule. © Jayzed Data Models Inc. 2016 57 Using SPARQL templates for common transformationsFor data properties common across USC FRO classes, we use a template rule rather than duplicating the SPARQL code. All USC_Component instances have a source instance and heading. All USC_Level instances have a data property for the number in the index. The SPARQL CONSTRUCTs only vary by the name of the USLM source class. We can pass the class name as an argument to a SPIN template. The snippet shows the rules, SetHeading, SetNumberText and SetSourceInstance for uslm:paragraph in the class form. We take a close look at SetNumberText. The template has a single Argument spl:predicate, an rdf:Property. At the bottom of the rule we see uslm:id-paragraph passed to the spl:predicate. At execution the template statement line ?this ?predicate ?SourceId . Will be replaced with the passed argument: ?this uslm:id-paragraph ?SourceId . And we can construct the ?targetInstance with the USC identifier. © Jayzed Data Models Inc. 2016 58 Paragraph transformations content textThe USLM Paragraph is a generic structure. A query for the paragraph text sometimes involves several nested instances and variation. FinRegOnt denormalizes into straight forward data and object properties, where appropriate. The custom SPIN rule is attached to the source class uslm:paragraph. It will be executed for every instance of the class. (see CFR SPIN rules populating properties). The CONSTRUCT shows the triple. The target (fro-usc) paragraph content text property will be populated with a “full text”. The WHERE clause starts joining (any) child of the paragraph into a variable. A challenge with the USLM paragraph structure is that content text is either directly under uslm:content nested within a uslm:P structure. The OPTIONAL segments explore both possibilities and call a custom SPIN function to concatenate the text. We end up with either ?content_full_text or ?p_full_text bound. The FILTER statements makes sure that ?full_text as a value. (some paragraphs don’t have a text. Finally, we bind ?targetPara to the ?this variable. The spinmap:targetResource function uses the paragraph mapping context. # set Complex Type Text CONSTRUCT { ?targetPara fro-usc:hasContentText ?full_text . } WHERE { ?this composite:child ?complex_type . OPTIONAL { ?complex_type a uslm:content . BIND (usc-15-2D-spin:getUSLMComplexTypeText(?complex_type) AS ?content_full_text) . } . ?complex_type composite:child ?p . ?p a uslm:p . BIND (usc-15-2D-spin:getUSLMComplexTypeText(?p) AS ?p_full_text) . BIND (IF(bound(?content_full_text), ?content_full_text, ?p_full_text) AS ?full_text) . FILTER bound(?full_text) . BIND (spinmap:targetResource(?this, usc-15-2D-spin:paragraph-USC_Paragraph) AS ?targetPara) . © Jayzed Data Models Inc. 2016 59 Concatenating complex text structuresThe previous Paragraph transformation rule called a custom function to build the text. The function usc-15-2D-spin:getUSLMComplexTypeText takes a uslm:content or uslm:p instance as an argument and returns the text. USLM contains both content of the law and formatting. The XML reflect this having a text block broken down into small fragments of text nodes, references, dates, iterations and inline elements. Financial Regulation Ontology is only interested in the semantic. That is human readable smallest fragment of the law, that we connect to a Legal Reasoning rule. Hence, FinRegOnt concatenates the text fragments into a string data property. Other transformation rules retain the references, uslm:ref and resolve them into object property links. For example: If a reference (="/us/usc/t15/s80b–3”) points to a section, FinRegOnt populates the object property fro-leg-ref:refers_to with the URI. The function’s query has three nested selects. The innermost query selects the text of the text of the different class instances under ?complex_type. The next SELECT layer performs a GROUP CONCAT of the result set. The outmost query FILTERs to ensure that ?full_text is bound and casts the value to xsd:string. SELECT ?full_text_str WHERE { { SELECT ?complex_type ((GROUP_CONCAT(?complex_text)) AS ?full_text) SELECT ?complex_type ?complex_text ?complex_type composite:child ?complex_child . ?complex_child composite:index ?child_index . OPTIONAL { ?complex_child a sxml:TextNode . ?complex_child sxml:text ?complex_text . } . ?complex_child a uslm:ref . ?complex_child composite:child ?ref_text_node . ?ref_text_node sxml:text ?complex_text . ?complex_child a uslm:date . ?complex_child composite:child ?date_text_node . ?date_text_node sxml:text ?complex_text . ?complex_child a uslm:i . ?complex_child composite:child ?i_text_node . ?i_text_node sxml:text ?complex_text . ?complex_child a uslm:inline . FILTER bound(?complex_text) . } ORDER BY (rdfs:Resource("child_index"^^xsd:string)) GROUP BY ?complex_type ORDER BY (rdfs:Resource("complex_type"^^xsd:string)) FILTER (bound(?full_text) && (str(?full_text) != "")) . BIND (spif:cast(?full_text, xsd:string, xsd:string, xsd:string) AS ?full_text_str) . © Jayzed Data Models Inc. 2016 60 Rules for paragraph object properties.The main object properties linking FRO USC instances are fro-leg-ref:divides and fro-leg-ref:refers_to. The rule pattern is to query the composite:child structure and CONTRUCT the target. The rule CONSTRUCT sets the divided by object property for the Section of the Paragraph. The WHERE clause joins (any) Subject with a child of ?this. We test the populated variable for being a uslm:section. (Remember that paragraphs can also occur under Subsections.) Finally, we BIND target section and paragraph using the mapping context. # set paragraph divides (Section) CONSTRUCT { ?targetSection fro-leg-ref:divided_by ?targetPara . } WHERE { ?section composite:child ?this . ?section a uslm:section . BIND (spinmap:targetResource(?section, usc-15-2D-spin:chapeau-USC_Chapeau) AS ?targetSection) . BIND (spinmap:targetResource(?this, usc-15-2D-spin:paragraph-USC_Paragraph) AS ?targetPara) . The second example follows the same pattern. We want check, if the paragraph has a chapeau and set it. The CONSTRUCT sets the refers to Chapeau object property for the paragraph. (if it has a chapeau). The WHERE clause joins composite:child of the paragraph, ?this. We test, if the child is a uslm:chapeau and BIND target chapeau and paragraph via the mapping context. # set reference to Chapeau CONSTRUCT { ?targetPara fro-usc:refers_toChapeau ?targetChapeau . } WHERE { ?this composite:child ?chapeau . ?chapeau a uslm:chapeau . BIND (spinmap:targetResource(?chapeau, usc-15-2D-spin:chapeau-USC_Chapeau) AS ?targetChapeau) . BIND (spinmap:targetResource(?this, usc-15-2D-spin:paragraph-USC_Paragraph) AS ?targetPara) . © Jayzed Data Models Inc. 2016 61 USC Inferencing and validationRunning the inference engine to populates FRO USC following the same steps as explained for CFR inferencing. The screenshot shows the class browser with number of instances and the list of inference triples, scrolled for our paragraph. There are 1985 USC_Component instances. Initial validation follows the same steps as for FRO CFR: Compare instance counts to the USCUSLM data source ontology. Examine sample class instances in the Resource Form. Draw and explore the graph for the Private Fund Exception. Follow the hierarchy up to section and chapter. Expand chapeau and notes associated with the level elements. As for CFR we make the triples persistent in the target ontology file. The file is available on the FinRegOnt website: FRO_USC_Title_15_Chapter_2D.ttl We won’t repeat these steps here, but rather drill deeper into data and metadata queries on the United States Code. © Jayzed Data Models Inc. 2016 62 United States Code: “everything query”The query SELECTs all USC instances and properties. This is to validate target population comprehensively. The SPARQL statement is quite long (115 lines) and execution may take a few minutes. The screenshot is a zoom-out of the Excel result set (70 columns and 160,000 rows). We use the zoom-out to eyeball consistency. Any blank row should be investigated: There is a break in the population or the query There is a valid reason that the particular USC chapter doesn’t have the particular field(s). The website query directory contains various queries and result sets for CFR and USC chapters in Excel format. The following pages show sections of the “everything query” as standalone SELECTS and results sets. © Jayzed Data Models Inc. 2016 63 USC query: Title to SubchapterThe query SELECTs all USC instances and properties. We show the SPARQL and samples of the result set. The WHERE clause for title and chapter is straightforward. The OPTIONAL ensures that ?subchapter is bound, dividing either chapter or subchapter. # USC query header information Title to Subchapter SELECT DISTINCT ?title_seq ?title_ident ?title_heading ?title_number ?chapter ?chapter_seq ?chapter_ident ?chapter_heading ?chapter_number ?subchapter ?subchapter_seq ?subchapter_ident ?subchapter_heading ?subchapter_number WHERE { # Title properties ?title a fro-usc:USC_Title ; fro-leg-ref:hasSequenceNumber ?title_seq ; fro-usc:hasIdentifierText ?title_ident ; fro-usc:hasHeading ?title_heading ; fro-usc:hasNumberText ?title_number . # Chapter properties ?title fro-leg-ref:divided_by ?chapter . ?chapter fro-leg-ref:hasSequenceNumber ?chapter_seq ; fro-usc:hasIdentifierText ?chapter_ident ; fro-usc:hasHeading ?chapter_heading ; fro-usc:hasNumberText ?chapter_number . # Some Titles do not have a subchapter. The Sections are directly underneath the Chapter # Subchapter properties OPTIONAL { ?chapter fro-leg-ref:divided_by ?subchapter . ?subchapter a fro-usc:USC_Subchapter ; fro-leg-ref:hasSequenceNumber ?subchapter_seq ; fro-usc:hasIdentifierText ?subchapter_ident ; fro-usc:hasHeading ?subchapter_heading ; fro-usc:hasNumberText ?subchapter_number ; fro-leg-ref:divided_by ?section . } title_seq title_ident /us/usc/t15 title_heading COMMERCE AND TRADE title_number Title 15— chapter <http://finregont.com/fro/usc/FRO_USC_Title_15_Chapter_2D.ttl#idd039fe6a-0c74-11e6-aa53-e455a13f2ad9> chapter_seq 4 chapter_ident /us/usc/t15/ch2D chapter_heading INVESTMENT COMPANIES AND ADVISERS chapter_number CHAPTER 2D— subchapter <http://finregont.com/fro/usc/FRO_USC_Title_15_Chapter_2D.ttl#idd04f5b18-0c74-11e6-aa53-e455a13f2ad9> subchapter_seq 3 subchapter_ident /us/usc/t15/ch2D/schII subchapter_heading INVESTMENT ADVISERS subchapter_number SUBCHAPTER II— © Jayzed Data Models Inc. 2016 64 USC query: Investment Advisers, SectionsThe query SELECTs all Sections under Subchapter II – INVESTMENT ADVISERS section_ident section_heading section_number /us/usc/t15/s80b–1 Findings § 80b–1. /us/usc/t15/s80b–10 Disclosure of information by Commission § 80b–10. /us/usc/t15/s80b–10a Consultation § 80b–10a. /us/usc/t15/s80b–11 Rules, regulations, and orders of Commission § 80b–11. /us/usc/t15/s80b–12 Hearings § 80b–12. /us/usc/t15/s80b–13 Court review of orders § 80b–13. /us/usc/t15/s80b–14 Jurisdiction of offenses and suits § 80b–14. /us/usc/t15/s80b–15 Validity of contracts § 80b–15. /us/usc/t15/s80b–16 Omitted § 80b–16. /us/usc/t15/s80b–17 Penalties § 80b–17. /us/usc/t15/s80b–18 Hiring and leasing authority of Commission § 80b–18. /us/usc/t15/s80b–18a State regulation of investment advisers § 80b–18a. /us/usc/t15/s80b–18b Custody of client accounts § 80b–18b. /us/usc/t15/s80b–18c Rule of construction relating to the Commodities Exchange Act § 80b–18c. /us/usc/t15/s80b–19 Separability § 80b–19. /us/usc/t15/s80b–2 Definitions § 80b–2. /us/usc/t15/s80b–20 Short title § 80b–20. /us/usc/t15/s80b–21 Effective date § 80b–21. /us/usc/t15/s80b–3 Registration of investment advisers § 80b–3. /us/usc/t15/s80b–3a State and Federal responsibilities § 80b–3a. /us/usc/t15/s80b–4 Reports by investment advisers § 80b–4. /us/usc/t15/s80b–4a Prevention of misuse of nonpublic information § 80b–4a. /us/usc/t15/s80b–5 Investment advisory contracts § 80b–5. /us/usc/t15/s80b–6 Prohibited transactions by investment advisers § 80b–6. /us/usc/t15/s80b–6a Exemptions § 80b–6a. /us/usc/t15/s80b–7 Material misstatements § 80b–7. /us/usc/t15/s80b–8 General prohibitions § 80b–8. /us/usc/t15/s80b–9 Enforcement of subchapter § 80b–9. We select instances of type FRO USC Subchapter where the heading matches our search criteria. And join Sections that divide the Subchapter. The result set lists identifier, heading and section number, including the Registration of investment Advisers that we examined before. We will continue to navigate down to the Private Fund Exemption in the next query # USC query INVESTMENT ADVISERS, Sections SELECT * WHERE { ?subchapter a fro-usc:USC_Subchapter . ?subchapter fro-usc:hasHeading "INVESTMENT ADVISERS" . ?subchapter fro-usc:hasHeading ?subchapter_heading . ?subchapter fro-leg-ref:divided_by ?section . # Section properties ?section a fro-usc:USC_Section ; fro-leg-ref:hasSequenceNumber ?section_seq ; fro-usc:hasIdentifierText ?section_ident ; fro-usc:hasHeading ?section_heading ; fro-usc:hasNumberText ?section_number . } ORDER BY ?section_ident © Jayzed Data Models Inc. 2016 65 USC query: Registration SubsectionThe query SELECTs all Subsections under Section § 80b–3 -Registration of investment advisers. Filter criteria is the section number, "§ 80b–3. The paragraph text (OPTIONAL) is blank for sections that have text only in the underlying paragraphs. The sections have a subsection as we will see in the next query. ident subsection_heading # Subsection_text /us/usc/t15/s80b–3/a Necessity of registration (a) Except as provided in subsection (b) and section 80b–3a of this title , it shall be unlawful … /us/usc/t15/s80b–3/b Investment advisers who need not be registered (b) /us/usc/t15/s80b–3/c Procedure for registration; filing of application; effective date of registration; amendment of registration (c) /us/usc/t15/s80b–3/d Other acts prohibited by subchapter (d) Any provision of this subchapter (other than subsection (a) of this section) which prohibits … /us/usc/t15/s80b–3/e Censure, denial, or suspension of registration; notice and hearing (e) /us/usc/t15/s80b–3/f Bar or suspension from association with investment adviser; notice and hearing (f) The Commission, by order, shall censure or place limitations on the activities of any person … /us/usc/t15/s80b–3/g Registration of successor to business of investment adviser (g) Any successor to the business of an investment adviser registered under this section shall be … /us/usc/t15/s80b–3/h Withdrawal of registration (h) Any person registered under this section may, upon such terms and conditions as the Commission finds … /us/usc/t15/s80b–3/i Money penalties in administrative proceedings (i) /us/usc/t15/s80b–3/j Authority to enter order requiring accounting and disgorgement (j) In any proceeding in which the Commission may impose a penalty under this section, … /us/usc/t15/s80b–3/k Cease-and-desist proceedings (k) /us/usc/t15/s80b–3/l Exemption of venture capital fund advisers (l) /us/usc/t15/s80b–3/m Exemption of and reporting by certain private fund advisers (m) /us/usc/t15/s80b–3/n Registration and examination of mid-sized private fund advisers (n) In prescribing regulations to carry out the requirements of this section with respect to investment advisers acting as … # USC Query - section 80-b3 Registration subsections SELECT * WHERE { ?section a fro-usc:USC_Section . ?section fro-usc:hasNumberText ?section_number . ?section fro-usc:hasNumberText "§ 80b–3." . # Subsection properties - (not every section has a subsection) OPTIONAL { ?section fro-leg-ref:divided_by ?subsection . ?subsection a fro-usc:USC_Subsection . ?subsection fro-leg-ref:hasSequenceNumber ?subsection_seq ; fro-usc:hasIdentifierText ?subsection_ident ; fro-usc:hasHeading ?subsection_heading ; fro-usc:hasNumberText ?subsection_number . OPTIONAL { ?subsection fro-usc:hasContentText ?subsection_text . } } ORDER BY ?subsection_number © Jayzed Data Models Inc. 2016 66 USC query: Registration SubsectionThe query SELECTs all Paragraphs under Subsection § 80b–3/b - Registration Exemption SELECT * WHERE { ?subsection a fro-usc:USC_Subsection . ?subsection fro-usc:hasIdentifierText "/us/usc/t15/s80b–3/b" . ?subsection fro-leg-ref:divided_by ?subsection_para . ?subsection_para a fro-usc:USC_Paragraph . ?subsection_para fro-leg-ref:hasSequenceNumber ?subsection_para_seq . ?subsection_para fro-usc:hasIdentifierText ?subsection_para_ident . OPTIONAL {?subsection_para fro-usc:hasHeading ?subsection_para_heading . } ?subsection_para fro-usc:hasNumberText ?subsection_para_number . OPTIONAL {?subsection_para fro-usc:hasContentText ?subsection_para_text .} } ORDER BY ?subsection_para_number Finally, we drilled down from Title 15 all the way to the Investment Adviser Registration exemption. The piece of USC OLCR XML that we started with. Note that paragraphs 5,7 and don’t have a text, because they have content in Subparagraphs. subsection_para_ident subsection_para_number subsection_para_text /us/usc/t15/s80b–3/b/1 (1) any investment adviser, other than an investment adviser who acts as an investment adviser to any private fund, all of whose clients are residents of the State within which such investment adviser maintains his or its principal office and place of business, and who does not furnish advice or issue analyses or reports with respect to securities listed or admitted to unlisted trading privileges on any national securities exchange; /us/usc/t15/s80b–3/b/2 (2) any investment adviser whose only clients are insurance companies; /us/usc/t15/s80b–3/b/3 (4) any investment adviser that is a foreign private adviser; /us/usc/t15/s80b–3/b/4 (5) /us/usc/t15/s80b–3/b/5 (6) any plan described in section 414(e) of title 26 , any person or entity eligible to establish and maintain such a plan under title 26, or any trustee, director, officer, or employee of or volunteer for any such plan or person, if such person or entity, acting in such capacity, provides investment advice exclusively to, or with respect to, any plan, person, or entity or any company, account, or fund that is excluded from the definition of an investment company under section 80a–3(c)(14) of this title ; /us/usc/t15/s80b–3/b/6 (7) /us/usc/t15/s80b–3/b/7 (8) © Jayzed Data Models Inc. 2016 67 Summary and conclusionCode of Federal Regulations and the United States Code are LKIF Legal Documents: Statute and Regulation. The legislative context for laws & regulations consists of actors (LKIF Public Bodies and Public Acts), and Public Acts ( lawmaking, rulemaking, codification and publication). LKIF expression ties the Public Act to the Legal Document. Government publishers provide the laws and regulations in XML format. Extract and convert the source file into FRO RDF Staging. Transform the RDF representation into FRO ontology with semantic mapping and Inference Rules. Load the inference triples into the target FRO ontology. The result is a standard Legal Ontology (LKIF) with FRO extensions populated with the full text of Finance Laws and Regulations. The Semantic Web approach has everything within the ontology and available for SPARQL query: Requirements, Schema, Data, Linage to source, and Mapping. © Jayzed Data Models Inc. 2016 68 Chapter II – books, recommended companion readingData Integration Blueprint and Modeling Anthony David Giordano IBM Press, 2011 Law and the Semantic Web: Legal Ontologies, Methodologies, Legal Information Retrieval, and Applications Richard Benjamins, Pompeu Casanovas, Joost Breuker, Aldo Gangemi Springer, 2009 Model Driven Engineering and Ontology Development Dragan Gasevic, Dragan Djuric, Vladan Devedzic Springer, 2010 Legal Ontology Engineering Nuria Casellas Springer, 2011 © Jayzed Data Models Inc. 2016 69 Chapter II - referencesFinancial Regulation Ontology Tutorial (online PowerPoint and softcopies): Documentation: SPARQL queries and result sets in Excel: Source Files (OWL-turtle): Subdirectories CFR, USC and REF TopBraid Composer Maestro website: TopQuadrant, SPIN SPARQL Inferencing Notation: TopQuadrant, SPINMap ontology mapping: graphical-notation/ W3C, Recommendation: SPARQL Query Language for RDF: SPIN – SPARQL Inferencing Notation website: SPARQL Motion website: © Jayzed Data Models Inc. 2016 70 FRO Chapter III – Legal ReasoningChapter 3 will be added to FinRegOnt.com as a separate deck in November. © Jayzed Data Models Inc. 2016 </div> </div> </div> </div> </div> </div> </div> <script src='https://www.google.com/recaptcha/api.js'></script>  <div class="modal fade" id="login" tabindex="-1" role="dialog" aria-labelledby="myModalLabel"> <div class="modal-dialog" role="document"> <div class="modal-content"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-label="Close" on="tap:login.close">×</button> <h3 class="modal-title">Sign In</h3> </div> <div class="modal-body"> <form action="https://slidepptx.com/login" method="post"> <div class="form-group form-group-lg"> <label class="sr-only" for="email">Email</label> <input class="form-input form-control" type="text" name="email" id="email" value="" placeholder="Email" /> </div> <div class="form-group form-group-lg"> <label class="sr-only" for="password">Password</label> <input class="form-input form-control" type="password" name="password" id="password" value="" placeholder="Password" /> </div> <div class="form-group form-group-lg"> <div class="checkbox"> <label class="form-checkbox"> <input type="checkbox" name="remember" value="1" /> Remember Password </label> <label class="pull-right"><a href="https://slidepptx.com/forgot">Forgot Password?</a></label> </div> </div> <button class="btn btn-lg btn-primary btn-block" type="submit">Sign In</button> </form> <hr style="margin-top: 15px;" /> <a href="https://slidepptx.com/login/google" class="btn btn-lg btn-google btn-block"> Login with Google</a> </div> </div> </div> </div>  <div class="footer-container" style="background: #fff;display: block;padding: 10px 0 20px 0;margin-top: 30px;"> <div class="footer-container-inner"> <footer id="footer" class="container"> <div class="row"> <div class="bottom-footer"> <div class="container"> Copyright © 2025 SLIDEPPTX.COM. All rights reserved. </div> <hr /> </div> </div> <div class="row">  <section class="block col-md-4 col-xs-12 col-sm-3" id="block_various_links_footer"> <h4>Information</h4> <ul class="toggle-footer" style=""> <li><a href="https://slidepptx.com/about">About Us</a></li> <li><a href="https://slidepptx.com/privacy">Privacy Policy</a></li> <li><a href="https://slidepptx.com/term">Terms and Conditions</a></li> <li><a href="https://slidepptx.com/copyright">Copyright</a></li> <li><a href="https://slidepptx.com/contact">Contact Us</a></li> </ul> </section>  <section id="social_block" class="col-md-4 col-xs-12 col-sm-3 block"> <h4>Follow us</h4> <ul> <li class="facebook"> <a target="_blank" href="" title="Facebook"> Facebook </a> </li> <li class="twitter"> <a target="_blank" href="" title="Twitter"> Twitter </a> </li> <li class="google-plus"> <a target="_blank" href="" title="Google Plus"> Google Plus </a> </li> </ul> </section>  <div id="newsletter" class="col-md-4 col-xs-12 col-sm-3 block"> <h4>Newsletter</h4> <div class="block_content"> <form action="https://slidepptx.com/newsletter" method="post"> <div class="form-group"> <input id="newsletter-input" type="text" name="email" size="18" placeholder="Entrer Email" /> <button type="submit" name="submit_newsletter" class="btn btn-default"> </button> <input type="hidden" name="action" value="0"> </div> </form> </div> </div>  </div> </footer> </div> </div>  <script> $(function () { $("#document_search").autocomplete({ source: function (request, response) { $.ajax({ url: "https://slidepptx.com/suggest", dataType: "json", data: { term: request.term }, success: function (data) { response(data); } }); }, autoFill: true, select: function (event, ui) { $(this).val(ui.item.value); $(this).parents("form").submit(); } }); }); $(document).ready(function() { $(".doc-share-btn").click(function() { var urlshare = $(this).attr('data-share-url'); window.open('http://www.facebook.com/sharer.php?u=' + urlshare, '_blank'); }); }); function download_submit() { $('#download_form').submit(); } </script> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-106734935-2', 'auto'); ga('send', 'pageview'); </script> </body> </html>

Financial Regulation Ontology Tutorial chapter two – loading the law

Recommend Documents