Again, xmlns="" puts an element in no namespace. That already works in
SimpleXML. There is no issue here that needs fixing.
IIUC, the OP doesn't want the element to be in no namespace, but wants
it to be in the default namespace, but unprefixed.
I have already laid out my reasons for believing requiring this in a
schema, although perhaps formally possible, goes against the XMLNames
spec. I won't repeat those reasons here. Suffice it to say that I don't
think anything needs fixing either.
However, there is something you cannot currently do with SimpleXML, and
that is add an unprefixed element that falls in the default namespace.
And although I don't think it's a bug that needs fixing, it wouldn't
hurt to add that functionality with something like:
$r->addChild("child",null,SIMPLEXML_DEFAULT_UNPREFIXED);
This adds a certain ambiguity to document creation if it is used, but it
does add functionality not currently there. I guess it's only worth
doing if there are specs out there in the wild that (wrongly IMHO)
require "unqualified" names in XMLNames-conforming documents.
So, if the OP or his associates are in control of his schema, I suggest
he should change it; if he can point to a respectable public schema that
does this, it would be worthy of greater consideration.
Ben.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
