CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 07:28:00 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:59 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cca35b786b3e92
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=UEl_op2EmYd_iCafovjPEYqJs_XP0HLKzIh4aYzXdwo-1760167680-1.0.1.1-A45kWh9AxqszMJ1of5j8IE42RjS.D.LcXdacg._LzjHle8CDOU5M5z_uaQV9tt6kSKUJUJLmdnnBG3qReV5qX8YIxZLgVJ4YqbwaQ1k_7hY; path=/; expires=Sat, 11-Oct-25 07:58:00 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cca35b786b3e92-BLR
alt-svc: h3=":443"; ma=86400
ORA-XQ-089-Q: Are all XQuery errors in the xdt namespace? from Stephen Buxton on 2004-02-16 (public-qt-comments@w3.org from February 2004)
ORA-XQ-089-Q: Are all XQuery errors in the xdt namespace?
- From: Stephen Buxton <Stephen.Buxton@oracle.com>
- Date: 16 Feb 04 11:42:34
- To: public-qt-comments@w3.org
- Cc:
- Message-Id: <200402161942.i1GJgYb05847@rgmgw4.us.oracle.com>
SECTION 2.5.2: Handling dynamic errors Third para, second sentence: "For example, an error value might be an integer, a string, a QName, or an element." In Functions and Operators section 3 "The error function" second para third sentence, it says "Each error defined in this document [ie, F&O] is identified by an xs:QName that is in the namespace associated with the xdt: prefix." This seems like a good convention, that all dynamic errors specified by the W3C specification are QNames in a single namespace. It would be good if the rest of the specifications in the XQuery suite adhered to the same convention. This may well be your intent already, in which case the sentence I started with, "For example, an error value might be an integer..." should be construed as referring to values permitted to a user invocation of fn:error. However, in the context in which it appears, it seems to be referring to dynamic errors specified by the XQuery language specification. - Steve B.
Received on Monday, 16 February 2004 14:42:37 UTC