I certainly agree that there are cases where users will need full access to the power of XACML and times when they will accept that a high level of sophistication is needed to work w/ it directly, especially if this is contained in a single upfront investment in the creation of slow changing policies. For some scenarios that I have in mind, however, policy authoring is an ongoing business function which is why I said a simplified, domain-specific façade atop XACML is important.

Also, I completely agree that new wire protocols be defined in a collaborative environment where all stakeholders have a voice. This open dialog is one aspect of this that I’m eager to continue at IIW, RSA, and other upcoming conferences. Perhaps I’ll even join OASIS to lend a hand in the definition of these profiles

Thanks again, Gerry!