[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Effective Element Name == "Expanded Name"

• From: Mark Tucker <mct@f...>
• To: xml-dev@i...
• Date: Wed, 9 Sep 1998 13:34:34 -0500 (EST)

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...)

• Prev by Date: Re: HTML != XML (was Re: [ANN] Kludgey workarounds for xt)
• Next by Date: Are elements allowed to nest within themselves?
• Previous by thread: Namespace Prefix should be Purely Convienience
• Next by thread: Are elements allowed to nest within themselves?
• Index(es):
  • Date
  • Thread