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

RE: XPath conformance? was RE: storing XML files

• From: Chris Parkerson <chrisp@e...>
• To: 'Evan Lenz' <elenz@x...>,"'Champion, Mike'" <Mike.Champion@S...>, xml-dev@l...
• Date: Tue, 09 Oct 2001 13:29:11 -0400

Agreeing with Evan, the way to extend XPath is to use XPath extensions
as defined by the W3C.  The way to extend XSLT is to use XSLT
Extensions.  It's very nice to have that capability (something missing
from many other standards that can be argued made their acceptance
limited).  I've seen use of these extension capabilities done in many
useful ways, both in XYZFind's product as well as other products.  Being
"creative" with and "extending" the CORE syntax of a language has caused
problems in the SQL world, caused the object database world to never
agree on standards (OQL... YIPE!), as well as fights in other realms.
Microsoft couldn't beat Java, couldn't claim ownership to C++, so now we
have C#... go figure ;->

As far as taking it to xmldb@x..., that would be fine, but that
would also imply that the issues here are completely separable from
issues facing XML technologies in general.  I do not believe that is the
case given the infancy of everything XML.  We are intertwined, and
issues such as this do not affect just the niche of the XML database
market.

Cheers,
Chris

---------------------------------------
Chris Parkerson
Product Manager
eXcelon Corporation
Burlington, MA
(781) 674-5393
http://www.exceloncorp.com
---------------------------------------


-----Original Message-----
From: Evan Lenz [mailto:elenz@x...] 
Sent: Tuesday, October 09, 2001 1:08 PM
To: Champion, Mike; xml-dev@l...
Subject: RE: XPath conformance? was RE:  storing XML files

Mike Champion wrote:
> I'd submit that a processor that executes legal XPath expressions "is"
an
> XPath processor, whatever it's called, and whatever superset of
> XPath syntax
> it also supports.

Because XPath can be extended via an extended function library, a la
XSLT
and XPointer, I would disagree with the claim that a processor that
supports
an extended *syntax* is in compliance with the XPath specification.

There are parts of the picture that are not standardized--most notably
how a
node-set (or even a boolean, for that matter) should be serialized.
These
are implementation-dependent (whether the implementation is the XSLT
specification or some XML database vendor).

This leaves vendors much freedom (at the expense of having a standard).
However, they should not feel free to extending the syntax of XPath,
i.e.
what the XPath spec *does* standardize.

For example, the following is not in compliance with the XPath spec:

/customer[name ~= "Mike"]

whereas this alternative expression would be perfectly fine:

/customer[ext:like(name, "Mike")]

Evan Lenz
XYZFind Corp.


-----------------------------------------------------------------
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 elist use the subscription
manager: <http://lists.xml.org/ob/adm.pl>

• References:
  • RE: XPath conformance? was RE: storing XML files
    • From: Evan Lenz <elenz@x...>

• Prev by Date: Re: Adam Bosworth on XML and W3C
• Next by Date: RE: Adam Bosworth on XML and W3C
• Previous by thread: RE: XPath conformance? was RE: storing XML files
• Next by thread: Re: XPath conformance? was RE: storing XML files
• Index(es):
  • Date
  • Thread