DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14010>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14010 Using 'all' within 'complexContent' [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-10-29 15:14 ------- Consider "Schema Component Constraint: All Group Limited" from http://www.w3.org/TR/xmlschema-1/#coss-modelGroup, which states: When a model group has {compositor} all all of the following must be true: 1 one of the following must be true: 1.1 It appears as the model group of a model group definition. 1.2 It appears in a particle with {min occurs}={max occurs}=1, and that particle must be part of a pair which constitutes the {content type} of a complex type definition. 2 The {max occurs} of all the particles in the {particles} of the group must be 0 or 1. Since the resulting content model of the extension is a sequence of base content type (e.g. sequence), and derived content model (e.g. all), which does not meet 1.1 (because they're not in model group definition) and they aren't the content type of a complex type definition, because they're part of a sequence. Also, according to the schema spec (http://www.w3.org/TR/xmlschema-1/#cos-particle-extend) you cannot extend an 'all' content model unless you are only adding attributes. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
