[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: schema 16 comments: request attributes
-----Original Message-----I agree with the idea, but I suggest having the optional attributes at the end rather than the beginning of the sequence. While it seems nice to have input data lexically b4 the choice, from a schema perspective we tend to like to have optional stuff at the end.
From: David Orchard [mailto:david.orchard@bea.com]
Sent: Wednesday, September 05, 2001 10:06 PM
To: Simon Godik; 'security-services@lists.oasis-open.org'
Subject: Re: schema 16 comments: request attributes
Dave
At 07:13 PM 9/5/01 -0700, Simon Godik wrote:
We should be able to pass request attributes to the issuing party.
I would like to propose addition to the RequestType:
<complexType name="RequestType">
<complexContent>
<extension base="samlp:RequestAbstractType">
<sequence>
<element ref="saml:Attribute" minOccurs="0" maxOccurs="unbounded"/>
<choice>
-- same as before --
</choice>
<sequence>
</extension>
</complexContent>
</complexType>
Simon Godik
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC