xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [xacml] interior node
MHonArc v2.5.0b2 -->xacml message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] interior node <Result> elements for a hierarchy
- From: "Daniel Engovatov" <[email protected]>
- To: <[email protected]>, "XACML TC" <[email protected]>
- Date: Tue, 11 May 2004 12:07:33 -0700
>Unless someone gives me a good reason otherwise, I plan to >specify that a <Result> SHALL be returned for each requested node >in a hierarchy. This retains backwards compatibility with the >XACML 1.0/1.1 "scope" description. Agree. I do not think that we can do any effective shortcuts in the standard - implementations though may achieve better efficiency by using an appropriate interfaces. I would also think that if my proposal for non-XML hierarchy specification is used, scope of "immediate" children would not make sense. For flattened "ancestors" attribute all children are immediate, so that there are no "diamond" or "cycle" inheritance problems (Though such topologies still can be effectively represented). For XML documents it may be useful, so I would not mind if it is preserved. Daniel.
- Follow-Ups:
- RE: [xacml] interior node <Result> elements for a hierarchy
- From: Anne Anderson <[email protected]>
- RE: [xacml] interior node <Result> elements for a hierarchy
[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]