[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] Groups - Request / Response Interface based on JSON and HTTP for XACML 3.0 Version 1.0 uploaded
There are a few remaining references to the previous Attributes object which should be updated to the new Category object:
4.1 Class Diagram
a. The diagram shows “Attributes” as the title of the center box. Should that be “Category”?
b. The diagram shows property “Category” but the table in 4.2.2 shows property “CategoryId”
4.2.6 RequestReference object
“Each ReferenceId value must be the value of an Attributes object Id property”
Attributes s/b Category
5.2.9 contains TODO and editor notes
One of the four ways that the multirequest profile defines how to represent a multirequest in the structure of a request object is to place multiple XML Attributes elements with the same category URN in the request. I can see that this can be done using the JSON Category as an array of objects, each using the same CategoryId to induce a multirequest evaluation at the PDP.
Can the default category objects be arrays to induce multirequest evaluation also? For example,
As semantically equivalent to an XML request containing two Attributes elements with the XACML subject category URN.
Apologies if this has already been discussed on the list and I missed it.
Dell | Identity & Access Management, Quest Software
Quest Software is now part of Dell.