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

change note format from bold to italics

This commit is contained in:
Steve Baskauf 2021-08-05 16:29:50 -05:00
parent 8b3f35f235
commit d7579720de
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/rdf/index.md
View File

@ -897,9 +897,9 @@ would be valid RDF. However, best practices ([Section 2.4.2.1.1](#24211-objects-
#### 2.6.1 Unintended consequences of using Darwin Core ID terms in RDF (non-normative)
**Note added in 2021-07-15 version:**
*Note added in 2021-07-15 version:*
**When the Darwin Core vocabulary was brought into conformance with the [Standards Documentation Specification](http://rs.tdwg.org/sds/doc/specification/), in order to comply with [Section 4.4.2.2](http://rs.tdwg.org/sds/doc/specification/#44-vocabularies-term-lists-and-terms), all subproperty declarations were removed from the term metadata. Therefore, the effects described in this section are no longer entailed by RDF metadata describing any Darwin Core terms. This explanation has been retained to explain part of the rationale for why ID terms were not recommended for use with RDF in the original specification.**
*When the Darwin Core vocabulary was brought into conformance with the [Standards Documentation Specification](http://rs.tdwg.org/sds/doc/specification/), in order to comply with [Section 4.4.2.2](http://rs.tdwg.org/sds/doc/specification/#44-vocabularies-term-lists-and-terms), all subproperty declarations were removed from the term metadata. Therefore, the effects described in this section are no longer entailed by RDF metadata describing any Darwin Core terms. This explanation has been retained to explain part of the rationale for why ID terms were not recommended for use with RDF in the original specification.*
The previous section showed that using a Darwin Core ID term to indicate the identifier associated with the subject resource is not necessary because there are well-known means in RDF (the `rdf:about` attribute and the `dcterms:identifier` property) for exposing the subject’s identifier. However, as shown below, using a Darwin Core ID term to identify an object resource (as shown in the non-RDF XML Example 21) would actually be problematic. In its normative definition, each Darwin Core ID term is declared to be `rdfs:subPropertyOf` `dcterms:identifier`. In RDF, the purpose of a subproperty declaration is to allow a client with reasoning capability to infer a triple containing a broader (and presumably more well-known) property. In the terminology of Dublin Core, the "ID" term is a [qualifier](https://www.dublincore.org/specifications/dublin-core/usageguide/qualifiers/) which "refines" a basic Dublin Core term and the process of inferring a broader meaning from a more specific term is called a "dumb-down" operation. If a provider attempting to expose the data of Table 3 as RDF used the `dwc:taxonID` term as a property of the identification as shown in the (incorrect) Example 23: