[tei-council] the "key" attribute

[Sebastian Rahtz]

Syd Bauman wrote:
> While I'd be fine with adding a new attribute in the naming contexts
> that is explicitly a URI reference to the regularization or
> disambiguation information, I would be very hesitant to completely
> remove key= and thus the capability to refer to databases that are
> not addressable via URI. 
so this is possibly

 6a. allow any (but  only one) of @target, @key and @lookup on the
object elements

or, more likely,

 6b. allow either (but  only one) @target or @lookup on the
object elements

You may well be right, though, that we should take @key away from 
specDesc, memberOf
and moduleRef and give them @teiKey instead. It would be a pain, because 
people
_have_ been using Odds and have their customization files, and I'd have 
an unpleasant
evening scouring ODD software for @key; but it is doable, and we could 
justify it to the
world.

in which case, I'd be happy with

 7. give the TEI ODD elements a new @teiKey, and allow the object elements
a choice of @key or @target. @key keeps its vague semantics of "a 
database lookup
key"

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