[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml-comment] JSON Profile Revision
+1 to generally disallowing null. Hal From: David Brossard <david.brossard@axiomatics.com> On Mon, May 21, 2018 at 5:48 AM, Steven Legg <steven.legg@viewds.com> wrote:
Empty arrays should be handled as an absence of value (an empty bag in XACML). "AccessSubject": { "Attribute": [ { "AttributeId": "com.acme.user.approvalLimit", "Value": [], "DataType": "double" }, { "AttributeId": "com.acme.user.employeeId", "Value": "Alice" } ] } is the same as "AccessSubject": { "Attribute": [ { "AttributeId": "com.acme.user.employeeId", "Value": "Alice" } ] }
It is odd to have an optional value be null. If it's optional it's because it can be skipped (and therefore null). I agree that we could disallow null in the profile. Either you do not show a property, or you show it and it has a value (including, when arrays are allowed, an array of zero elements)
Thanks for taking the time Steven, David.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]