W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > April to June 2009

[Bug 7031] New: XSD 1.1 doesn't support conversion of xs:sequence to xs:all because xs:all can't contain groups references

From: <bugzilla@wiggum.w3.org>
Date: Wed, 17 Jun 2009 11:51:43 +0000
To: www-xml-schema-comments@w3.org
Message-ID: <bug-7031-703@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7031

           Summary: XSD 1.1 doesn't support conversion of xs:sequence to
                    xs:all because xs:all can't contain groups references
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: abcoates@londata.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


Apologies that this is late in the day to be logging issues for XML Schema 1.1,
but this has a significant impact.  Many of us expect that, when 1.1. is
available, perhaps the majority of Schemas will be converted to use xs:all in
place of xs:sequence, since the imposition of sequencing into "data-oriented"
XML is usually a purely technical device that feels "unnatural" to users.  The
sooner we can move to unordered content for such Schemas, the better.

Some work has been done on this for FpML, the Financial Product Markup
Language, which is widely used for representing information about financial
derivatives.  The problem that has come out of the FpML conversion is that you
can't simply change "xsd:sequence" to "xsd:all" if your sequences contain
references to model groups, because "xsd:all" can't contain such references.

This is a significant issue for anyone hoping that XML Schema 1.1 will allow
them to move from ordered content to unordered content.  I'm concerned it may
block such moves, and remove one of the major reasons for migrating from 1.0 to
1.1.

It seems to me that the problem would be removed if "xsd:all" could be allowed
to contain references to "xsd:group", perhaps with the caveat that those groups
would have to contain "xsd:all" rather than a sequence or choice.

Is this plausible?  It will be a real blow if this stops us from migrating
Schemas as I had expected we would be able to.


-- 
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, 17 June 2009 11:51:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:09 UTC