|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XML formality (was: What is PI data exactly?)
>>I think the problems are particularly acute >>when the spec tries to talk about the actions of "XML processors" or >>"applications" because these notions are very fuzzy. > >That is not true at all. The processor and the application are cleanly >defined. The definition of conforming validating and non-validating processors in section 5 is reasonably OK, subject to "a reasonable man's" interpretations of certain words, especially the verbs "to report" (is an XML processor allowed to allow the application to suppress the error reports?) and "to process" (is the XML processor required to reveal the results of its processing or can it throw it all away, or mangle it in some way after processing?). A formal spec of an API such as SAX or DOM would be much cleaner. By contrast the defining occurrences of the terms processor and application in section 1 (to which hyperlinks point) are hopeless, since they don't define the boundary between the XML processor and the application: they don't tell me, for example, whether my SAXON library is part of the XML processor or part of the application. Mike Kay 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...)
|
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
|
|||||||||

Cart








