tmdinosaurcenter
/
dwc
mirror of https://github.com/tdwg/dwc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add verticalDatum , move measurementValue

This commit is contained in:
Steve Baskauf 2021-08-04 16:47:36 -05:00
parent c86e206c60
commit b784cb943a
2 changed files with 1429 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1423
docs/rdf/2016-04-25.md Normal file
View File

File diff suppressed because it is too large Load Diff

12
docs/rdf/index.md
View File

@ -4,7 +4,7 @@ Title
: Darwin Core RDF guide : Darwin Core RDF guide
Date version issued Date version issued
: 2016-04-25 : 2021-07-15
Date created Date created
: 2015-03-27 : 2015-03-27
@ -13,13 +13,13 @@ Part of TDWG Standard
: <http://www.tdwg.org/standards/450/> : <http://www.tdwg.org/standards/450/>
This version This version
: <http://rs.tdwg.org/dwc/terms/guides/rdf/2015-06-02> : <http://rs.tdwg.org/dwc/terms/guides/rdf/2021-07-15>
Latest version Latest version
: <http://rs.tdwg.org/dwc/terms/guides/rdf/> : <http://rs.tdwg.org/dwc/terms/guides/rdf/>
Previous version Previous version
: <http://rs.tdwg.org/dwc/terms/guides/rdf/2015-03-27> : <http://rs.tdwg.org/dwc/terms/guides/rdf/2016-04-25>
Abstract Abstract
: This guide is intended to facilitate the use of Darwin Core terms in the Resource Description Framework (RDF). It explains basic features of RDF and provides details of how to expose data in the form of RDF using Darwin Core terms and terms from other key vocabularies. It defines terms in the namespace `http://rs.tdwg.org/dwc/iri/` which are intended for use exclusively with non-literal objects. : This guide is intended to facilitate the use of Darwin Core terms in the Resource Description Framework (RDF). It explains basic features of RDF and provides details of how to expose data in the form of RDF using Darwin Core terms and terms from other key vocabularies. It defines terms in the namespace `http://rs.tdwg.org/dwc/iri/` which are intended for use exclusively with non-literal objects.
@ -31,7 +31,7 @@ Creator
: Darwin Core and RDF/OWL Task Groups : Darwin Core and RDF/OWL Task Groups
Bibliographic citation Bibliographic citation
: Darwin Core and RDF/OWL Task Groups. 2015. Darwin Core RDF guide. Biodiversity Information Standards (TDWG). <http://rs.tdwg.org/dwc/terms/guides/rdf/> : Darwin Core and RDF/OWL Task Groups. 2015. Darwin Core RDF guide. Biodiversity Information Standards (TDWG). <http://rs.tdwg.org/dwc/terms/guides/rdf/2021-07-15>
## 1 Introduction (non-normative) ## 1 Introduction (non-normative)
@ -1366,7 +1366,7 @@ Darwin Core term | Notes on expressing as RDF
--- | --- --- | ---
`dwc:eventDate`<br>`dwc:georeferencedDate`<br>`dwc:dateIdentified`<br>`dwc:relationshipEstablishedDate`<br>`dwc:measurementDeterminedDate` | 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)](https://en.wikipedia.org/wiki/ISO_8601). There is no defined [XML Schema datatype](https://www.w3.org/TR/xmlschema11-2/) 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](https://www.w3.org/TR/xmlschema11-2/#dateTime) (`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:eventDate`<br>`dwc:georeferencedDate`<br>`dwc:dateIdentified`<br>`dwc:relationshipEstablishedDate`<br>`dwc:measurementDeterminedDate` | 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)](https://en.wikipedia.org/wiki/ISO_8601). There is no defined [XML Schema datatype](https://www.w3.org/TR/xmlschema11-2/) 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](https://www.w3.org/TR/xmlschema11-2/#dateTime) (`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)](https://en.wikipedia.org/wiki/ISO_8601) be used. As with the date terms, there is no [XML Schema datatype](https://www.w3.org/TR/xmlschema11-2/) 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 dateTime datatype](https://www.w3.org/TR/xmlschema11-2/#dateTime) (`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). `dwc:eventTime` | It is recommended that the format described by [ISO 8601:2004(E)](https://en.wikipedia.org/wiki/ISO_8601) be used. As with the date terms, there is no [XML Schema datatype](https://www.w3.org/TR/xmlschema11-2/) 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 dateTime datatype](https://www.w3.org/TR/xmlschema11-2/#dateTime) (`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).
`dwc:individualCount`<br>`dwc:decimalLatitude`<br>`dwc:decimalLongitude`<br>`dwc:coordinatePrecision`<br>`dwc:pointRadiusSpatialFit`<br>`dwc:coordinateUncertaintyInMeters`<br>`dwc:minimumElevationInMeters`<br>`dwc:maximumElevationInMeters`<br>`dwc:minimumDepthInMeters`<br>`dwc:maximumDepthInMeters`<br>`dwc:minimumDistanceAboveSurfaceInMeters`<br>`dwc:maximumDistanceAboveSurfaceInMeters`<br>`dwc:startDayOfYear`<br>`dwc:endDayOfYear`<br>`dwc:year`<br>`dwc:month`<br>`dwc:day`<br>`dwc:footprintSpatialFit`<br>`dwc:measurementValue`<br>`dwc:measurementAccuracy` | 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. `dwc:individualCount`<br>`dwc:decimalLatitude`<br>`dwc:decimalLongitude`<br>`dwc:coordinatePrecision`<br>`dwc:pointRadiusSpatialFit`<br>`dwc:coordinateUncertaintyInMeters`<br>`dwc:minimumElevationInMeters`<br>`dwc:maximumElevationInMeters`<br>`dwc:minimumDepthInMeters`<br>`dwc:maximumDepthInMeters`<br>`dwc:minimumDistanceAboveSurfaceInMeters`<br>`dwc:maximumDistanceAboveSurfaceInMeters`<br>`dwc:startDayOfYear`<br>`dwc:endDayOfYear`<br>`dwc:year`<br>`dwc:month`<br>`dwc:day`<br>`dwc:footprintSpatialFit`<br>`dwc:measurementAccuracy` | 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.
`dwc:occurrenceRemarks`<br>`dwc:eventRemarks`<br>`dwc:locationRemarks`<br>`dwc:georeferenceRemarks`<br>`dwc:identificationRemarks`<br>`dwc:taxonRemarks`<br>`dwc:organismRemarks`<br>`dwc:relationshipRemarks`<br>`dwc:measurementRemarks` | Because these are remarks, they are expected to have literal values with an `xml:lang` attribute. `dwc:occurrenceRemarks`<br>`dwc:eventRemarks`<br>`dwc:locationRemarks`<br>`dwc:georeferenceRemarks`<br>`dwc:identificationRemarks`<br>`dwc:taxonRemarks`<br>`dwc:organismRemarks`<br>`dwc:relationshipRemarks`<br>`dwc:measurementRemarks` | Because these are remarks, they are expected to have literal values with an `xml:lang` attribute.
`dwc:catalogNumber`<br>`dwc:samplingEffort`<br>`dwc:organismName`<br>`dwc:verbatimEventDate`<br>`dwc:verbatimLocality`<br>`dwc:verbatimElevation`<br>`dwc:verbatimCoordinates`<br>`dwc:verbatimLatitude`<br>`dwc:verbatimLongitude`<br>`dwc:verbatimDepth`<br>`dwc:verbatumTaxonRank` | Based on their term definitions, these terms are expected to have untyped literal values `dwc:catalogNumber`<br>`dwc:samplingEffort`<br>`dwc:organismName`<br>`dwc:verbatimEventDate`<br>`dwc:verbatimLocality`<br>`dwc:verbatimElevation`<br>`dwc:verbatimCoordinates`<br>`dwc:verbatimLatitude`<br>`dwc:verbatimLongitude`<br>`dwc:verbatimDepth`<br>`dwc:verbatumTaxonRank` | 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: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.
@ -1405,7 +1405,7 @@ Darwin Core term having a `dwciri:` analogue with the same local name | Notes on
`dwc:recordedBy`<br>`dwc:identifiedBy`<br>`dwc:georeferencedBy`<br>`dwc:measurementDeterminedBy` | 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 page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md). `dwc:recordedBy`<br>`dwc:identifiedBy`<br>`dwc:georeferencedBy`<br>`dwc:measurementDeterminedBy` | 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 page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md).
`dwc:locationAccordingTo` | The object is an agent or publication. Use a well-known IRI when possible, such as an HTTP-proxied DOI. `dwc:locationAccordingTo` | The object is an agent or publication. Use a well-known IRI when possible, such as an HTTP-proxied DOI.
`dwc:georeferenceProtocol`<br>`dwc:georeferenceSources`<br>`dwc:samplingProtocol` | The object is a published or well-known reference; use an IRI version (preferably HTTP proxied) of doi, isbn, issn, etc. if available. `dwc:georeferenceProtocol`<br>`dwc:georeferenceSources`<br>`dwc:samplingProtocol` | The object is a published or well-known reference; use an IRI version (preferably HTTP proxied) of doi, isbn, issn, etc. if available.
`dwc:sex`<br>`dwc:lifeStage`<br>`dwc:reproductiveCondition`<br>`dwc:establishmentMeans`<br>`dwc:behavior`<br>`dwc:occurrenceStatus`<br>`dwc:disposition`<br>`dwc:verbatimCoordinateSystem`<br>`dwc:verbatimSRS`<br>`dwc:geodeticDatum`<br>`dwc:georeferenceVerificationStatus`<br>`dwc:footprintWKT`<br>`dwc:footprintSRS`<br>`dwc:lowestBiostratigraphicZone`<br>`dwc:highestBiostratigraphicZone`<br>`dwc:identificationVerificationStatus`<br>`dwc:identificationQualifier`<br>`dwc:preparations`<br>`dwc:typeStatus`<br>`dwc:measurementType`<br>`dwc:measurementUnit`<br>`dwc:measurementMethod` | Recommended best practice is to use a controlled vocabulary if one is available. `dwc:sex`<br>`dwc:lifeStage`<br>`dwc:reproductiveCondition`<br>`dwc:establishmentMeans`<br>`dwc:behavior`<br>`dwc:occurrenceStatus`<br>`dwc:disposition`<br>`dwc:verbatimCoordinateSystem`<br>`dwc:verbatimSRS`<br>`dwc:geodeticDatum`<br>`dwc:verticalDatum`<br>`dwc:georeferenceVerificationStatus`<br>`dwc:footprintWKT`<br>`dwc:footprintSRS`<br>`dwc:lowestBiostratigraphicZone`<br>`dwc:highestBiostratigraphicZone`<br>`dwc:identificationVerificationStatus`<br>`dwc:identificationQualifier`<br>`dwc:preparations`<br>`dwc:typeStatus`<br>`dwc:measurementType`<br>`dwc:measurementValue`<br>`dwc:measurementUnit`<br>`dwc:measurementMethod` | Recommended best practice is to use a controlled vocabulary if one is available.
`dwc:informationWithheld`<br>`dwc:dataGeneralizations`<br>`dwc:habitat` | 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. `dwc:informationWithheld`<br>`dwc:dataGeneralizations`<br>`dwc:habitat` | 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.
`dwc:fieldNumber`<br>`dwc:fieldNotes` | `dwciri:fieldNumber` is an object property whose subject is a (possibly IRI-identified) resource that is the field notes and whose object is a `dwc:Event` instance. `dwciri:fieldNotes` is an object property whose subject is a `dwc:Event` instance and whose object is a (possibly IRI-identified) resource that is the field notes. `dwc:fieldNumber`<br>`dwc:fieldNotes` | `dwciri:fieldNumber` is an object property whose subject is a (possibly IRI-identified) resource that is the field notes and whose object is a `dwc:Event` instance. `dwciri:fieldNotes` is an object property whose subject is a `dwc: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 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 whose object is a (possibly IRI-identified) resource that is the field notes.