Hugh Cayless wrote on tei-council on 2013-06-20:
It is possible to have an HTTP URI which is also an identifier, and in that case, I'd argue for keeping it in
<idno>. I doubt there are any examples in the Guidelines, but it's the kind of thing we may see more of as Linked Data picks up steam. For example, the URI
http://papyri.info/biblio/8276/refdenotes an actual book, and resolves to http://papyri.info/biblio/8276, which is a bibliographic record. Worldcat ids, like
http://www.worldcat.org/oclc/185922478function in the same way, and I can easily see people wanting to use them inside
<bibl>s. I would. Maybe some thinking about the appropriate @type to use for these is warranted...
I suggest that we add "uri" as a suggested value for idno@type and gloss this value as being used for URI used as an identifier for an item without intending resolution. Giving one of these examples would be good.
While I also suspect we haven't used
<idno> this way in the Guidelines, I know that we have used @ref in this way in a few cases. For example:
<author ref="http://id.loc.gov/authorities/names/no2001067434">. I think these can stay as they are.