The Dublin Core Metadata Initiative is looking for someone to build them a wiki. At least I think that’s what they want.
From the Call for Tender page:
“DCMI Call for Tender 2007-03: Wiki format for application profiles convertible into XML”
From the DCMI home page:
“Call for tender for a machine-processable application profile format”
I don’t think that these two descriptions are describing the same thing at all. Of course, that just reflects my sense that “machine-processable application profile” doesn’t mean “application profile that can be scraped from a wiki page and expressed as XML”.
I’m more inclined to think that a “machine-processable application profile” means a DCAP that can be directly used to validate data that has been created with the intention of conforming to a specified DCAP (or is it DSP? — I wish that they wouldn’t suddenly change the terminology just to fit the model).
Increasingly, I’m viewing “machine-processable application profile” as meaning machine-processable-DCAP-derived data-entry forms (XFORMS) used to generate DCAP-conformant XML data that can be validated using a machine-processable-DCAP-derived RELAX NG schema, W3C XML Schema, or Schematron ruleset. RDF triples would then have to be derived from the validated XML.
The intermediate XML validation is necessary because a sensibly efficient way to validate RDF against a DCAP currently doesn’t exist. Although Alistair‘s notion of rules-based RDF validation based on SPARQL query assertions looks like it might work in a Schematron-like way. This would then imply the ability to derive SPARQL queries from a machine-processable DCAP.
While the idea of a wiki-based DCAP editor is conceptually interesting, it would seem to me that a tender to produce exemplars of the above based on the current DCAP XML expression would be far more useful in actually providing useful test cases for determining the validity and utility of that expression.