Cart
[Home] [By Thread] [By Date] [Recent Entries]
> That's well and good, but we can't wait until the XSchema recommendation is > finalized. XHTML is due to be finalized much earlier, and as we've seen it > depends on what the decision in XSchema will be. I don't know how the W3C > process handles such a conflict. What will happen if XHTML makes a decision, > and the XSchema draft then changes so it no longer makes sense? Which is one reason why I think XHTML should perhaps go with zero namespaces for now and the W3C should address the broader issue ASAP. Although, it could be said that the W3C *has* addressed the issue and he has already made his mind up :-) 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/ 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...)
|
