[tei-council] the "key" attribute

James Cummings James.Cummings at computing-services.oxford.ac.uk
Mon May 21 06:47:21 EDT 2007


Sebastian Rahtz wrote:
> James Cummings wrote:
>>  In most other cases does having a choice of target
>> or key make sense? What's the logic of making them mutually exclusive? 
> to assist processors. If I see both, which do I operate on?

Whichever you know how to handle?  I view them sort of as different things.
 To me @key gives a record that can (if understood) be used to provide more
information about the element content, whereas @target provides a reference
to something.  i.e. the first is a key for metadata, while the second is
more a form of transclusion and/or citation.  But, thinking about it, maybe
that isn't really much of a distinction.

Are you proposing that anywhere that @target exists, this could be replaced
by a mutually exclusive @key?  i.e. <ref key="DB123">ref</ref> ?

-James
-- 
Dr James Cummings, Oxford Text Archive, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk



More information about the tei-council mailing list