The parser would have only done that if you had enabled namespace
processing. Once you do that, the rules change and all element/attr names
can only have one colon and the text before that colon is a prefix which
must be mapped. If you are getting this without enabling namespace
processing (directly, or possibly indirectly), then something is wrong.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: Peter A. Volchek [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 8:25 AM
To: Xerces
Subject: colon in the attribute's name
Let's parse two xml documents.
1.
<A xmlns:my="http://my.http"; my:name="Peter"/>
This is parsed w/o errors. Prefix my is mapped to http://my.http, so all is
fine
2.
<A my:name="Peter"/>
The parser throws the following error:
[The prefix 'my' has not been mapped to any URI ( line 1, char 21 )]
But, in this case the colon ":" is part of attribute name rather then
namespace quailified name.
Let's look at xml rec http://www.w3.org/TR/REC-xml#NT-Name
.........
Note:
The Namespaces in XML Recommendation [XML Names] assigns a meaning to names
containing colon characters. Therefore, authors should not use the colon in
XML names except for namespace purposes,
but XML processors must accept the colon as a name character.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
..........
So, I guess, there should be no error.
Ideas?
Peter A. Volchek
Software Engineer
Metis International, Inc.
[EMAIL PROTECTED]
---------------------------------------------------------------------
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]
