>> What's the best way for a document to announce to its consumers what the @type attribute in <idno> means? How to say, for example, that a @type of "ASIN" refers to an Amazon catalog number and not an Australian Serials number? How to do for idno @type vocabularies what XML namespace declarations do for namespace abbreviations?
>> I have in mind a machine-readable form, not just a prose statement.
> you're opening a fairly big can of worms here, in wanting machine-readable definitions of @type? but working with a system like http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-cRefPattern.html would seem to be the way to start going.
> whether anyone has ever implemented that, I'd not like to put money on...
> Sebastian Rahtz
Implementing cRefPattern would be straightforward enough. But what about
the more general question: How should one encode what cataloging (er,
cataloguing) system @type refers to? Something in <tagUsage>? in
<classDecl> seems better. The Guidelines say it documents classifiation
schemes used in the header, but the specification says "elsewhere in the
text", so I guess it's OK.
Something like this?
<idno @type="OCLC"> </idno>
< >http://worldcatlibraries.org</ > <-- something like an XML
<cRefPattern> </cRefPattern><-- if the cataloging
authority offers lookup
But nothing there unambiguously ties the @type to that taxonomy.
Something needs to map @type to a data.pointer pointing to the taxonomy
Or maybe a <typeDecl> as a sibling of <classDecl>?