|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XSchema Spec, Section 3, Draft 1 (Namespaces)
Simon St.Laurent wrote: > > And again, since the XSchema processor is already going to have to handle the > task of expanding namespace references in the name attributes of ElementDecl if "processors" have to do this then the (base) architecture is wrong. binding qualified names to universal identifiers is an "encoding/decoding" problem. it is not a "processing" problem. sorry to be so unequivocal here, but it is evident that i've yet to make the point clearly enough to get across. > elements, the PI is redundant and doesn't accomplish anything. The XSchema > processor is in charge of that task. We could choose to use the > less-accomplished PI instead of the XSC:Namespace element, but I see no > benefits to doing that. the suggested encoding as a XSC:Namespace is forcing the merging of two problem aspects (the notation for symbols - and - the documentation for the namespace regions) which belong separable. as you've said, i'm repeating myself too much, and without effect. i'll shut up about this 'till i figure out how to make it clear. bye for now, 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








