[tei-council] datatypes again: make data.key a URI

[Lou Burnard]

James Cummings wrote:
> Sebastian Rahtz wrote:
> 
>>> Isn't it at all likely that I'll want to apply both rather than have
>>> to choose between them?
>>
>>
>> what you're doing here is a grotesque abuse of xml:id! in your example
>> "someDocumentIDScheme" identifies this <rs>, not the "foo" thing.
> 
> 
> Ok... I must be being dense, I was assuming it was identifying the <rs> 
> element, not the 'foo'.... can't I have a database key attached to 
> something where I also want to have an ID of some sort on the element?  
> Aren't these two completely different things?
> 

This makes no sense. Have another murphys.

The <rs> can have an xml:id if you like. The <person> can too.
The purpose of the KEY attribute however is to say what <person> 
corresponds to this <rs>. It can do that by pointing to the <person>s 
ID, or by Some Other Means.