Cart
[Home] [By Thread] [By Date] [Recent Entries]
The chorus has spoken: >> > In aid of this, I am PROPOSING that we not use any ID attributes >> > in XSchema 1.0; change the "id ID #REQUIRED" attributes in ElementDecl >> > elements to "name NMTOKEN #REQUIRED" instead. That will allow us >> > to reserved XML IDs for structure-sharing. >> >> I like this idea. > >Ditto. It looks like the XSchema app is going to have to do half the work >anyway, so there's no point in limiting ourselves with IDs. I'll make the change. I think this opens up XSchema dramatically, making possible and eventually compatible the currently-proposed nested model, Paul's rule based model, and several of the ideas I've seen for re-creating parameter entities. The key in my mind remains making the declarations referenceable; the rest we can handle in successive specifications as needed. I think we have a great start here. 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...)
|
