CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 02:29:37 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 02:29:37 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98caee472c04b277
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=r5D.iVr8ph8CDxvcVoPMsTbLZx6t5WFbjeYKOnXriKM-1760149777-1.0.1.1-KSxxcx.cksv0ah2kWAQXmNTbll3dfdsxGIoCG5VNyhDFcEkk4N11aoj0aNsTXVOhXHC0gqeMKuegIs_3vKnO6.tbMC62TISqsH2LD75booI; path=/; expires=Sat, 11-Oct-25 02:59:37 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98caee472c04b277-BLR
alt-svc: h3=":443"; ma=86400
[XQuery] IBM-XQ-003: New term for in-scope namespaces from Don Chamberlin on 2004-02-11 (public-qt-comments@w3.org from February 2004)
[XQuery] IBM-XQ-003: New term for in-scope namespaces
- From: Don Chamberlin <chamberl@almaden.ibm.com>
- Date: Wed, 11 Feb 2004 15:49:21 -0800
- To: public-qt-comments@w3.org
- Message-ID: <OFF209AD92.178ABB97-ON88256E37.007FB0F1-88256E37.0082DD71@us.ibm.com>
(IBM-XQ-003) At present, our documents are inconsistent in their use of the term "in-scope namespaces". In the XPath and XQuery documents, "in-scope namespaces" is part of the Static Context and is a property of an expression. On the other hand, in the Data Model and Functions and Operators documents, "in-scope namespaces" is a property of an element and has another meaning entirely. The term "in-scope namespaces" appears13 times in the Data Model document and 10 times in F&O document. I think we should fix this inconsistency by changing the term "in-scope namespaces" in the Static Context to "declared namespaces" and using this term throughout the XQuery and XPath documents. The term "declared namespaces" suggests where the information comes from: either a namespace declaration in the Prolog, or a namespace declaration attribute. In this solution, no changes are needed to the Data Model and F&O documents. --Don Chamberlin
Received on Wednesday, 11 February 2004 18:49:38 UTC