[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPath/XSLT 2.0 concerns

• To: Jeni Tennison <jeni@j...>
• Subject: Re: XPath/XSLT 2.0 concerns
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Mon, 07 Oct 2002 00:42:36 -0600
• Cc: "David Rosenborg" <darolst@p...>, xml-dev@l...
• In-reply-to: Message from Jeni Tennison <jeni@j...> of "Fri, 04 Oct 2002 13:09:12 BST." <91680579912.20021004130912@j...>
• Sender: uche.ogbuji@f...

> So for example a W3C XML Schema module could declare the axis
> "xs:type" to get a node representing the type definition of the
> context node. A RELAX NG module could declare the axis
> "rng:annotation" to get nodes representing the annotations on the
> definition of the context node, if there are any. And so on, as
> appropriate for the schema language.

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).  For instance, what would the node look like that 
represents WXS type info?  Is it just a text node whose string value is the 
type URI?  If so, then why not just make it a string?  I suppose it might be a 
node in order to be able to represent facets and the like.  I'd have to think 
about that hard from both a user and implementor POV.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Apache 2.0 API - http://www-106.ibm.com/developerworks/linux/library/l-apache/
Python&XML column: Tour of Python/XML - http://www.xml.com/pub/a/2002/09/18/py.
html
Python/Web Services column: xmlrpclib - http://www-106.ibm.com/developerworks/w
ebservices/library/ws-pyth10.html

• Follow-Ups:
  • RE: XPath/XSLT 2.0 concerns
    • From: "Michael Kay" <michael.h.kay@n...>

• References:
  • Re: XPath/XSLT 2.0 concerns
    • From: Jeni Tennison <jeni@j...>

• Prev by Date: Re: XPath/XSLT 2.0 concerns
• Next by Date: Re: XPath/XSLT 2.0 concerns
• Previous by thread: Re: XPath/XSLT 2.0 concerns
• Next by thread: RE: XPath/XSLT 2.0 concerns
• Index(es):
  • Date
  • Thread