Lists Home |
Date Index |
in order to properly mix two namespaces:
Why would one want to do this? What advantages would it afford? In what
scenarios would it be useful?
Booz | Allen | Hamilton
Jeff Lowery wrote:
> Speaking of reckless recommendations, has anyone previously given thought to
> namespaces of the form:
> <np1:root xmlns:np1="http://www.example.com/ns1"
> <np2:np1:baz/> <!-- this one -->
> I know this is disallowed by Namespaces in XML Rec, but to me it could be
> helpful for the types of namespace mixing pointed out by Arjun Ray awhile
> For the np2:np1:baz element above, the local name baz is interpreted to be
> qualified by three distinct namespaces: ../ns1, ../ns2, and the hybrid
> ../ns1|../ns2 (signified by either np1:np2:baz for np2:np1:baz; order of
> qualification is irrelevant).
> The point is not to solve the problem of needing some semantic knowledge in
> order to properly mix two namespaces: some function still needs to know
> which elements get tagged with both their original namespace and the
> overarching namespace. But it at least allows just _one_ function to have to
> know-- the rest can just stupidly parse the qualified names, with awareness
> of either one or both qualifiers.
> Just thinking out loud...
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
fn:Joseph M. Chiusano