Skip to content

Commit 51f0304

Browse files
committed
Replace example
1 parent 68ba290 commit 51f0304

File tree

1 file changed

+37
-41
lines changed

1 file changed

+37
-41
lines changed

index.qmd

Lines changed: 37 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -24,43 +24,39 @@ CRM defines abstract types of entities (CRM classes) such as events, measurement
2424

2525
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.
2626

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)
38-
[
39-
a crm:E52_Time-Span ;
40-
crm:P82_at_some_time_within "1912-04-15"^^xsd:date
41-
] ;
42-
# 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.
51-
52-
~~~ttl
53-
<TitanticWreckLocation> a crm:E53_Place ;
54-
crm:P89_falls_within <AtlanticOcean> ;
55-
geo:hasGeometry [ a geo:Geometry ;
56-
geo:asGeoJSON '{"type": "Point","coordinates": [-49.946944,41.7325,-3803]}' ;
57-
geo:asWKT "POINT (-49.946944 41.7325 -3803)" ;
58-
] .
59-
~~~
60-
61-
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)
38+
[
39+
a crm:E52_Time-Span ;
40+
crm:P82_at_some_time_within "1912-04-15"^^xsd:date
41+
] ;
42+
# 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.
47+
48+
~~~ttl
49+
<TitanticWreckLocation> a crm:E53_Place ;
50+
crm:P89_falls_within <AtlanticOcean> ;
51+
geo:hasGeometry [ a geo:Geometry ;
52+
geo:asGeoJSON '{"type": "Point","coordinates": [-49.946944,41.7325,-3803]}' ;
53+
geo:asWKT "POINT (-49.946944 41.7325 -3803)" ;
54+
] .
55+
~~~
56+
57+
GeoSPARQL properties `geo:hasMetricSpatialResolution` and/or `geo:hasSpatialAccuracy` can be used to indicate level of detail.
58+
59+
Instances of [E95 Spacetime Primitive] ... (TODO)
6460

6561
[GeoSPARQL]: https://www.ogc.org/de/publications/standard/geosparql/
6662

@@ -103,10 +99,10 @@ Defintion of instances of [E58 Measurement Unit] should be avoided but either ta
10399
@prefix unit: <http://qudt.org/vocab/unit/> .
104100
@prefix cdt: <https://w3id.org/cdt/> .
105101
106-
<measurement>
107-
crm:P40 observed dimension [
108-
crm:P90_has_value 7 ; crm:P91_has_unit unit:M ; # QUDT unit URI
109-
rdf:value "7 m"^^cdt:ucum # UCUM value
102+
<TitanticSinking>
103+
crm:P191_had_duration [ a crm:E54_Dimension ;
104+
crm:P90_has_value 160 ; crm:P91_has_unit unit:MIN ; # value and QUDT unit
105+
rdf:value "7 min"^^cdt:ucum # UCUM string
110106
] .
111107
~~~
112108

0 commit comments

Comments
 (0)