On 15-02-05 03:00 AM, Martin de la Iglesia wrote:
> Am 03.02.2015 um 14:45 schrieb Martin Holmes:
>> Exactly. The TEI (or of course the customizing user) is responsible
>> for defining what is a URI and what isn't:
>> "This specification does not attempt to specify which text strings in
>> a document are to be interpreted as URIs. That is the responsibility
>> of each XML vocabulary. The question addressed by this specification
>> is: given a relative URI in an XML document, what base URI is it
>> resolved against?"
>> I believe that if you were to define the content model of <idno> to be
>> a URI, then you should expect a schema-aware XML processor to expand
>> that URI appropriately based on the @xml:base attribute on the element
>> (since the element content is a text node which is its descendant).
>> But like Piotr, I'd be intrigued to know if that actually works with
> Wouldn't it be desirable to be able to specify in the TEI document
> itself (rather than in the ODD) what is a URI and what isn't?
To the TEI, a URI is a specific datatype, based on xsd:anyURI:
The ODD/schema seems the right place for that kind of definition.