Re: JSON profile

So the new name would become the "JSON Profile of XACML 3.0".

I am fine with that. In particular the HTTP part is indeed unnecessary. As for policy encoding, is it possible to extend a profile in the future to add a section? In this case, add a section on policy encoding?

Cheers,

David.

On Thu, Mar 6, 2014 at 9:34 PM, Sinnema, Remon <remon.sinnema@emc.com> wrote:

Hi David,

On our calls we keep talking about the JSON profile. Officially it’s called “Request / Response Interface based on JSON and HTTP for XACML 3.0”. I propose we rename it to match our current usage, for the following reasons:

1. The HTTP part should really be left to the REST profile, as the text already acknowledges

2. In the future we may want to represent policies in JSON as well

What do you think?

Thanks,

Ray

David Brossard, M.Eng, SCEA, CSTP
VP of Customer Relations
+46(0)760 25 85 75
Axiomatics AB
Skeppsbron 40
S-111 30 Stockholm, Sweden

Support: https://support.axiomatics.com
Web: http://www.axiomatics.com

Connect with us on LinkedIn | Twitter | Google Plus | Facebook | YouTube

xacml message