• To: <uche.ogbuji@f...>,"'Jeni Tennison'" <jeni@j...>
• Subject: RE: XPath/XSLT 2.0 concerns
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Mon, 7 Oct 2002 09:22:17 +0100
• Cc: "'David Rosenborg'" <darolst@p...>,<xml-dev@l...>
• Importance: Normal
• In-reply-to: <E17yRbc-0004t9-00@m...>
• Reply-to: <michael.h.kay@n...>

> I think this hints at the missing link for me in this idea of 
> using axes for 
> XPath m12n.  It's the fact that they operate only in terms of 
> nodes (or, 
> really, node sets). 

Yes, I think one thing we've learnt from the problems with "namespace
nodes" is that representing all information in terms of nodes is a bad
idea, because nodes carry too much baggage - they have identity, they
belong to a document, they have a parent. Can two elements in different
documents share a "type node"? If the context item is a "type node",
what is the value of "/"?

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s... 

• Follow-Ups:
  • Re: XPath/XSLT 2.0 concerns
    • From: "David Rosenborg" <darolst@p...>

• References:
  • Re: XPath/XSLT 2.0 concerns
    • From: Uche Ogbuji <uche.ogbuji@f...>

• Prev by Date: Re: XPath/XSLT 2.0 concerns
• Next by Date: Re: heritage (was Re: SGML on the Web)
• Previous by thread: Re: XPath/XSLT 2.0 concerns
• Next by thread: Re: XPath/XSLT 2.0 concerns
• Index(es):
  • Date
  • Thread