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
+24-18Lines changed: 24 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ CRM defines abstract types of entities (CRM classes) such as events, measurement
22
22
23
23
- instances of [E60 Number](http://www.cidoc-crm.org/cidoc-crm/E60) are expressed as RDF literals with numeric data type such as `xsd:integer`
24
24
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.
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](#e41-appelation) can be used when a mapping to established RDF data types is not applicable.
26
26
27
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 dates in RDF yet.^[See discussion to extend SPARQL [for simple dates](https://github.com/w3c/sparql-dev/blob/main/SEP/SEP-0002/sep-0002.md) and [EDTF in RDF](https://periodo.github.io/edtf-ontology/).] CRM includes its own classes and properties to model more complex temporal values so this has not been decided yet.
CRM class [E32 Authority Document] and CRM property [P71 lists] should not be used in RDF but corresponding SKOS RDF classes `skos:ConceptScheme` and `skos:inScheme`. Applications may define `skos:ConceptScheme` as subclass of [E31 Document] and `skos:inScheme` as subproperty of [P67 refers to] if needed.
@@ -83,13 +74,6 @@ CRM also defines class [E55 Type] with properties [P127 has broader term] and [P
83
74
[P127i has narrower term]: http://www.cidoc-crm.org/cidoc-crm/P127i_has_narrower_term
@@ -110,7 +94,7 @@ Defintion of instances of [E58 Measurement Unit] should be avoided but either ta
110
94
111
95
#### E41 Appellation
112
96
113
-
**[E42 Appellation]** and its subclasses ([E35 Title] and [E42 Identifier]) should be avoided (see [above](#primitive-values) for additional subclasses [E61 Time Primitive], [E94 Space Primitive], and [E94 Space Primitive]):
97
+
**[E41 Appellation]** and its subclasses ([E35 Title] and [E42 Identifier]) should be avoided (see [above](#primitive-values) for additional subclasses [E61 Time Primitive], [E94 Space Primitive], and [E94 Space Primitive]), unless a name cannot uniquely be identified with a sequence of Unicode characters and an optional language tag:
114
98
115
99
~~~ttl
116
100
<RMSTitantic>
@@ -125,6 +109,11 @@ If there are multiple names with one preferred name per language and optional na
125
109
skos:altLabel "Titanic"@en, "Royal Mail Steamship Titanic"@en .
126
110
~~~
127
111
112
+
The RDF property `skos:prefLabel` should not be confused with [P48 has preferred identifier] to be used for identifiers only.
113
+
114
+
115
+
If information about the act of naming is required, use [E13 Attribute Assignment] for simple appelations or [E15 Identifier Assignment] for identifiers.
116
+
128
117
If an identifier **[E42 Identifier] is an URI** meant to identify an RDF resource, dont use plain strings but resource URIs in RDF. If a resource happens to have multiple equivalent URIs, choose a preferred URI and use `owl:sameAs` to record aliases:
129
118
130
119
~~~ttl
@@ -153,3 +142,20 @@ CRM is constantly evolving, so some CRM classes have been renamed or replaced. O
0 commit comments