"The prefix xmlns is used only for namespace bindings and is not itself
bound to any namespace name."
Doh! Maybe I remembered wrong and it was *this* one that I ended up
assigning to a proprietary URL when its used like "xmlns:foo", since it is a
namespace prefix and it cannot map to "" since that indicates its in the
global namespace. That's probably it, so you can probably ignore that other
whole conversation, though you can probably now complain that this isn't
right either. But given that we have to report them (for recreation of the
document), and that it cannot map to the empty URL, it had to map to
something for practical purposes.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: David E. Cleary [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 02, 2001 1:09 PM
To: [EMAIL PROTECTED]
Subject: RE: A different namespace issue, bug?
> When I run this through the SAX2 parser interface for Xerces,
> with default feature settings (which means namespace processing
> is on), I get the following fatal error:
>
> Fatal Error: The prefix 'xlink' has not been mapped to any URI#114 (3:29)
>
> I believe this is an overzealous interpretation of the XML and
> Namespace specs. Just because an XML name has ":" in it does not
> mean it is a qualified name in some namespace.
I disagree. From the current Infoset WD:
<Quote>
XML 1.0 documents that do not conform to [Namespaces], though technically
well-formed, are not considered to have meaningful information sets. That
is, this specification does not define an information set for documents that
have element or attribute names containing colons that are used in other
ways than as prescribed by [Namespaces].
Furthermore, this specification does not define an information set for
documents which use relative URI references in namespace declarations. This
is in accordance with the decision of the W3C XML Plenary Interest Group
described in [Relative Namespace URI References]. Thus the value of a
[namespace name] property is always an absolute URI with an optional
fragment identifier.
</Quote>
And if you follow that directly to Namespaces, you get:
<Quote>
Namespace Constraint: Prefix Declared
The namespace prefix, unless it is xml or xmlns, must have been declared in
a namespace declaration attribute in either the start-tag of the element
where the prefix is used or in an an ancestor element (i.e. an element in
whose content the prefixed markup occurs). The prefix xml is by definition
bound to the namespace name http://www.w3.org/XML/1998/namespace. The prefix
xmlns is used only for namespace bindings and is not itself bound to any
namespace name.
</Quote>
So this certainly isn't overzealous interpretation.
> I believe a more correct intrepretation would be that if no
> matching xmlns declaration can be found in the scope of the XML
> name, the name should be treated as an unqualified ordinary name,
> just like "a" and "b" in the rest of the sample.
>
> Compromise: make it a Warning rather than a Fatal Error.
The right thing to do is to turn off namespace processing if you don't want
namespace processing.
David Cleary
Progress Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
