[tei-council] the "key" attribute

[Sebastian Rahtz]

Conal Tuohy wrote:
> Can you explain why? Do you mean because of your earlier point that
> there's no failsafe way to determine whether a @key is intended to
> represent a db record key on the one hand, or a URI on the other?
>   
yes. what does <name key="FOO"/> mean?
> If the problem with "or a URI" is as I supposed, another approach would
> be to require that @key always contains a URI
thats fine, but then we have two elements with the same "key" attribute,
but different datatypes. this just seems wrong.
> Without using http or another resolution protocol, the key could still
> be encoded in URI syntax using the "tag" URI scheme:
>
> <!-- a URI -->
> <name key="tag:nzetc.org/2007,name-121558">Conal</name>
>
>   
thats an interesting idea. bit verbose, tho?


-- 
Sebastian Rahtz      

Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431