Cart
[Home] [By Thread] [By Date] [Recent Entries]
james anderson wrote: > It should well be published as an interface which makes use of the > prefix<->uri map, with the restriction that either it depends the dynamic > context - and as such is unambiguous I think this mechanism is the only meaningful one, which was why I spoke of the *current* (viz. at a given point in the document) map. > To depend on the prefix-URI bindings outside of the dynamic context is to > permit erroneous results. True. > It suffices to permit the application to process > names in the parser's dynamic context. To this end it need no explicit access > to the prefix<->uri map, just to an interface which interns qualified names > given the parser's dynamic context. Probably sufficient; it may be, however, that there is an occasional need to generate a currently-correct Qname from a URI+NCName. -- John Cowan http://www.ccil.org/~cowan cowan@c... You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5) 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...)
|
