[tei-council] facsKey agayne

[Lou Burnard]

That is the proposal, yes. The syntax of data.URI supports functionality 
equivalent to (or better than) data.key, so we can combine the two in 
one attribute,

Laurent Romary wrote:
> These (with the urn comment) are good points. Do you mean we could/ 
> should have a uniform mechanism for pointers and keys in general?
> 
> Le 9 févr. 10 à 00:17, Sebastian Rahtz a écrit :
> 
>> A couple of conversations outside my office this afternoon suggest  
>> that people who want
>> to use @facs to point to an arbitrary identifier can do so trivially  
>> by making up their own
>> protocol. Thus
>>
>> <p facs="#foo">
>>
>> is short for the normal HTTP
>>
>> <p facs="http://$basedoc#foo">
>>
>> but
>>
>> <p facs="tk:foo">
>>
>> is equally a legal URI, where "tk" is a new adhoc protocol. Examples  
>> at
>> http://en.wikipedia.org/wiki/URI_scheme#Unofficial_but_common_URI_schemes
>> show similar ideas - the "doi:" protocol is like this, since it  
>> references
>> an arbitrary identifier which does not get resolved to some web  
>> address.
>>
>> Using @facs in this way is much better than @facsKey, IMHO, because  
>> it signals
>> clearly to the processing application what is going on, but does not  
>> need a new
>> attribute. It means the user can make use of _several_ protocols in  
>> the same
>> document.
>>
>> Or is all this completely mad?
>> --
>> Sebastian Rahtz
>> Information Manager, Oxford University Computing Services
>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>
>> Sólo le pido a Dios
>> que el futuro no me sea indiferente
>>
>>
>>
>>
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council