[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XSD 1.1 - assert a condition of a complex type depending o

• From: "Michael Kay" <mike@saxonica.com>
• To: 'Maik St?ührenberg' <maik.stuehrenberg@uni-bielefeld.de>
• Date: Fri, 23 Oct 2009 10:18:34 +0100

> 
> So the correct assert would be inside the cd element:
> 
> <xs:element name="cd">
>     <xs:complexType>
>       <xs:sequence>
>         <xs:element ref="pd" minOccurs="1" maxOccurs="unbounded"/>
>         <xs:element ref="segs"/>
>       </xs:sequence>
>       <xs:assert test="pd/@start le segs/s/@start"/>
>       <xs:assert test="pd/@end ge segs/s/@end"/>
>     </xs:complexType>
>   </xs:element>
> 

Shouldn't it be something like

test="every $s in segs/s/@start satisfies pd/@start le $s"

> 
> In addition the problem with that solution is that the error 
> is raised for the common ancestor which makes it much harder 
> to inspect the wrong s element (if I imagine hundreds of s 
> elements and only one is wrong...)

Yes. Saxon supports a coding convention here: if you write the assertion as
an "empty()" predicate, and the result isn't empty, Saxon will tell you
where the nodes were that were found. Something like:

test="empty(for $p in pd/@start, $s in segs/s[$p le @start] return $s)"

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 

• References:
  • XSD 1.1 - assert a condition of a complex type depending on anotherelement's attribute value
    • From: =?UTF-8?B?TWFpayBTdMKfw7xocmVuYmVyZw==?=<maik.stuehrenberg@uni-bielefeld.de>
  • RE: XSD 1.1 - assert a condition of a complex type depending on another element's attribute value
    • From: "Michael Kay" <mike@saxonica.com>
  • Re: XSD 1.1 - assert a condition of a complex type dependingon another element's attribute value
    • From: =?UTF-8?B?TWFpayBTdMKfw7xocmVuYmVyZw==?=<maik.stuehrenberg@uni-bielefeld.de>