| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 07:27:34 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 07:27:34 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cca2bddfd8f313
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=Xyn1AFymSzr02lsCicwogUd9WUDgiWVH6U5Vd6_RP1c-1760167654-1.0.1.1-lAWkkyUT3zT1iV3BmNuBgstq1Vs1dpQErN3T5BE_CB2mfHlL_ag0MLY2IZH07B8VrvHzviK3g0RrooyUMfCIwdfiK5VilVemT2DX0kfW4Qo; path=/; expires=Sat, 11-Oct-25 07:57:34 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cca2bddfd8f313-BLR
alt-svc: h3=":443"; ma=86400
ORA-XQ-132-B: name "xmlspace" suggests an incorrect association with xml:space attribute from Stephen Buxton on 2004-02-16 (public-qt-comments@w3.org from February 2004)
ORA-XQ-132-B: name "xmlspace" suggests an incorrect association with xml:space attribute
- From: Stephen Buxton <Stephen.Buxton@oracle.com>
- Date: 16 Feb 04 13:19:16
- To: public-qt-comments@w3.org
- Cc:
- Message-Id: <200402162119.i1GLJHb07878@rgmgw4.us.oracle.com>
SECTION 4.10: xmlspace declaration The keyword "xmlspace" suggests a connection with the xml:space attribute. The user might get the idea that "declare xmlspace preserve" causes an explicit or implicit xml:space='preserve' attribute in every element constructor, and "declare xmlspace strip" causes an explicit or implicit xml:space='default' attribute in every element constructor. I don't think this is your intention; I think you intend that the user must explicitly generate any xml:space attributes, just as the user must explicitly generate any other attributes. Some keyword other than xmlspace would be preferable, perhaps "boundaryspace" or "boundary space". - Steve B.
Received on Monday, 16 February 2004 16:19:19 UTC