Pete Cordell writes: > Replacing the xs:anys with xs:element declarations, UPAC wise I don't > think the following would be legal: > > <xs:sequence> > <xs:element name="given" type="xs:string"/> > <xs:element name="any" minOccurs="0" maxOccurs="unbounded"/> > <xs:sequence minOccurs="0"> > <xs:element name="middle" type="xs:string" /> > <xs:element name="any" minOccurs="0" maxOccurs="unbounded"/> > </xs:sequence> > <xs:element name="family" type="xs:string"/> > </xs:sequence> I'm feeling dense. Can you show an example of instance having at least one element that would match more than one of the wildcards? I think that's what you have to demonstrate to show that this violates UPA, given the new semantics for wildcard matching in Schema 1.1. What am I missing? I don't see why this violates UPC. Noah -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 --------------------------------------Received on Thursday, 15 March 2007 21:47:07 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 March 2007 21:47:14 GMT