xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [xacml] condition reference text (item 7)
MHonArc v2.5.0b2 -->xacml message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] condition reference text (item 7)
- From: Tim Moses <[email protected]>
- To: Tim Moses <[email protected]>, "'Simon Godik'" <[email protected]>, "'[email protected]'" <[email protected]>
- Date: Fri, 12 Mar 2004 09:48:44 -0500
Title: Message
|
Colleagues - I have just realized how much work this is going to
be. In addition to the specific changes described by Simon, all the
examples are affected and the introductory material, including the class diagram
are affected. This is going to take some time.
I
would like to see formal acceptance of the proposal as soon as possible, because
backtracking doesn't look like an appealing option.
Personally, I lament the passing of <Condition>. The part of
<Rule> that complements <Target> is a significant independent
concept that deserves its own name. Anyone who has to explain XACML will
have to refer to it. With the passing of <Condition>, they'll have
to talk about "the child <Expression> element of
the <Rule> element" or some such. Global replace may work for
the editor, but it is not a very attractive prospect for the
reader.
Does
anyone else feel that this idea needs a name of its own?
All
the best. Tim.
|