 |
 |
Dear Tom, well...one better should look for http://www.mathematik.uni-osnabrueck.de/projects/dcqual/qual21.3.1/Schema/A/terms What is in there should suffice as support of the dc-web-site for RDF applications. That is for instance what an RDF Schema intended for. [This doesn't say, that all RDF applications will just use such a slim version. ] Your question about automatic generation: That may depend on the metadata/structure of the documents /usage/terms/dc/ cites. In case the snippets of information one wants to see in a Schema ready for machine consumption, which uses standardized vocabulary and fromal syntax to express (semantic) relations and rules to machines can savely be picked up from documents intended for human consumption - of course you can write a program - but you're left to define (!), what will be mapped to what....i.e. and additional set of rules. For that it's a bit confusing, that usage/terms/dc/ mixes seemingly (?) existing metadata vocabulary with it's own terms - technically speaking it's not clear whether an additional namespace is asked for to represent the terms used in an RDF Schema. In the Scheme/A/terms approach things are expressed using DC and RDFS vocabulary only. One example: Speaking RDF usage/terms/dc seems to introduce a Class called "Decision" and goes ahead in typing certain documents as members of the Class. The pointer to such a document is an rdfs:seeAlso - In case one thinks it's important for the functionality of arbitrary RDF applications based on DC vocabulary to know about certain documents represent decisions - one will need a namespace outside the range of the dcmi namespace recommendation to host a Class named "Decision". Similarly it is with the supersede property: Is it used - as one would expect - as a subProperty of dcterms:replaces or is it used to indicate versioning (of what)? Cheers, rs