Re: Additional simplifications in the JSON profile

I agree with that. It makes it more consistent. Thanks for all your help.

On Thu, May 16, 2013 at 12:53 AM, Steven Legg <> wrote:

On 16/05/2013 8:46 AM, Steven Legg wrote:

Hi David,

On 16/05/2013 12:59 AM, David Brossard wrote:

Hi,

Following the decision to remove unnecessary nestings e.g. Obligations and Obligation as well as

RequestDefaults and XPathVersion, I'd also like to put forward the following simplification.

Right now we have in the JSON Request an object called "Attributes" which is an array of Attributes.

Each Attributes object contains an array of Attribute objects. I find the naming rather confusing although

it's directly in line w/ the XACML spec.

I would much rather rename Attributes to Categories and rename Attribute to Attributes.

Current state example:

{"attributes":[{"category":"urn:oasis:names:tc:xacml:3.0:attribute-category:resource","attribute":[{"attributeId":"username","value":"alice",}]}]}

Suggested change:

{"categories":[{"category":"urn:oasis:names:tc:xacml:3.0:attribute-category:resource","attributes":[{"attributeId":"username","value":"alice",}]}]}

Thoughts?

You have used singular form for the names of other arrays, e.g., "Value",

"RequestReference" and "ReferenceId". To be consistent, "Attributes" would

be renamed to "Category" and "Attribute" would stay the same.

And the nested "Category" URI field should change to "CategoryId".

Regards,

Steven

Regards,

Steven

David.

-- 
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