[Home] [By Thread] [By Date] [Recent Entries]
Paul Prescod wrote: > XML attributes will probably have relative URLs in them and the XML > Application will have to know how to resolve them. This reminds me of another reason why you need positional information even in a simple interface. Suppose you have a document doc.xml that references an external parsed entity chapters/3.xml and suppose chapters/3.xml contains some element with an attribute that is a relative URL "4.xml". I would claim that the appropriate URL to use as the base for resolving that relative URL is the URL of the resource that contains the URL, so that relative to the document URL, that relative URL should be interpreted as chapters/4.xml rather than 4.xml. But unless the parser passes through positional information, there's no way an application can do this. I think apps are going to need at least: startExternalEntity(URL url) endExternalEntity() James xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|

Cart



