Re: [security-services] Core 27 syntax comment

["Eve L. Maler" <eve.maler@sun.com>]

I agree.  It would be quite natural to allow a single optional 
Evidence and make it contain a mixture of one or more 
AssertionIDReference and Assertion elements.  (The "one or more" would 
be because the parent element is already optional; don't use the 
element if you don't want to supply content.)

This is tangentially related to my proposal to get rid of 
AssertionSpecifier, whose type is currently used by Evidence.  Later 
today I will make two proposals: one to simply get rid of 
AssertionSpecifier, and one to get rid of it and also change Evidence 
in the manner that Tim suggests.

	Eve

Tim Moses wrote:

> Colleagues - It seems unfortunate that, in order to include more than 
> one assertion in a request, multiple "evidence" elements (each 
> containing one assertion) have to be inserted.  It seems preferable that 
> one evidence element be capable of carrying more than one assertion.  
> All the best.  Tim.

-- 
Eve Maler                                    +1 781 442 3190
Sun Microsystems XML Technology Center   eve.maler @ sun.com