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

Add correct <br> codes back to tables

This commit is contained in:
Peter Desmet 2018-10-01 21:28:01 +02:00
parent f0dd92e939
commit 63b52d515b
1 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
docs/rdf/index.md
View File

@ -1364,11 +1364,11 @@ dcterms:bibliographicCitation | dcterms:BibliographicResource | rdfs:Literal
Darwin Core term | Notes on expressing as RDF
--- | ---
`dwc:eventDate` `dwc:georeferencedDate` `dwc:dateIdentified` `dwc:relationshipEstablishedDate` `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:individualCount` `dwc:decimalLatitude` `dwc:decimalLongitude` `dwc:coordinatePrecision` `dwc:pointRadiusSpatialFit` `dwc:coordinateUncertaintyInMeters` `dwc:minimumElevationInMeters` `dwc:maximumElevationInMeters` `dwc:minimumDepthInMeters` `dwc:maximumDepthInMeters` `dwc:minimumDistanceAboveSurfaceInMeters` `dwc:maximumDistanceAboveSurfaceInMeters` `dwc:startDayOfYear` `dwc:endDayOfYear` `dwc:year` `dwc:month` `dwc:day` `dwc:footprintSpatialFit` `dwc:measurementValue` `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` `dwc:eventRemarks` `dwc:locationRemarks` `dwc:georeferenceRemarks` `dwc:identificationRemarks` `dwc:taxonRemarks` `dwc:organismRemarks` `dwc:relationshipRemarks` `dwc:measurementRemarks` | Because these are remarks, they are expected to have literal values with an `xml:lang` attribute.
`dwc:catalogNumber` `dwc:samplingEffort` `dwc:organismName` `dwc:verbatimEventDate` `dwc:verbatimLocality` `dwc:verbatimElevation` `dwc:verbatimCoordinates` `dwc:verbatimLatitude` `dwc:verbatimLongitude` `dwc:verbatimDepth` `dwc:verbatumTaxonRank` | Based on their term definitions, these terms are expected to have untyped literal values
`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: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: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.
@ -1381,11 +1381,11 @@ See [Section 2.7](#27-darwin-core-convenience-terms-non-normative) for more info
Darwin Core term | Notes
--- | ---
`dwc:collectionCode` `dwc:institutionCode` `dwc:ownerInstitutionCode` | The subject resource can be any resource that is part of a collection. As an alternative, use the object property `dwciri:inCollection` to link the subject resource to an IRI for the collection containing the institution that owns or controls the resource.
`dwc:kingdom` `dwc:phylum` `dwc:class` `dwc:order` `dwc:family` `dwc:genus` `dwc:subgenus` `dwc:specificEpithet` `dwc:infraspecificEpithet` `dwc:higherClassification` `dwc:vernacularName` `dwc:nameAccordingTo` `dwc:scientificName` `dwc:taxonRank` `dwc:scientificNameAuthorship` `dwc:nomenclaturalStatus` `dwc:namePublishedIn` `dwc:namePublishedInYear` `dwc:nomenclaturalCode` `dwc:originalNameUsage` `dwc:taxonomicStatus` `dwc:parentNameUsage` `dwc:acceptedNameUsage` | The subject resource should be a `dwc:Identification` instance. See [Section 2.7.4](#274-description-of-a-taxonomic-entity-normative) for a discussion of why it not recommended to use these as properties of `dwc:Taxon` instances. As an alternative, use the object property `dwciri:toTaxon` to link the subject `dwc:Identification` instance to a taxonomic entity such as a taxon, taxon concept, or taxon name use. It is likely that these taxonomic entities will have a complex structure which differentiates among name entities, name strings, application of a name to a concept, which expresses parent/child and set relationships among entities, and which tracks provenance information about the names, references, and concepts. The flat nature of text-based Darwin Core cannot represent such a complex structure and it is beyond the scope of this guide to describe them.
`dwc:higherGeography` `dwc:continent` `dwc:waterBody` `dwc:islandGroup` `dwc:island` `dwc:countryCode` `dwc:country` `dwc:stateProvince` `dwc:county` `dwc:municipality` `dwc:locality` | The subject resource should be a `dcterms:Location` instance. As an alternative, use the object property `dwciri:inDescribedPlace` to link the subject resource to a standardized place described as part of a hierarchy. See [Section 2.7.5](#275-names-of-geographic-subdivisions-normative) for details. It is likely that providers will want to provide a text value for `dwc:locality` even if `dwciri:inDescribedPlace` is used to replace the other hierarchical convenience terms in this category. This is because it is unlikely that a place description at this most specific level (e.g., "15 km N of Essen") would be represented by a standardized IRI-identified place instance. There is no `dwciri:` analogue of `dwc:locality` because if an IRI-identified place were available to represent the locality, the term `dwciri:inDescribedPlace` would be used to link to it.
`dwc:earliestEonOrLowestEonothem` `dwc:latestEonOrHighestEonothem` `dwc:earliestEraOrLowestErathem` `dwc:latestEraOrHighestErathem` `dwc:earliestPeriodOrLowestSystem` `dwc:latestPeriodOrHighestSystem` `dwc:earliestEpochOrLowestSeries` `dwc:latestEpochOrHighestSeries` `dwc:earliestAgeOrLowestStage` `dwc:latestAgeOrHighestStage` | The subject resource should be a `dwc:GeologicalContext` instance. As an alternative, use the object properties `dwciri:earliestGeochronologicalEra` and `dwciri:latestGeochronologicalEra` as described in [Section 3.6](#36-dwciri-terms-having-local-names-that-dont-correspond-to-terms-in-the-dwc-darwin-core-namespace-normative). See [Section 2.7.6](#276-chronostratographic-geological-timescale-descriptors-normative) for details.
`dwc:lithostratigraphicTerms` `dwc:group` `dwc:formation` `dwc:member` `dwc:bed` | The subject resource should be a `dwc:GeologicalContext` instance. As an alternative, use the object property `dwciri:fromLithostratigraphicUnit` to link the subject resource to the lowest appropriate unit of a lithostratigraphic hierarchy.
`dwc:collectionCode`<br>`dwc:institutionCode`<br>`dwc:ownerInstitutionCode` | The subject resource can be any resource that is part of a collection. As an alternative, use the object property `dwciri:inCollection` to link the subject resource to an IRI for the collection containing the institution that owns or controls the resource.
`dwc:kingdom`<br>`dwc:phylum`<br>`dwc:class`<br>`dwc:order`<br>`dwc:family`<br>`dwc:genus`<br>`dwc:subgenus`<br>`dwc:specificEpithet`<br>`dwc:infraspecificEpithet`<br>`dwc:higherClassification`<br>`dwc:vernacularName`<br>`dwc:nameAccordingTo`<br>`dwc:scientificName`<br>`dwc:taxonRank`<br>`dwc:scientificNameAuthorship`<br>`dwc:nomenclaturalStatus`<br>`dwc:namePublishedIn`<br>`dwc:namePublishedInYear`<br>`dwc:nomenclaturalCode`<br>`dwc:originalNameUsage`<br>`dwc:taxonomicStatus`<br>`dwc:parentNameUsage`<br>`dwc:acceptedNameUsage` | The subject resource should be a `dwc:Identification` instance. See [Section 2.7.4](#274-description-of-a-taxonomic-entity-normative) for a discussion of why it not recommended to use these as properties of `dwc:Taxon` instances. As an alternative, use the object property `dwciri:toTaxon` to link the subject `dwc:Identification` instance to a taxonomic entity such as a taxon, taxon concept, or taxon name use. It is likely that these taxonomic entities will have a complex structure which differentiates among name entities, name strings, application of a name to a concept, which expresses parent/child and set relationships among entities, and which tracks provenance information about the names, references, and concepts. The flat nature of text-based Darwin Core cannot represent such a complex structure and it is beyond the scope of this guide to describe them.
`dwc:higherGeography`<br>`dwc:continent`<br>`dwc:waterBody`<br>`dwc:islandGroup`<br>`dwc:island`<br>`dwc:countryCode`<br>`dwc:country`<br>`dwc:stateProvince`<br>`dwc:county`<br>`dwc:municipality`<br>`dwc:locality` | The subject resource should be a `dcterms:Location` instance. As an alternative, use the object property `dwciri:inDescribedPlace` to link the subject resource to a standardized place described as part of a hierarchy. See [Section 2.7.5](#275-names-of-geographic-subdivisions-normative) for details. It is likely that providers will want to provide a text value for `dwc:locality` even if `dwciri:inDescribedPlace` is used to replace the other hierarchical convenience terms in this category. This is because it is unlikely that a place description at this most specific level (e.g., "15 km N of Essen") would be represented by a standardized IRI-identified place instance. There is no `dwciri:` analogue of `dwc:locality` because if an IRI-identified place were available to represent the locality, the term `dwciri:inDescribedPlace` would be used to link to it.
`dwc:earliestEonOrLowestEonothem`<br>`dwc:latestEonOrHighestEonothem`<br>`dwc:earliestEraOrLowestErathem`<br>`dwc:latestEraOrHighestErathem`<br>`dwc:earliestPeriodOrLowestSystem`<br>`dwc:latestPeriodOrHighestSystem`<br>`dwc:earliestEpochOrLowestSeries`<br>`dwc:latestEpochOrHighestSeries`<br>`dwc:earliestAgeOrLowestStage`<br>`dwc:latestAgeOrHighestStage` | The subject resource should be a `dwc:GeologicalContext` instance. As an alternative, use the object properties `dwciri:earliestGeochronologicalEra` and `dwciri:latestGeochronologicalEra` as described in [Section 3.6](#36-dwciri-terms-having-local-names-that-dont-correspond-to-terms-in-the-dwc-darwin-core-namespace-normative). See [Section 2.7.6](#276-chronostratographic-geological-timescale-descriptors-normative) for details.
`dwc:lithostratigraphicTerms`<br>`dwc:group`<br>`dwc:formation`<br>`dwc:member`<br>`dwc:bed` | The subject resource should be a `dwc:GeologicalContext` instance. As an alternative, use the object property `dwciri:fromLithostratigraphicUnit` to link the subject resource to the lowest appropriate unit of a lithostratigraphic hierarchy.
### 3.6 `dwciri:` terms having local names that don’t correspond to terms in the `dwc:` Darwin Core namespace (normative)
@ -1394,7 +1394,7 @@ Darwin Core term | Notes
`dwciri:inCollection` | Use to link any subject resource that is part of a collection to the collection containing the resource. Recommended best practice is to use IRIs from [Global Registry of Biorepositories](http://grbio.org/). For details, see the list of sources of controlled values in the [Darwin Core informative ancillary web page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md). See [Section 2.7.3](#273-ownership-of-a-collection-item-normative) for usage details.
`dwciri:toTaxon` | Use to link a `dwc:Identification` instance subject to a taxonomic entity such as a taxon, taxon concept, or taxon name use. See [Section 2.7.4](#274-description-of-a-taxonomic-entity-normative) for usage details.
`dwciri:inDescribedPlace` | Use to link a `dcterms:Location` instance subject to the lowest level standardized hierarchically-described resource. It is expected that such resources will be linked to higher levels in the hierarchy by the organization minting the IRI. Recommended best practice is to use IRIs from the [GeoNames geographical database](https://www.geonames.org/). For details, see the list of sources of controlled values in the [Darwin Core informative ancillary web page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md). See [Section 2.7.5](#275-names-of-geographic-subdivisions-normative) for usage details.
`dwciri:earliestGeochronologicalEra` `dwciri:latestGeochronologicalEra` | Use to link a `dwc:GeologicalContext` instance to chronostratigraphic time periods at the lowest possible level in a standardized hierarchy. Use `dwciri:earliestGeochronologicalEra` to point to the earliest possible geological time period from which the cataloged item was collected and the object property `dwciri:latestGeochronologicalEra` to point to the latest possible geological time period from which the cataloged item was collected. The organization minting the IRI should link those time periods to higher levels in the hierarchy. Recommended best practice is to use IRIs defined by the [International Commission on Stratigraphy](http://www.stratigraphy.org/). For details, see the list of sources of controlled values in the [Darwin Core informative ancillary web page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md). See [Section 2.7.6](#276-chronostratographic-geological-timescale-descriptors-normative) for usage details.
`dwciri:earliestGeochronologicalEra`<br>`dwciri:latestGeochronologicalEra` | Use to link a `dwc:GeologicalContext` instance to chronostratigraphic time periods at the lowest possible level in a standardized hierarchy. Use `dwciri:earliestGeochronologicalEra` to point to the earliest possible geological time period from which the cataloged item was collected and the object property `dwciri:latestGeochronologicalEra` to point to the latest possible geological time period from which the cataloged item was collected. The organization minting the IRI should link those time periods to higher levels in the hierarchy. Recommended best practice is to use IRIs defined by the [International Commission on Stratigraphy](http://www.stratigraphy.org/). For details, see the list of sources of controlled values in the [Darwin Core informative ancillary web page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md). See [Section 2.7.6](#276-chronostratographic-geological-timescale-descriptors-normative) for usage details.
`dwciri:fromLithostratigraphicUnit` | Use to link a `dwc:GeologicalContext` instance to an IRI-identified lithostratigraphic unit at the lowest possible level in a hierarchy. It is expected that such resources will be linked to higher levels in the hierarchy by the organization minting the IRI. See [Section 2.7.7](#277-lithostratigraphy-descriptors-normative) for usage details.
`dwciri:inDataset` | This object property is provided to link a subject dataset record to the dataset which contains it. A string literal name of the dataset can be provided using the term `dwc:datasetName`.
@ -1402,19 +1402,19 @@ Darwin Core term | Notes
Darwin Core term having a `dwciri:` analogue with the same local name | Notes on the `dwciri:` analogues
--- | ---
`dwc:recordedBy` `dwc:identifiedBy` `dwc:georeferencedBy` `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:georeferenceProtocol` `dwc:georeferenceSources` `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` `dwc:lifeStage` `dwc:reproductiveCondition` `dwc:establishmentMeans` `dwc:behavior` `dwc:occurrenceStatus` `dwc:disposition` `dwc:verbatimCoordinateSystem` `dwc:verbatimSRS` `dwc:geodeticDatum` `dwc:georeferenceVerificationStatus` `dwc:footprintWKT` `dwc:footprintSRS` `dwc:lowestBiostratigraphicZone` `dwc:highestBiostratigraphicZone` `dwc:identificationVerificationStatus` `dwc:identificationQualifier` `dwc:preparations` `dwc:typeStatus` `dwc:measurementType` `dwc:measurementUnit` `dwc:measurementMethod` | Recommended best practice is to use a controlled vocabulary if one is available.
`dwc:informationWithheld` `dwc:dataGeneralizations` `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` `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: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: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: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.
### 3.8 Darwin Core terms for which this guide does not recommend the use of a `dwciri: object` property (normative)
Darwin Core term | Notes
--- | ---
`dwc:relationshipOfResource` `dwc:relationshipAccordingTo` | The non-RDF use of terms organized under the `dwc:ResourceRelationship` class depends on values for `dwc:resourceID` and `dwc:relatedResourceID`, terms which cannot be used in RDF for reasons discussed in [Section 2.6](#26-darwin-core-id-terms-and-rdf-normative). As of November 2014, the RDF/OWL Task Group is seeking a way to express resource relationships as RDF. For the present, `dwciri:` analogues have not been adopted for these two terms. See the [Darwin Core informative ancillary web page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md) for further discussion.
`dwc:associatedOccurrences` `dwc:associatedMedia` `dwc:associatedSequences` `dwc:associatedTaxa` `dwc:associatedOrganisms` | Use `dcterms:relation` and `rdf:type`, or terms that indicate more specific relationships as described in [Section 2.8](#28-darwin-core-association-terms-non-normative) (Darwin Core association terms).
`dwc:relationshipOfResource`<br>`dwc:relationshipAccordingTo` | The non-RDF use of terms organized under the `dwc:ResourceRelationship` class depends on values for `dwc:resourceID` and `dwc:relatedResourceID`, terms which cannot be used in RDF for reasons discussed in [Section 2.6](#26-darwin-core-id-terms-and-rdf-normative). As of November 2014, the RDF/OWL Task Group is seeking a way to express resource relationships as RDF. For the present, `dwciri:` analogues have not been adopted for these two terms. See the [Darwin Core informative ancillary web page](https://github.com/tdwg/rdf/blob/master/DwCAncillary.md) for further discussion.
`dwc:associatedOccurrences`<br>`dwc:associatedMedia`<br>`dwc:associatedSequences`<br>`dwc:associatedTaxa`<br>`dwc:associatedOrganisms` | Use `dcterms:relation` and `rdf:type`, or terms that indicate more specific relationships as described in [Section 2.8](#28-darwin-core-association-terms-non-normative) (Darwin Core association terms).
`dwc:previousIdentifications` | There is no consensus object property for associating identifications with resources of other classes. From whatever scheme you have chosen to provide object properties, use same object property as used for the most recent identification but provide an earlier dwc:dateIdentified value.
`dwc:organismScope` | Use `rdf:type` with a non-literal object. See the comment at http://rs.tdwg.org/dwc/terms/organismScope.