11250 2010-11-07 05:12:54 +0000 minor editorial improvement : improvements to section "3.7 Model Group Definitions" 2010-11-20 03:36:03 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only All All RESOLVED INVALID P2 minor --- 1 gandhi.mukul David_E3 cmsmcq www-xml-schema-comments oldest_to_newest 42219 0 gandhi.mukul 2010-11-07 05:12:54 +0000 I'm referring to the latest editor's draft of XML Schema 1.1 spec (ref, http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.omni.20101029.html) and have few suggestions as below to improve slightly the intent of section "3.7.2 XML Representation of Model Group Definition Schema Components". 1. The title "XML Mapping Summary for Particle Schema Component" might probably be changed to "XML Mapping Summary for Model Group Particle Schema Component". (only mention of word "Particle" in the title above confused me a bit, since schema particles of various kinds) 2. The "Note:" section just below the table for "XML Mapping Summary for Particle Schema Component" may be modified from (after the heading of this table is changed to something like as specified in point 1 above): <old> The name of this section is slightly misleading, in that the second, un-named, case above (with a ref and no name) is not really a named model group at all, but a reference to one. Also note that in the first (named) case above no reference is made to minOccurs or maxOccurs: this is because the schema for schema documents does not allow them on the child of <group> when it is named. This in turn is because the {min occurs} and {max occurs} of the particles which refer to the definition are what count. </old> TO may be text like follows: <new> In the first (named) case above no reference is made to minOccurs or maxOccurs: this is because the schema for schema documents does not allow them as attributes of <group> when it is named. This in turn is because the {min occurs} and {max occurs} of the particles which refer to the definition are what count. </new> i.e readers of the spec are probably confused, when it's said "The name of this section is *slightly misleading* etc". In the cited <old> text above, the phrase "does not allow them on the child of <group> when it is named" appears incorrect (since minOccurs and maxOccurs are not child of <group> but ARE attributes). I believe corrected text should be somewhat like following, "does not allow them as attributes of <group> when it is named" -- which is suggested in the <new> text as above. 42220 1 gandhi.mukul 2010-11-07 05:15:03 +0000 (In reply to comment #0) > (only mention of word "Particle" in the title above confused me a bit, since > schema particles of various kinds) This should be read as below, (only mention of word "Particle" in the title above confused me a bit, since schema particles are of various kinds) Thanks. 42396 2 gandhi.mukul 2010-11-10 21:46:31 +0000 (In reply to comment #0) > In the cited <old> text above, the phrase "does not allow them on the child of > <group> when it is named" appears incorrect (since minOccurs and maxOccurs are > not child of <group> but ARE attributes). I believe corrected text should be > somewhat like following, "does not allow them as attributes of <group> when it > is named" -- which is suggested in the <new> text as above. It seems I'm only inclined to have the above change go into corrections, and I'm requesting my other comments (even the one with request to change heading of the section I pointed to) in this bug report to be canceled. Thanks. 42643 3 sandygao 2010-11-20 02:28:17 +0000 > Also note that in the first (named) case above no > reference is made to minOccurs or maxOccurs: this is because the schema for > schema documents does not allow them on the child of <group> when it is named. This is indeed correct. The min/maxOccurs attribute are not allowed on the <all/sequence/choice> element under <group>. i.e. the following is not allowed by the schema for schema documents. <group name="grp"> <sequence maxOccurs="2"> ... </sequence> </group> 42649 4 gandhi.mukul 2010-11-20 03:36:03 +0000 (In reply to comment #3) > This is indeed correct. The min/maxOccurs attribute are not allowed on the > <all/sequence/choice> element under <group>. i.e. the following is not allowed > by the schema for schema documents. > > <group name="grp"> > <sequence maxOccurs="2"> > ... > </sequence> > </group> Thanks, Sandy for the clarifications (i'm happy). I'm therefore marking this issue as resolved. Thanks.