This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4396 - Note on QName considered misleading or false
Summary: Note on QName considered misleading or false
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.0/1.1 both
Hardware: Macintosh All
: P1 normal
Target Milestone: CR
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: cluster: QNames
Keywords: decided
Depends on:
Blocks:
 
Reported: 2007-03-15 17:40 UTC by C. M. Sperberg-McQueen
Modified: 2009-04-20 17:19 UTC (History)
2 users (show)

See Also:


Attachments

Description C. M. Sperberg-McQueen 2007-03-15 17:40:51 UTC
Both 1.0 and 1.1 have a Note in the section on QNames which reads:

    Note:  The mapping between ·literals· in the ·lexical space· 
    and values in the ·value space· of QName requires a namespace 
    declaration to be in scope for the context in which QName is used.

Read literally, this appears to say that given a schema containing

    <xsd:attribute name="my-qname" type="xsd:QName"/>

then in the document

    <test tns:my-qname="foo"/>

there is no mapping for "foo", because there is no namespace
declaration anywhere around.  I think that that's (a) not a good idea
and (b) not what we intended.  The Note should be changed to say
something like "The mapping ... depends on the set of namespace
declarations in scope."
Comment 1 C. M. Sperberg-McQueen 2008-05-30 04:07:29 UTC
The issue raised here appears to be one of clarity, not one of changing
the intent of the spec.  So I'm unilaterally classifying it editorial.
This may have the effect of making it possible to take care of this
problem after publication of our next working drafts.
Comment 2 C. M. Sperberg-McQueen 2009-04-13 00:48:03 UTC
A wording proposal intended to resolve this issue is at

  http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.b3264.html
  (member-only link)

It should be noted that (if the keywords are not out of date) the WG has not
formally accepted this bug report as an issue, so the WG is not committed to
changing the spec in order to resolve it, or to the idea that the issue reported
on is a real issue.
Comment 3 David Ezell 2009-04-17 16:26:12 UTC
4396: Note on QName considered misleading or false
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.b4396.html

Summary: proposes to replace current text

     Note: The mapping between ·literals· in the ·lexical space·
     and values in the ·value space· of QName requires a namespace
     declaration to be in scope for the context in which QName is
     used.

with

     Note: The mapping between ·literals· in the ·lexical space·
     and values in the ·value space· of QName depends on the set
     of namespace declarations in scope for the context in which
     QName is used.

MSM's recommendation:  adopt without discussion.
Comment 4 Dave Peterson 2009-04-20 17:18:29 UTC
The WG adopted the proposal referred to in comment #2 (referral repeated in comment #3) on 17 Apr and the change has been added to the SQ document.  Therefore, I am marking this FIXED.  Since the fix is precisely the fix proposed by the originator, who was present at the telephone meeting, I will  immediately mark it CLOSED on his behalf.