Submitter's message
Fixed the IANA registration section.
Fixed inconsistent DataType spelling. DataType is always the XACML attribute and JSON property name. Data type refers to the English notion.
Fixed the status XML content encoding to be consistent with the Request XML encoding technique.
Fixed a non-normative section label.
Fixed the formatting of JSON property names.
Fixed the XACML to JSON data type inference by adding references to the relevant XML data types.
-- Mr. David Brossard
Document Name: Request / Response Interface based on JSON and HTTP for XACML 3.0 Version 1.0
Description
With the rise in popularity of APIs and its consumerization, it becomes
important for XACML to be easily understood in order to increase the
likelihood it will be adopted. In particular, XML is often considered to be
too verbose. Developers increasingly prefer a lighter representation using
JSON, the _javascript_ object notation.
This profile aims at defining a JSON format for the XACML request and
response. It also defines the transport between client (PEP) and service
(PDP).
Download Latest Revision
Public Download Link
Submitter: Mr. David Brossard
Group: OASIS eXtensible Access Control Markup Language (XACML) TC
Folder: Specifications and Working Drafts
Date submitted: 2013-02-04 05:10:38
Revision: 8
