- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 Sep 2010 16:26:05 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10682
Summary: [XQ1.1] Use of the term URI in introduction
Product: XPath / XQuery / XSLT
Version: Member-only Editors Drafts
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XQuery 1.1
AssignedTo: jonathan.robie@redhat.com
ReportedBy: oliver@cbcl.co.uk
QAContact: public-qt-comments@w3.org
Section 2 of the spec contains the following definitions:
[Definition: The in-scope namespaces property of an element node is a set of
namespace bindings, each of which associates a namespace prefix with a URI,
thus defining the set of namespace prefixes that are available for interpreting
lexical QNames within the scope of the element. For a given element, one
namespace binding may have an empty prefix; the URI of this namespace binding
is the default namespace within the scope of the element.]
[Definition: Within this specification, the term URI refers to a Universal
Resource Identifier as defined in [RFC3986] and extended in [RFC3987] with the
new name IRI.]
This implies that in-scope namespace URIs must be valid URIs according to
RFC3986/3987. However it seems that we have relaxed this condition and
namespace URIs need only be strings. The first definition should probably
changed to:
each of which associates a namespace prefix with a namespace URI
and also define "namespace URI" to be a string that may or may not actually be
a URI.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 22 September 2010 16:26:06 UTC