Re: [xacml] Putting the final touches to the JSON representation

[David Brossard <david.brossard@axiomatics.com>]

Hi Ray,

I take it you didn't apply for an IANA registration for XACML Media Type application/xacml+json

Do we want to register such a media type? How would that relate to your registration since yours is simply called XACML Media Type. Does it mean we would add xacml+json as a subsection?

Cheers,

David.

On Mon, Oct 29, 2012 at 11:24 AM, Sinnema, Remon <remon.sinnema@emc.com> wrote:

Hi David,


From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org] On
Behalf Of David Brossard
Sent: Monday, October 29, 2012 10:51 AM
To: Sinnema, Remon; xacml
Subject: [xacml] Putting the final touches to the JSON representation

> 1. Ray, what did you have in mind for the IANA registration section? You
asked me to add this as a section but I don't know what you have in mind
exactly.

That section should contain the IANA registration details. See section 2 of
http://tools.ietf.org/html/draft-sinnema-xacml-media-type-00 for the
registration of the XML format that you can use as an example.

> 2. With respect to section 7, transport, I currently have a short
statement:
>
> The XACML request represented in its JSON format MAY be carried from a PEP
to a PDP via an HTTP POST request.
>
> It does not define mandatory headers that an HTTP request would contain
such as the media-type. Should we leave that up to the REST profile and
> reference it?

I think we should mention the Content-Type and Accept headers and refer to
the media type in the IANA registration section.
A reference to the REST profile also seems worthwhile.


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