4.1 Address types

4.1.a Should we have a single attribute used for storing all locators, 
with another attribute expressing its type, as with the initial draft's 
HREF/HRTYPE? Note that this has the side-effect that a locator element
can contain only one locator (which of course, could be a tokenized list). 

4.1.b If so, what should the attribute be called? 

4.1.c If not, should we use a different attribute for each type of locator? 
Note that this means we could in principle have multiple addresses per 
locator element although only one of each HRTYPE. 

4.1.d If using different attributes for locator languages, can we have 
multiple locators packed into locator attribute values?

4.1.e Should we discard this scheme and adopt something wholly different 
for selecting among locator languages? 

4.1.f Should we abandon the idea of different address types and assert that 
everything is a URL?  Can we do this and retain support for good old
IDREF(S) addressing?  Does XML-LINK need to subsume IDREF(S)?  This
would require packing complex addresses (e.g. TEI locators) into URLs.

Cheers, Tim Bray
tbray@textuality.com http://www.textuality.com/ +1-604-708-9592