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 11251 - minor editorial improvement : improvements to section "3.8.1 The Model Group Schema Component"
Summary: minor editorial improvement : improvements to section "3.8.1 The Model Group ...
Status: RESOLVED WORKSFORME
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-07 06:24 UTC by Mukul Gandhi
Modified: 2010-11-12 16:45 UTC (History)
1 user (show)

See Also:

Attachments

Description Mukul Gandhi 2010-11-07 06:24:37 UTC 
In the latest XML Schema 1.1 WD at, http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.omni.20101029.html I am able to suggest following improvements to one of the language texts,

In the section "3.8.1 The Model Group Schema Component" it's said:
<quote>
When two or more element declarations contained ·directly·, ·indirectly·, or ·implicitly· in the {particles} of a model group have identical names, the type definitions of those declarations must be the same.
</quote>

I think this description is probably wrong. The above text seems to convey that, element declarations having same name must be validated by the same schema type (in this case, the element declarations belong to model group -- but to my opinion, that doesn't make difference to relationship between an element declaration and it's schema type with any other case like xs:element being child of xs:sequence for example).

It probably seems appropriate to me, that the above cited text (within <quote>) is not at all needed -- so I recommend it to be deleted from the cited section.
Comment 1 David Ezell 2010-11-12 16:45:35 UTC 
The WG examined this issue, and it appears that the text is correct, if slightly redundant.  It's re-explaining Element Delcaration Consistent.
Therefore, we are resolving this bug as WORKSFORME.