xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
[Issue] Would it be SO bad if we dropped the
MHonArc v2.5.0b2 -->xacml message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Issue] Would it be SO bad if we dropped the <Function> element?
- From: Tim Moses <[email protected]>
- To: "'XACML'" <[email protected]>
- Date: Mon, 29 Dec 2003 11:41:02 -0500
Colleagues - Do we need to retain the <Function> element? I believe its purpose can be served by the <Apply> element when the FunctionId attribute identifies one of the bag functions. We already allow a similar special case in the <Condition> element, which is an <Apply> element whose FunctionId attribute must identify a function whose return type is boolean. As currently structured, the bag function does not "enclose" the attributes or functions to which it applies. If we require the use of the <Apply> element instead, the bag function can enclose the attributes or functions to which it applies. See lines [a477] to [a491] in draft 3. Doesn't this make more sense? All the best. Tim. ----------------------------------------------------------------- Tim Moses 613.270.3183
[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]