Hi Andy,
> The current DCMI encoding guidelines and the draft abstract
> model require that all terms (DCMI terms and others) are
> assigned URI references before they can be used in metadata
> application profiles. This document attempts to provide some
> guidance about how to assign such identifiers.
Thanks for this.
I have some other comments which I'll send tomorrow when I get my
argument straight, but re the conclusions:
===
Of the four strategies for assigning URI references to terms listed in
this document, the use of PURLs is recommended for the identification of
elements, element refinements and encoding schemes and the use of PURLs
or "info" URIs is recommended for the identification of terms in
controlled vocabularies.
===
> Do people agree with this conclusion?
I'm not sure, but I think probably not! ;-)
> Is more justification for this conclusion required?
Yes ;-) I couldn't really find the argument for why "terms in controlled
vocabularies" should be treated differently from "elements, element
refinements and encoding schemes".
Why is an info URI appropriate for identifying a "term in a controlled
vocabulary" but not for identifying those other classes of resource? Is
the suggestion that the ability to de-reference the URI and retrieve
some useful information is less important for "terms in a controlled
vocabulary" than for the other things? (If so, I think I disagree!)
And of course, some "terms in controlled vocabularies" may also be
"encoding schemes"....
Pete
|