During the last call I asked people to identify the issues or new
features we intend to complete for version 3.0. I agree than many of
your suggestions would be quite valuable additions to the next version
of XACML.
On the other, I don't think XACML 3.0 should be arbitrarily held up just
because people are beginning to implement 2.0. A lot of time and effort
has been put into Admin policies for example and that functionality is
frequently requested. Also I expect some of the 3.0 work, such as the
SAML Profile, WS-XACML profile and the Provisioning Protocol will be
useful in conjunction with XACML 2.0.
I think the PR aspect of this can be dealt with by careful handling. For
one thing it will be legal to support only "3.0 without Admin policies".
This should be an easy step for current 2.0 implementations.
We should discuss this on the call.
Hal
