MURATA Makoto wrote: > > I agree with Paul. I personally would like to drop everything that affects > information sets from the schema language. Hence, I oppose to information > set contributions, archetypes, defaults, entities, notations, .... I understand your goal but I think that that is too severe a constraint. The convenience of annotating the tree from the schema is just too large. Given a schema and a design for an application, the application designer can decide whether the application needs to be built on top of a schema processor or not. If it needs archetype, default, etc. then it must be, otherwise it does not need to be. Clearly language designers would have to start taking responsibility for performance. "If we depend on that then schema-less processing will be impossible. I think that it should always be possible to choose to see the same view that a schema-less processor would see. -- Paul Prescod - ISOGEN Consulting Engineer speaking for only himself http://itrc.uwaterloo.ca/~papresco The dress code in Las Cruces New Mexico has been tightened [to] target Gothic clothing, such as dark trench coats. "It is not a witch hunt" Superintendent Jesse L. Gozales said. "It is for the safety of the kids in our schools." - Associated Press, May 16 1999 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...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format