The DCMI has just released a new version of their document: “Expressing Dublin Core metadata using HTML/XHTML meta and link elements”. I am not really familiar with the details of the DCMI process but my understanding is that public comments are still welcome before finalizing the document. It is interesting to note that a clear mechanism is provided to define and use the different DCMI vocabularies via some sort of a namespace declaration mechanism, ie, this is not only to use the well known properties like
dc:date. Check it out!
Although not explicitly said in the document proper (everything is expressed in terms of the abstract Dublin Core data model) but it is noteworthy that the specification provides a clear way of getting the DC metadata into RDF. On the one hand, the abstract model can be expressed in RDF (see again the data model definition), and the encoding in HTML/XHTML is based on an HTML profile for DCMI. And using this profile, one gets a hook into the GRDDL processing world.
This more than just a theoretical possibility. Pete Johnson, one of the editors of the document, posted an extra mail on the DCMI archives referring to the fact the namespace document is already prepared for GRDDL and it links to an appropriate XSLT transform. Ie, already today, if one uses the profile and the conventions described in the DCMI documents, Dublin Core metadata can be mashed up with other RDF data via GRDDL. Eg, the example document on the DCMI site can yield the RDF content either via the W3C GRDDL service. Yey!
B.t.w.: it is interesting to note that the usage of (X)HTML profiles begins to come to the fore. GRDDL is based on profiles; the POWDER specification (see my earlier blog) uses profiles; now DCMI uses it big time. This is important to remember: there are voices in the HTML world who would like to strike HTML profiles. As far as I know (I may be wrong, though) the main reason being: it is not used. Well, this is changing!