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 1842 - Consider effect of XML 1.1-based XSD types on Schema 1.1 adoption
Summary: Consider effect of XML 1.1-based XSD types on Schema 1.1 adoption
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Windows 2000
: P2 normal
Target Milestone: ---
Assignee: XML Schema WG
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-08-12 00:06 UTC by Noah Mendelsohn
Modified: 2009-04-20 19:59 UTC (History)
1 user (show)

See Also:


Attachments

Description Noah Mendelsohn 2005-08-12 00:06:01 UTC
We have closed RQ-152 [1] with a decision that in XML Schema 1.1 our types such
as xsd:Name will be defined in terms of the pertinent productions from XML 1.1.
 It has been suggested that while this decision is in some ways supportive of
the needs of XML query "Implementation Defined Item" [2] that enables XML 1.1,
our decision is arguably problematic for the many implementations that will use
query in "XML 1.0 mode".

While we have not at this time decided to reopen RQ-152, this is a request to
open a separate issue which is to (a) ensure that we are taking appropriate
steps to ensure that the implications of our current RQ-152 resolution are
understood by the rest of the XML community and (b) to explore, possibly in
conjunction with the Query workgroup, what approaches to XML 1.1 support would
help to maximize the adoption of Schema 1.1 by Query.   One possible outcome of
such efforts would indeed be a decision to reopen our resolution of RQ-152, I.e.
to change the Schema 1.0 definitions of types such as xsd:Name.

[1] http://www.w3.org/XML/Group/2002/07/xmlschema-1.1-current-reqs-list.html#xml1.1)
[2] http://www.w3.org/TR/xquery/#id-impl-defined-items
Comment 1 C. M. Sperberg-McQueen 2005-09-07 21:51:17 UTC
I believe this is ready for WG consideration and classification.
Comment 2 C. M. Sperberg-McQueen 2006-09-20 23:13:07 UTC
This issue was resolved by the adoption of the proposal for 
bug 1838 at the Working Group's face to face meeting of 
January 2006 in St. Petersburg.  The resolution is reflected 
in the last call working draft of 17 February 2006.

This issue should have been mark as RESOLVED / FIXED at that
time, but apparently was not.  I am marking it that way now, to
reduce confusion.