RE: [xml-dev] minOccurs maxOccurs doesnt seem to be working correctly in my schema

[Marielou <marielou_h@yahoo.co.uk>]

Yes I have just tested that if element <B> appears in
my XML file, I need to have element <C> as a child of
<B> for the file to validate. However, I am finding
that my schema is accepting <C> without <B> and so
that is what has been confusing me! Because I see that
on testing, my schema is seemingly accepting any
elements which are not defined in the schema and any
number of child elements defined in the schema despite
them having a restriction on the occurrences. For
example, i can type a brand new element in the XML <D>
not defining it in the schema, and this validates
also. And on testing, I also find I can take out all
occurrences of a child element of <A> from the XML and
validate ok, even if that element had maxOccurs="1" in
<A>. Though the type restrictions I put on elements
which do exist in my schema seem to be being checked
properly. 

Marie Louise


--- Michael Kay <mike@saxonica.com> wrote:

>  
> > My XML file has format:
> > 
> > <parentA>
> >  		<C>0</C>
> >  		<C>1</C>
> >  		<C>2</C>
> >  		<C>3</C>
> > 		<C>4</C>
> >  		<C>5</C>
> >  		<C>6</C>
> >  		<C>7</C>
> > </parentA>
> > 
> > <B> is just an element ref I put in the <all> tag
> in <A> to 
> > get around the fact that <A> has no sequence but
> elements 
> > which need to occur more than once. <B> describes
> the 
> > occurrences of <C> to be more than 1, in my schema
> 
> > maxOccurs="7" but <B> does not occur in my XML
> document
> 
> No, B is an element declaration. The content model
> of parentA allows B
> elements and nothing else. Your schema doesn't allow
> C elements to appear as
> children of a parentA, only as grandchildren.
> 
> Michael Kay
> http://www.saxonica.com/
> 
> 


Send instant messages to your online friends http://uk.messenger.yahoo.com