7 See the DCMI accessRights guidelines [DC-ACCESSRIGHTS] for an example.
| Darwin Core term | Notes on expressing as RDF |
| These date terms have range rdfs:Literal 8. Best practice as specified in the term definition recommends that they should be formatted according to ISO 8601:2004(E). There is no defined XML Schema datatype that corresponds exactly to ISO 8601:2004(E), therefore the entire set of possible values cannot be specified using an rdf:datatype attribute. The XML Schema dateTime datatype (xsd:dateTime) which is effectively a subset of ISO 8601:2004(E), may be used as an rdf:datatype attribute. However, xsd:dateTime requires the complete series of year, month, day, hour, second (e.g., 002-10-10T12:00:00) and does not permit listing only part of this hierarchy (e.g., only the year) as is allowed in ISO 8601:2004(E). |
| dwc:eventTime | It is recommended that the format described by ISO 8601:2004(E) be used. As with the date terms, there is no XML Schema datatype that includes all of the possible values allowed in ISO 8601:2004(E), so there is no generic rdf:datatype attribute that would apply to all possible instances. The XML Schema time datatype (xsd:time) which is effectively a subset of ISO 8601:2004(E) may be used as an rdf:datatype attribute although it is limited to values that include hours, minutes, and seconds (e.g., 13:07:56-05:00). |
| These terms are expected to have literal values that are numeric. Therefore, an rdf:datatype attribute describing the form of the number should be used. |
| Because these are remarks, they are expected to have literal values with an xml:lang attribute. |
| Based on their term definitions, these terms are expected to have untyped literal values |
| dwc:otherCatalogNumbers | There is no simple mapping because of the kinds of identifiers people use and variety of relationships that there may be among identifiers. For non-IRI identifiers expressed as string values, the string may be provided as a literal value of dwc:otherCatalogNumbers. Whether this is preferable to providing multiple dwc:catalogNumber properties may depend on community practice. owl:sameAs may be used to associate other IRI identifiers with the subject IRI if that is appropriate. |
| dwc:basisOfRecord | Use only with literal value strings consisting of the local name component of Darwin Core class IRIs. Use rdf:type to refer to IRIs that describe the type of the resource. |
| dwc:dynamicProperties | Expected to contain JSON as a literal. Communities of practice might choose to use other vocabularies or develop their own vocabularies to express this sort of content directly as RDF. |
| Darwin Core term | Notes on expressing as RDF |
| These date terms have range rdfs:Literal 8. Best practice as specified in the term definition recommends that they should be formatted according to ISO 8601:2004(E). There is no defined XML Schema datatype that corresponds exactly to ISO 8601:2004(E), therefore the entire set of possible values cannot be specified using an rdf:datatype attribute. The XML Schema dateTime datatype (xsd:dateTime) which is effectively a subset of ISO 8601:2004(E), may be used as an rdf:datatype attribute. However, xsd:dateTime requires the complete series of year, month, day, hour, second (e.g., 002-10-10T12:00:00) and does not permit listing only part of this hierarchy (e.g., only the year) as is allowed in ISO 8601:2004(E). |
| dwc:eventTime | It is recommended that the format described by ISO 8601:2004(E) be used. As with the date terms, there is no XML Schema datatype that includes all of the possible values allowed in ISO 8601:2004(E), so there is no generic rdf:datatype attribute that would apply to all possible instances. The XML Schema time datatype (xsd:time) which is effectively a subset of ISO 8601:2004(E) may be used as an rdf:datatype attribute although it is limited to values that include hours, minutes, and seconds (e.g., 13:07:56-05:00). |
| These terms are expected to have literal values that are numeric. Therefore, an rdf:datatype attribute describing the form of the number should be used. |
| Because these are remarks, they are expected to have literal values with an xml:lang attribute. |
| Based on their term definitions, these terms are expected to have untyped literal values |
| dwc:otherCatalogNumbers | There is no simple mapping because of the kinds of identifiers people use and variety of relationships that there may be among identifiers. For non-IRI identifiers expressed as string values, the string may be provided as a literal value of dwc:otherCatalogNumbers. Whether this is preferable to providing multiple dwc:catalogNumber properties may depend on community practice. owl:sameAs may be used to associate other IRI identifiers with the subject IRI if that is appropriate. |
| dwc:basisOfRecord | Use only with literal value strings consisting of the local name component of Darwin Core class IRIs. Use rdf:type to refer to IRIs that describe the type of the resource. |
| dwc:dynamicProperties | Expected to contain JSON as a literal. Communities of practice might choose to use other vocabularies or develop their own vocabularies to express this sort of content directly as RDF. |
8 No Darwin Core terms defined in the Darwin Core normative RDF (as opposed to those imported from Dublin Core) have domain or range declarations as a part of their definitions. However, the five terms in the dwc: namespace listed in the table above are defined to be rdfs:subPropertyOf of dcterms:date, which has the range rdfs:Literal. Under the extensional entailment rule ext4 listed in section 7.3.1 of the RDF Semantics 2004 W3C Recommendation [RDF-SEMANTICS-2004], these terms can be inferred to have the range rdfs:Literal. However, the RDF 1.1 Semantics W3C Recommendation [RDF-SEMANTICS-1.1] does not include these extensional entailment rules. Nevertheless, it is reasonable to expect that date properties should have literal values, with datatype attributes whenever possible.
@@ -885,7 +885,7 @@| Darwin Core term having a dwciri: analogue with the same local name | Notes on the dwciri: analogues |
| The object is an agent; use a well-known IRI such as those referenced in the list of sources of controlled values in the Darwin Core informative ancillary web pages [DWC-RDF-ANCILLARY]. |
| dwc:locationAccordingTo | The object is an agent or publication. Use a well-known IRI when possible, such as an HTTP-proxied DOI. |
| The object is a published or well-known reference; use an IRI version (preferably HTTP proxied) of doi, isbn, issn, etc. if available. |
| Recommended best practice is to use a controlled vocabulary if one is available. |
| If the object property (dwciri: analogue) is used rather than the dwc: property, the object property should point to a stable resource which might be a controlled vocabulary. |
| dwciri:fieldNumber is an object property whose subject is a (possibly IRI-identified) resource that is the field notes and whose object is a dcmitype:Event instance. dwciri:fieldNotes is an object property whose subject is a dcmitype:Event instance and whose object is a (possibly IRI-identified) resource that is the field notes. |
| dwc:recordNumber | dwciri:recordNumber is an object property whose subject is an occurrence and and whose object is a (possibly IRI-identified) resource that is the field notes. |
| Darwin Core term having a dwciri: analogue with the same local name | Notes on the dwciri: analogues |
| The object is an agent; use a well-known IRI such as those referenced in the list of sources of controlled values in the Darwin Core informative ancillary web pages [DWC-RDF-ANCILLARY]. |
| dwc:locationAccordingTo | The object is an agent or publication. Use a well-known IRI when possible, such as an HTTP-proxied DOI. |
| The object is a published or well-known reference; use an IRI version (preferably HTTP proxied) of doi, isbn, issn, etc. if available. |
| Recommended best practice is to use a controlled vocabulary if one is available. |
| If the object property (dwciri: analogue) is used rather than the dwc: property, the object property should point to a stable resource which might be a controlled vocabulary. |
| dwciri:fieldNumber is an object property whose subject is a (possibly IRI-identified) resource that is the field notes and whose object is a dcmitype:Event instance. dwciri:fieldNotes is an object property whose subject is a dcmitype:Event instance and whose object is a (possibly IRI-identified) resource that is the field notes. |
| dwc:recordNumber | dwciri:recordNumber is an object property whose subject is an occurrence and and whose object is a (possibly IRI-identified) resource that is the field notes. |