| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 13:16:32 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: Mon, 10 Nov 2025 13:16:32 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cea1e82b680bc9
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=8spSwiP_EmQgItZ6XhDcp9fMT5HzYBmw2FBh_DPeRA8-1760188592-1.0.1.1-rlfFosZBX9EiIWuRTeeSD.or2PwacQQoFCY8EKvHfnir5cJBFnaQ0lIQ1CpQ3uKuwb4kNWClo9Mm87NULYazWhJtGKCF3HWo8oGFA_CJHdM; path=/; expires=Sat, 11-Oct-25 13:46:32 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cea1e82b680bc9-BLR
alt-svc: h3=":443"; ma=86400
ORA-XQ-216-E: Explanation of initial /, // and non-initial / and // as path separators in abreviation from Stephen Buxton on 2004-02-16 (public-qt-comments@w3.org from February 2004)
ORA-XQ-216-E: Explanation of initial /, // and non-initial / and // as path separators in abreviation
- From: Stephen Buxton <Stephen.Buxton@oracle.com>
- Date: 16 Feb 04 13:51:39
- To: public-qt-comments@w3.org
- Cc:
- Message-Id: <200402162151.i1GLpd219969@rgmgw6.us.oracle.com>
SECTION 3.2.4: Abbreviated Syntax 3.2.4, bullet 3, gives an explanation of // as being effectively replaced by /descendant-or-self::node()/ However, this is only true for // used in non-initial positions. If // is used at the beginning of a path expression, it is effectively replaced by fn:root(self:node()) treat as document-node()/descendant-or-self::node() as explained in 3.2 Path Expressions. So we need to make it clear here. Or repeat the abbreviation of the initial '/' and '//' here in 3.2.4 as well. - Steve B.
Received on Monday, 16 February 2004 16:51:41 UTC