RE: min occurs

> -----Original Message-----
> From: Kasimier Buchcik [mailto:K.Buchcik@4commerce.de] 
> Sent: Thursday, October 13, 2005 04:35
> To: Alessandro Triglia
> Cc: ML-xml-schema-dev
> Subject: Re: min occurs
> 
> 
> Hi,
> 
> On Wed, 2005-10-12 at 12:53 -0400, Alessandro Triglia wrote:
> > Hi
> > 
> > I noticed the following inconsistency in Part 1:
> > 
> > -------------------------------------------------------
> > Schema Component Constraint: Particle Correct
> > 
> > 2 If {max occurs} is not unbounded [...]:
> > 
> > 2.2 {max occurs} must be greater than or equal to 1
> > -------------------------------------------------------
> > 
> > 
> > -------------------------------------------------------
> > Schema Component: Particle
> > 
> > {max occurs}
> > Either a non-negative integer or unbounded.
> > -------------------------------------------------------
> > 
> > 
> > Why wasn't the {max occur} property of particles just 
> specified as a *positive* integer?  Am I missing something obvious?
> > 
> > 
> > I also noticed the following:
> > 
> > ------------------------------------------------------
> > Schema Component Constraint: All Group Limited
> > 
> > When a model group has {compositor} all [...]:
> > 
> > 2 The {max occurs} of all the particles in the {particles} 
> of the group must be 0 or 1.
> > ------------------------------------------------------
> > 
> > How could it be 0 without violating "Schema Component 
> Constraint: Particle Correct"?
> > 
> > 
> > Alessandro Triglia
> > OSS Nokalva
> 
> Yes, this has been noticed already:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=2222


The second issue above (beginning with "I also noticed the following...") is
not reported in Sandy's bug report.

Also, I think the problem is narrower than what is reported by Sandy.  I
don't see any problem in the XML representation and in the mapping from the
XML representation to the schema components.  The only problem that I see is
entirely at the schema component level, and is the way that the Particle
schema component's {max occurs} property is specified.  It should really
have been "Either a positive integer or unbounded".

I would like to reply to Sandy that the two following things are very
different:

1) the attribute "maxOccurs" of certain elements in the XML representation
of a schema;
2) the property {max occurs} of a particle corresponding to that element.

The former is allowed to be "0", the latter is not allowed to be 0.

Alessandro


> 
> Apparently there's an schema angel called Sandy Gao around.
> I already fell in love with her, since, beside other things,
> she's gathering all the scattered comments of the past
> and present and adds them to bugzilla.
> 
> Regards,
> 
> Kasimier
> 
>

Received on Thursday, 13 October 2005 15:24:34 UTC