W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2009

[Bug 6482] New: [UPD] setToUntyped() and xml:id

From: <bugzilla@wiggum.w3.org>
Date: Wed, 28 Jan 2009 11:58:33 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-6482-523@http.www.w3.org/Bugs/Public/>


           Summary: [UPD] setToUntyped() and xml:id
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org

A literal reading of setToUntyped() suggests that the is-id property is cleared
for all attributes, including an attribute named xml:id.

A number of tests in the test suite, for example setToUntyped-001, take the
same interpretation.

However, the data model specification states (twice): "The is-id property is
always true for attributes named xml:id.".

Admittedly it says this under "construction from an InfoSet" and "construction
from a PSVI". However, the wording used strongly suggests that it is intended
to be a universal rule. And certainly, it is a sensible rule: the whole point
of xml:id is that IDness should be determined solely by the choice of attribute

I believe that the update spec should treat this as a constraint, and ensure
that the is-id property is always true for attributes named xml:id (whether
these are existing attributes, newly created, or whatever.)

[I have this rule very deeply hard-wired into my data model implementation, and
I think it is reasonable to do so.]

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, 28 January 2009 11:58:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:25 UTC