Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Megginson wrote: > > As a developer, I believe that this is a seriously broken idea: we > need a single HTML Namespace URI so that we can identify and process > HTML markup embedded in other document types; if we have to check > three or more qualified names just to figure out that we have an HTML > <p> element (and write three separate patterns in XSL, etc.) then > we're in serious trouble. I think that if the three different namespaces happen be interchangable for the purposes of YOUR process then it is YOUR responsibility to say so. This implies that XSLT, Namespace-filters for SAX, DOM etc.need extensions for stating that two namespaces are interchangable for a given task. Yes, there should also be a way for a namespace creator to globally state that a namespace is a subset of another namespace but the lack of such a declaration cannot be blamed on the XHTML people. They are trying to do the right thing. Paul Prescod 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/ and on CD-ROM/ISBN 981-02-3594-1 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...)
|
