My take on this is that it's simply a bug in our parser. My guess is
that, because PI target names are defined to be XML Names, we use the
same piece of code to check on it as we use everywhere else. When
namespace support was added this special case was overlooked.
I don't see on what ground the parser would barf like it does. In the
second revision of the XML 1.0 spec we actually added the following note
[1]:
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.
[1] http://www.w3.org/TR/REC-xml#dt-name
--
Arnaud Le Hors - IBM Cupertino, XML Strategy Group
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
