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: index.qmd
+37-41Lines changed: 37 additions & 41 deletions
Original file line number
Diff line number
Diff line change
@@ -24,43 +24,39 @@ CRM defines abstract types of entities (CRM classes) such as events, measurement
24
24
25
25
The CRM classes [E61 Time Primitive], [E94 Space Primitive], and [E95 Spacetime Primitive] are both subclasses of [E59 Primitive Value] and of [E41 Appellation], so the latter can be used when a mapping to established RDF data types is not applicable.
26
26
27
-
- instances of [E61 Time Primitive] and [E52 Time-Span] eare expressed as RDF literals of type `xsd:date`, `xsd:time`, `xsd:dateTime`, or `xsd:dateTimeStamp` if applicable. More complex time values should be expressed using the [Extended Date/Time Format (EDTF)](https://www.loc.gov/standards/datetime/) but there is no established method to calculate with EDTF in RDF yet.^[See <https://periodo.github.io/edtf-ontology/> for a draft.] CRM includes its own classes and properties to model more complex temporal values so this has not been decided yet.
28
-
29
-
~~~ttl
30
-
@prefix edtf: <http://id.loc.gov/datatypes/edtf/>
31
-
@prefix unit: <http://qudt.org/vocab/unit/> .
32
-
33
-
<TitanticSinking> a crm:E81_Transformation ;
34
-
crm:P124_transformed <RMSTitanic> ;
35
-
crm:P123_resulted_in <TitanticWreck> .
36
-
crm:P4_has_time-span
37
-
"1912-04-15"^^xsd:date , # or ^^edtf:EDTF (subsumes xsd:date)
# TODO: add exact time of sinking (02:38–05:18 GMT)
43
-
crm:P191_had_duration [
44
-
crm:P90_has_value 160 ;
45
-
crm:P91_has_unit unit:MIN
46
-
]
47
-
.
48
-
~~~
49
-
50
-
- instances of [E94 Space Primitive] should be expressed using [GeoSPARQL] Ontology as instance of `geo:hasGeometry`, compatible with various geographic data formats (WKT, GeoJSON, GML...).^[See also CRM Geo draft at <http://www.cidoc-crm.org/extensions/crmgeo/>, defining superclasses of `geo:Geometry`.] CRM Property [P168 place is defined by] should be expressed with RDF property `geo:hasGeometry`. CRM Properties [P171 at some place within], and [P172 contains] can be used as RDF properties to link places ([E53 Place]) to outer and inner geometries but `geo:hasBoundingBox` and `geo:hasCentroid` should be preferred, if applicable.
GeoSPARQL properties `geo:hasMetricSpatialResolution` and/or `geo:hasSpatialAccuracy` can be used to indicate level of detail.
62
-
63
-
- instances of [E95 Spacetime Primitive] ... (TODO)
27
+
Instances of **[E61 Time Primitive] and [E52 Time-Span]** are better expressed as RDF literals of type `xsd:date`, `xsd:time`, `xsd:dateTime`, or `xsd:dateTimeStamp` if applicable. More complex time values should be expressed using the [Extended Date/Time Format (EDTF)](https://www.loc.gov/standards/datetime/) but there is no established method to calculate with EDTF in RDF yet.^[See <https://periodo.github.io/edtf-ontology/> for a draft.] CRM includes its own classes and properties to model more complex temporal values so this has not been decided yet.
28
+
29
+
~~~ttl
30
+
@prefix edtf: <http://id.loc.gov/datatypes/edtf/>
31
+
@prefix unit: <http://qudt.org/vocab/unit/> .
32
+
33
+
<TitanticSinking> a crm:E81_Transformation ;
34
+
crm:P124_transformed <RMSTitanic> ;
35
+
crm:P123_resulted_in <TitanticWreck> .
36
+
crm:P4_has_time-span
37
+
"1912-04-15"^^xsd:date , # or ^^edtf:EDTF (subsumes xsd:date)
# TODO: add exact time of sinking (02:38–05:18 GMT)
43
+
.
44
+
~~~
45
+
46
+
Instances of **[E94 Space Primitive]** should be expressed using [GeoSPARQL] Ontology as instance of `geo:hasGeometry`, compatible with various geographic data formats (WKT, GeoJSON, GML...).^[See also CRM Geo draft at <http://www.cidoc-crm.org/extensions/crmgeo/>, defining superclasses of `geo:Geometry`.] CRM Property [P168 place is defined by] should be expressed with RDF property `geo:hasGeometry`. CRM Properties [P171 at some place within], and [P172 contains] can be used as RDF properties to link places ([E53 Place]) to outer and inner geometries but `geo:hasBoundingBox` and `geo:hasCentroid` should be preferred, if applicable.
0 commit comments