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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: Short comment on cd-1 schema


While looking through the cd-1 schema I noticed this:

<xs:complexType name="RequestType">
−
<xs:sequence minOccurs="0" maxOccurs="unbounded">
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<xs:element ref="xacml:RequestDefaults" minOccurs="0"/>
<xs:element ref="xacml:Attributes" maxOccurs="unbounded"/>
<xs:element ref="xacml:MultiRequests" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="ReturnPolicyIdList" type="xs:boolean"
use="required"/>
</xs:complexType>


Do we really want this? It means that a Request could have several
RequestDefaults elements. I get the impression this wasn't intentional
and that we should remove the minOccurs/maxOccurs in the sequence.

If it was intentional, I would appreciate an explanation what the
use-case is (and how we resolve the valid RequestDefaults if there are
several).


Regards,

Ludwig Seitz


-- 
Ludwig Seitz, PhD             |   Axiomatics AB
Training & Development        |   Electrum 223
Phone: +46 (0)760 44 22 91    |   S-164 40 Kista, Sweden
Mail: ludwig@axiomatics.com   |

This is a digitally signed message part



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