Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: SV: no targetNamespace, elementFormDefault qualified

From: noah_mendelsohn@--.---.---
To: "Bryan Rasmussen" <BRS@----.-->
Date: 4/3/2006 3:01:00 PM
Bryan Rasmussen writes:

> Should there be an xmlns:blank="" perhaps to actively qualify 
> the non-namespace qualified elements?

Well, while this could perhaps have been done, the namespaces 1.1 
Recommendation is very clear on this point.  From [1]:

"The empty string, though it is a legal IRI reference, cannot be used as a 
namespace name."

furthermore:

"The use of relative IRI references, including same-document references, 
in namespace declarations is deprecated."

So, "" is by design not usable as a namespace name.  If "" were a 
namespace name, its use would be deprecated at very least because it would 
be a relative URI.  Furthermore, there's already a ton of software 
deployed that understands the above as doing something else. [2]:

"The attribute value in a namespace declaration for a prefix MAY be empty. 
This has the effect, within the scope of the declaration, of removing any 
association of the prefix with a namespace name."

If the above syntax were used, then we'd need another way to unbind a 
namespace declaration. [2] 

For all those reasons, my personal opinion is that this isn't going to 
happen. 

Noah

[1] http://www.w3.org/TR/xml-names11/#iri-use
[2] http://www.w3.org/TR/xml-names11/#scoping

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------





From BRS@i... Tue Apr 04 08:41:05 2006
Received: from aji.w3.org ([133.27.228.225])
	by


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent