OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] XSD 1.1 - assert a condition of a complex type depending on another element's attribute value

> 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)"


Michael Kay

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS