From: "Karen Coyle" <[log in to unmask]>
> it's easier for a human to key
> <typeOfResource>cartographic</typeOfResource>
> than
>
>
<typeOfResource>info:xv/1/mods/resourceType/1/cartographic</typeOfResource>
Sorry, I overstated when I implied you'd *have to* supply a URI (which
would be the case if the type were changed to 'anyURI' -- which I did say);
actually 'cartographic' could be supplied (so ignore my earlier statement
that we would use anyURI and assume instead 'string'), assuming that the
prefix is defaulted, in this case 'info:xv/1/mods/resourceType/1/'. Or, for
special applications the user could change the default, say to
'info:xv/1/mods/resourceType/2/' if all the values were to be from that
list. (The trick is to get editors to support this. But that's not going
to happen until we develop it.)
> And I'd rather look at a list that goes:
> textual
> cartographic
> manuscript
>
> than
> info:xv/1/mods/resourceType/1/textual
> info:xv/1/mods/resourceType/1/cartographic
> info:xv/1/mods/resourceType/1/manuscript
Absolutely. That's would be the idea behind the default prefix.
> This proposal does not have an authority list, ......
Yes it does (unless I misunderstand what you mean by an authority list).
Consider these three URIs:
info:xv/1/mods/resourceType/1/cartographic
info:xv/1/mods/resourceType/2/cartographic
info:xv/1/mods/resourceType/3/cartographic
where 'cartographic' has three different meanings and is correspondingly on
three different lists.
In the first, 'cartographic' comes from a core list (the '1' identifies the
authority), in the second and third '2' and '3' respectively identify the
authorities.
--Ray
|