[
Lists Home |
Date Index |
Thread Index
]
- From: "Hill, Les" <lhill@excelergy.com>
- To: 'David Megginson' <david@megginson.com>
- Date: Mon, 20 Dec 1999 16:43:54 -0500
David Megginson writes:
> Hill, Les writes:
> > startNamespace("foo")
> > startNamespace("baz")
> > startElement("bar", atts)
> >
> > which namespace is "bar" in?
>
> That's a separate question -- the idea of the original suggestion is
> that NamespaceContext would not be nested -- in the worst case, there
> would have to be start/endNamespaceContext events for every element.
> This is separate from the question of reporting the scope of
> Namespace
> declarations.
I must have missed that nuance. In fact I am still missing it :)
If the element name has its own contextual information (i.e. using compound
names+), then yes, the namespace scoping is orthogonal. If the element name
does not have the contextual information, then namespace scoping is crucial.
Unfortunately, startNamespace()/endNamespace() isn't good enough (see above
:)
What am I missing?
+The original event sequence read as using simple Strings and NOT using
compound names mostly due to the second sequence in the message explicitly
identifying the namespace.
Regards,
Les Hill
Senior Architect
Excelergy
=======================================================
Excelergy is hiring Java/C++ XML developers, all levels
send resume (and mention me :) to jobs@excelergy.com
=======================================================
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|