Effective Element Name == "Expanded Name"
Andrew, You wrote al> The "effective element name" is illustrated in section 6.3 of the proposed al> spec. Unfortunately, what is lacking in section 6.3 of the proposal, is a clear statement of the semantics of an "Expanded Name." >From your remark, I take it that you agree that the "meaning" of an element is governed by the expanded name and that the particular prefix used in a document is irrelevant. That is good news. To define the semantics of namespaces, if you said something like: Namespace conformant applications treat elements as if their ELEMENT TAG were the Expanded Name then you would have defined how DTD validators are to treat documents with namespaces. As it stands, the consensus on XMLDEV seems to be that documents with namespaces are validated by "ignoring the meaning of the xmlns prefix." So, <PN:NAME> is validated without regard to what the PN prefix is actually defined to represent. The statements xmlns:PN="someMeaning" seem to be ignored, and namespace defaulting cannot be used. -- Mark 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