[Bug 4159] Reflect legacy types better in infoset / infoset fixups

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4159

           Summary: Reflect legacy types better in infoset / infoset fixups
           Product: XML Schema
           Version: unspecified
          Platform: Macintosh
               URL: http://lists.w3.org/Archives/Member/w3c-xml-schema-
                    wg/2002Jan/0090.html
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: cmsmcq@w3.org
         QAContact: www-xml-schema-comments@w3.org


This issue was raised by Jonathan Marsh in email of January 2002
http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Jan/0090.html

In that mail, his third point is:

     Looking at Schema from the point of view of retaining infoset
     consistency, I then wonder why Schema provides "legacy" datatypes
     such as xs:ID, which are not reflected in the infoset in a manner
     that recognizes the legacy behavior.  This is apparent in the
     unfortunate fact that XPointer cannot recognize Schema IDs,
     because it is based on the Infoset.  To provide meaningful legacy
     support, Schema would have to reflect xs:ID in the [attribute
     type] and [references] properties.  There are likely similar
     issues with the other legacy datatypes (e.g.  NOTATION).

For the first issue raised by Jonathan Marsh's email, see bug 2102
(for 1.0) and 2105 (for 1.1); for the second, see bug 2103 (for 1.0)
and bug 2748 (this issue, for 1.1).

Received on Monday, 8 January 2007 22:17:09 UTC