Cart
[Home] [By Thread] [By Date] [Recent Entries]
>I don't like telling people they can use DOCTYPE or XSchema PIs but not both. I >also don't like having to write a long list of conflict resolutions -- it just >makes XSchemas harder to use. In both cases, it feels like we are imposing >requirements not in the XML spec. Ideas? Perhaps the simplest way to deal with this is to leave roots _out_ of the XSchema PI. I always thought it was kind of silly to declare it in DOCTYPE - after all, the root element should be the first and last thing you see in a document, and an application should be able to figure it out. It seems to me like redundancy, though there may be reasons for it which I haven't fathomed. The other reason for ignoring roots is that we _can't_ change DOCTYPE, so I think we'd better just stay out of its way. Simon St.Laurent Dynamic HTML: A Primer / XML: A Primer / Cookies 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...)
|
