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

Dear all,

I have upload WD17 of the JSON profile which is now officially called "JSON Profile of XACML 3.0". The file name doesn't change however (as per Chet's comment).

If everyone is happy with the shorthand notation names as they are today:

all consistent
all start with a lower case since the category ids in XACML are lower case
some contain a hyphen e.g. access-subject

then WD17 is the final revision.

It's been a long road and I look forward to moving this to CS.

Cheers,

David.

On Thu, Apr 17, 2014 at 4:06 PM, David Brossard <david.brossard@axiomatics.com> wrote:

Submitter's message
- Updated the profile title per conversation on the XACML TC list
- Updated section 3.2.1 on object names in JSON
- Fixed broken reference to 3.3.1 in 3.3.2
- Updated the inference rule for double and integers to remove any doubt as to the potential datatypes
- Fixed wording in section 4.2.1 (much like vs. just like)
- Simplified the wording of section 4.2.2.2
- Updated the example in section 4.2.2.3
- Changed the shorthand name subject to access-subject to be consistent
- Added the Indeterminate behavior for invalid numerical values
- Fixed the base 64 encoding example in section 4.2.3.3.
- Fixed the examples (wrong attribute names, missing parents, missing curly braces)
- Changed the MS Word quotes into proper quotes

-- 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: 2014-04-17 07:06:07
Revision: 15

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

Axiomatics for developers: http://developers.axiomatics.com

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

xacml message