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: Polar Humenn <[email protected]>
- To: Michael McIntosh <[email protected]>
- Date: Thu, 13 Nov 2003 01:08:51 -0500 (EST)
My appologies for not making the concall this morning. Unforunately, I got detained at the doctor's office this morning. > Seth: Status Issue - want to be able to specify attribute without value. > Anne: Already accepted this. > Hal: Want to have two definitions (one where value is required and one > where it isn't) This is the case where you need to specify the attribute in the return status as missing. Correct? 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? BTW, I leave for England tomorrow for a week, so I will not be at the next concall. Cheers, -Polar
- Follow-Ups:
- Re: [xacml] Draft Minutes - November 13
- From: Seth Proctor <[email protected]>
- Re: [xacml] Draft Minutes - November 13
- References:
- Draft Minutes - November 13
- From: Michael McIntosh <[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]