W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2007

[Bug 5161] all model group min/maxoccurs confusing

From: <bugzilla@wiggum.w3.org>
Date: Mon, 08 Oct 2007 21:03:34 +0000
CC:
To: www-xml-schema-comments@w3.org
Message-Id: <E1IezlG-0005qk-AM@wiggum.w3.org>

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

           Summary: all model group min/maxoccurs confusing
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: johnarwe@us.ibm.com
         QAContact: www-xml-schema-comments@w3.org


3.8.1 The Model Group Schema Component says "(all) contain all and only exactly
zero or one of each element specified in {particles}. The elements can occur in
any order. In this case, to reduce implementation complexity, {particles} is
restricted to contain local and top-level element declarations only, with {min
occurs}=0 or 1, {max occurs}=1."

this is then closely followed by 3.8.2 <all...> where it specifies
minoccurs=(0|1):1 maxoccurs=1:1

In 3.8.1 the statement "{particles} is restricted to contain local and
top-level..." gets confusing because it could be read to apply to <all> group
as a whole, or to its individual particles.  

I think 3.8.1 intends to restrict the facet values on each particle, in which
case the following formulation is clearer (to me)

o (all) contain all and only exactly zero or one of each element specified in
{particles}. The elements can occur in any order. To reduce implementation
complexity, each {particle} is restricted to a contain local or top-level
element declaration only, with {min occurs}=0 or 1, and {max occurs}=1."
Received on Monday, 8 October 2007 21:03:44 UTC

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