Re: [xacml] Groups - Request / Response Interface based on JSON and HTTP

Subject: Re: [xacml] Groups - Request / Response Interface based on JSON and HTTP for XACML 3.0 Version 1.0 uploaded

have a header in the transport mechanism to convey the version of the spec. That's covered (I think) in the IANA registration section since there is an optional parameter to the media type to represent the version number.
have a dedicated HTTP header called version or something similar (still in transport)
have a property that contains the namespace URI (that's clearly unambiguous and future-proof)

But generally, the request structure is so radically different between 2.0 and 3.0 that a machine can tell which is which easily. That's not future-proof though.

On Mon, Oct 29, 2012 at 4:57 PM, Sinnema, Remon <remon.sinnema@emc.com> wrote:

Hi David,

From: David Brossard [mailto:david.brossard@axiomatics.com]
Sent: Monday, October 29, 2012 4:51 PM
To: Sinnema, Remon
Cc: xacml@lists.oasis-open.org
Subject: Re: [xacml] Groups - Request / Response Interface based on JSON and HTTP for XACML 3.0 Version 1.0 uploaded

> That's a good point. Actually, as it turns out, the modeling of the JSON profile is such that it only supports XACML 3.0 though now that I think about it.

Adding such a construct may be of value for future XACML versions as well.

> As a matter of fact, I don't see a benefit to retrofitting to XACML 2.0 request / response.
>
> Do you think it's an important requirement?

It's not important, but would be nice. If the profile describes just the translation mechanism from XML to JSON, it should be much work to include 2.0.

Thanks,
Ray

--
David Brossard, M.Eng, SCEA, CSTP
Product Manager
+46(0)760 25 85 75
Axiomatics AB
Skeppsbron 40
S-111 30 Stockholm, Sweden
http://www.linkedin.com/companies/536082
http://www.axiomatics.com
http://twitter.com/axiomatics

xacml message