Note: I did not change the obsolete terms, which have always had camelCase labels. Also, the IRI terms that have non-IRI analogs have " (IRI)" appended to their labels to distinguish them.
Move dcterms:type below the recommended terms and change status to deprecated. Change its notes to indicate that dc:type should be used for strings and that the RDF guide recommends rdf:type instead of dcterms:type when providing an IRI value. Replace dcterms:type in the record-level terms with dc:type and carry over the examples that were previously in dcterms:type to it. NOTE: the terms below the recommended terms are not in alphabetical order still.
In the record level terms section, replace dcterms:language with dc:language. Use the former dcterms: examples for string values with dc:language. Move dcterms:language to the UseWithIRI section and change its recommended value to an IRI from the LOC ISO 639-2 scheme (to maintain consistency with Audubon Core usage. NOTE: the value of organized_in for dc:language is now different from the other DCMI terms in the record-level section. Will that break the QRG build script?
So they are mixed with the order recommended terms, in Darwin Core order. Ran python build.py after this and there are no changes in the quick ref guide
See #262:
- Remove 160 terms from 2018-09-06 that are unchanged duplicates of the 2017-10-06 version
- Reinstate "recommended" status for the 160 2017-10-06 terms 45 + 47 + 36 + 1 + 31
Not that the reinstated recommended terms are NOT YET SORTED to the top
Ping @tucotuco: as far as I can find, spaces are allowed in wkt. Adding them allows the example to wrap to multiple lines in the quick ref, thus not breaking the design. Only updated for recommended term, not the two superseded ones
Steve Baskauf
peterdesmet
Peter Desmet
tucotuco