CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 23:30:46 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 23:30:46 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98d225aa097825e0
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=cFsafl21Xo4uoam.w7CQMUI63DJPZpLt2OLU_SA5BS0-1760225446-1.0.1.1-3AhaA7Kz7vXm5rktgICPvmfrxXy9bB.KupCHqDr7wpufOvl94c3BDLZOpjFmUcVeuY5lAVVA.vE.yFhDH.y13283Mfd_tXJgD1ux3rMBQ5Q; path=/; expires=Sun, 12-Oct-25 00:00:46 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d225aa097825e0-BLR
alt-svc: h3=":443"; ma=86400
ORA-XQ-104-B: Flagger should use XML 1.0 lexical rules even if the implementation supports X ML 1.1 from Stephen Buxton on 2004-02-16 (public-qt-comments@w3.org from February 2004)
ORA-XQ-104-B: Flagger should use XML 1.0 lexical rules even if the implementation supports X ML 1.1
- From: Stephen Buxton <Stephen.Buxton@oracle.com>
- Date: 16 Feb 04 11:53:03
- To: public-qt-comments@w3.org
- Cc:
- Message-Id: <200402161953.i1GJr3214772@rgmgw6.us.oracle.com>
SECTION 2.6.6.1: XQuery flagger To assure portability, the flagger must adhere to the XML 1.0 lexical rules, since it is impossible to know whether the platform to be ported to will use XML 1.0 or XML 1.1. Note that Section A.2 "Lexical structure" says that implementations can use either XML 1.0 or XML 1.1 conventions. - Steve B.
Received on Monday, 16 February 2004 14:53:06 UTC