Hi,
I am sorry if this issue has been already brought up for
draft-ietf-simple-presence-rules-04:
<provide-services> has the following schema
associated:
<xs:complexType
name="provideServicePermission">
<xs:choice>
<xs:element name="all-services">
<xs:complexType/>
</xs:element>
<xs:sequence minOccurs="0"
maxOccurs="unbounded">
<xs:choice>
<xs:element ref="pr:service-uri"/>
<xs:element
ref="pr:service-uri-scheme"/>
<xs:element ref="pr:occurrence-id"/>
<xs:element ref="pr:class"/>
<xs:any namespace="##other"/>
</xs:choice>
</xs:sequence>
</xs:choice>
</xs:complexType>
Here, the minOccurs and maxOccurs definitions state that
there can be
zero or more child elements. No problem here.
However, for provide-devices the schema contains:
<xs:complexType
name="provideDevicePermission">
<xs:choice>
<xs:element name="all-devices">
<xs:complexType/>
</xs:element>
<xs:sequence>
<xs:choice>
<xs:element ref="pr:device-id"/>
<xs:element ref="pr:occurrence-id"/>
<xs:element ref="pr:class"/>
<xs:any namespace="##other"/>
</xs:choice>
</xs:sequence>
</xs:choice>
</xs:complexType>
The schema should have the same minOccurs and maxOccurs
definitions as
for <provide-services>.
The same is true for <provide-persons>:
<xs:complexType
name="providePersonPermission">
<xs:choice>
<xs:element name="all-persons">
<xs:complexType/>
</xs:element>
<xs:sequence>
<xs:choice>
<xs:element ref="pr:occurrence-id"/>
<xs:element ref="pr:class"/>
<xs:any namespace="##other"/>
</xs:choice>
</xs:sequence>
</xs:choice>
</xs:complexType>
Thanks,
Krisztian
_______________________________________________
Simple mailing list
Simple ietf.org
https:/
/www1.ietf.org/mailman/listinfo/simple
|