| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 01:19:08 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:50:22 GMT
cache-control: max-age=2592000, public
expires: Sun, 09 Nov 2025 12:17:48 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c60e83faddcf88
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=.mNIKgPN11tL7vecgYAgoP.raxdWw8L4yp4AVa0FtuU-1760145548-1.0.1.1-7WvjYsmPCBysJAyx_ZIk0nbmo4YqeDnqPqMt_UaS232YOPWzEYIp._g6nGE3rgBDZg7XZggQ5a2mKsBy0v61i5odTNllysoIUdqhyHDrw5w; path=/; expires=Sat, 11-Oct-25 01:49:08 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ca87071a4dc169-BLR
alt-svc: h3=":443"; ma=86400
[XPath] Incompatibilities with XPath 1.0 from Martin Duerst on 2004-02-13 (public-qt-comments@w3.org from February 2004)
[XPath] Incompatibilities with XPath 1.0
- From: Martin Duerst <duerst@w3.org>
- Date: Fri, 13 Feb 2004 12:16:41 -0500
- To: public-qt-comments@w3.org
- Message-Id: <4.2.0.58.J.20040211174135.028e6fd0@localhost>
I'm quite frightened by the long list of incompatibilities (even despite a special compatibility switch) between XPath 1.0 and XPath 2.0. Each of these items seems to be small, but overall, this has a large potential for confusion, subtle errors, and so on. Not a big problem for a spec, but a potential nightmare for deployment. My guess is that to avoid this, implementations will probably implement both XPath 1.0 and XPath 2.0. If that's the case, it would be easier to make the compatibility switch switch all features, rather than just part of them. Bringing XPath 1.0 and 2.0 closer together would be even better. Regards, Martin.
Received on Friday, 13 February 2004 12:17:06 UTC