> Of course, I can see that from the perspective of your proposal this is
> a Good Thing! But it does seem perhaps slightly contrary to the way
> metadata formats have typically been used in OAI-PMH - though I say this
> without first-hand experience of working either as a service provide or
> data provider so I may be skating on thin ice, and others are better
> placed to comment. My understanding is that metadata formats are used
> precisely to try to ensure "predictability" - if as a data provider I
> say I provide a specified format, then a service provider knows
> _exactly_ what to expect.
This kind of "predictability" depends on the way you design the XML
Schema. When you take a design inspired by HTML Meta - you can
get rid off the limitation. We played a little with RDF generally
a bit - What one needs to add is something like an XSLT.
I think Andy did so specifically for HTMLMeta2RDF/XML.
> (Having said that, I take the point made by Roland that as terms are
> added to the DCMI dcterms vocabulary, "Qualified DC" as described in
> Andy's model doc changes through time, and so would a metadata format
> corresponding to that.)
Not necessarily. Good old HTML meta is NOT affected by property
....But these things are largely tools issues and not primarily