Namespace prefixes optional?

Marcus Carr mrc at
Sun Jan 9 23:25:11 GMT 2000

rev-bob at wrote:

> That is, by defining "fragment" as belonging to namespace rbns, I am defining the
> attributes of "fragment" and the children of "fragment" as belonging to the same
> namespace by default.  With the "p" element, I declare that it belongs to the htmlns
> namespace, along with (by default) its children and attributes.  With the "b" element, for
> some reason, I need to attach an attribute from the bubbans namespace - so I mark just
> that attribute as belonging to a different space.  When "p" closes, so does the htmlns
> fragment, and the default namespace reverts back to rbns.
> Simple enough?

Perhaps too simple. :-)

In the event that you wanted to fragment your data further and the original namespace was
significant in the new context, you would meed to obtain from the higher level element and
make it explicit when you do the fragmentation. I suppose the feeling was that you can create
your data in the way that you described, then apply a simple tool to make the namespaces
explicit, and that this was preferable to requiring the manipulation when the data is being

>  Rev. Robert L. Hood  |

I'm guessing you've been quiet because Christmas is your busy period...:-)


Marcus Carr                      email:  mrc at
Allette Systems (Australia)      www:
"Everything should be made as simple as possible, but not simpler."
       - Einstein

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list