You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: IG Core/IGLayersCodingGuidelines.txt
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -34,21 +34,23 @@ Where component-level combinations exist (e.g., eat and drink) within a given st
34
34
35
35
Logical relationships cannot only be used to capture relationships between the same component types, but also to link components hierarchically (e.g., objects and object properties, or properties and sub properties). Ensure to select the corresponding relationship type when linking individual components (e.g., 'Child-to-Parent Relationship').
36
36
37
-
Specific component types allow further specific annotations (e.g., Context Taxonomy, Regulative Functions, Constitutive Functions) discussed as part of the general coding guidelines for IG 2.0 (see URL above).
37
+
Specific component types allow further specific annotations (e.g., Context Taxonomy, Regulative Functions, Constitutive Functions) discussed as part of the general coding guidelines for IG 2.0 (see URL above). Entities can further be annotated as animate, inanimate, and abstract or concrete.
38
38
39
39
Where components of a given institutional statement are implicit or exist outside an institutional statement, indicate those in the 'IG Institutional Statement' layer as part of statement-level annotation.
40
40
41
-
Specific considerations for complex data structures or policy references that coders may find embedded in institutional statement components are highlighted in the following.
41
+
Specific considerations for complex data structures, collections, equations, or policy references that coders may find embedded in institutional statement components are highlighted in the following.
42
42
43
-
Complex data structures:
44
-
------------------------
43
+
Complex data structures, Collections & Equations:
44
+
-------------------------------------------------
45
45
46
46
Where individual components contain complex regular structures (e.g., lists, or quantitative information), those can be decomposed using the 'IG Collection' layer and the 'IG Complex Data Structure' layer, respectively. The purpose is to make commonly found textual structures machine-readable.
47
47
48
-
The 'IG Collection' layer identifies elements in lists (e.g., item1 AND item2, etc.) or other logical relationships (e.g., item1 AND item2 XOR item3, etc.). It is further possible to indicate precedence amongst the relationships, and further indicate whether the listing is exhaustive.
48
+
The 'IG Collection' layer identifies elements in lists (e.g., item1 AND item2, etc.) or other logical relationships (e.g., item1 AND item2 XOR item3, etc.). It is further possible to indicate precedence amongst the relationships, and further indicate whether the listing is exhaustive. Elements identify in the collection can further be annotated as abstract or concrete, as well as indicating embedded institutional statements.
49
49
50
50
The 'IG Complex Data Structure' layer allows for the decomposition of elementary values (e.g., items in a list) in an extensible schema building on the base structure QUALIFIER, COMPARATOR, QUANTITY, UNIT, OBJECT, OBJECT PROPERTY (components can be omitted where suitable). Example: "a bit (qualifier) more than (comparator) 10 (quantity) tons (unit) high-quality (object property) building material (object)"
51
51
52
+
The 'IG Equation' layer allows the specification of equation components (e.g., left-hand side, right-hand side) and their relationship (by drawing links between both equation sides). Alternatively, an entire expression as inferred from textual form, can be explicitly provided.
0 commit comments