xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [xacml] Draft Minutes - November 13
MHonArc v2.5.0b2 -->xacml message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xacml] Draft Minutes - November 13
- From: Seth Proctor <[email protected]>
- To: Polar Humenn <[email protected]>
- Date: Thu, 13 Nov 2003 16:15:45 -0500
On Thu, 2003-11-13 at 01:08, Polar Humenn wrote: > This is the case where you need to specify the attribute in the return > status as missing. Correct? Yes. > As part of the input context, every <Attribute> MUST have a value, > otherise, the "mustBePresent" semantics breaks down. We should probably > have a new element that specifies it as a missing attribute specification > as part of the output context not to get it mixed up with the <Attribute> > element. > > Is that the way its going? That is the way this is going. That's what I originally suggested since we need to keep the behavior that you describe here. I'll try to get this written up soon. seth
- References:
- Draft Minutes - November 13
- From: Michael McIntosh <[email protected]>
- Re: [xacml] Draft Minutes - November 13
- From: Polar Humenn <[email protected]>
- Draft Minutes - November 13
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]