Subject: Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Version 1.1
On 12/02/2019 10:45 am, Steven Legg wrote:
ViewDS Identity Solutions has successfully implemented OASIS JSON Profile of XACML 3.0 Version 1.1 Committee Specification 01 approved on 5 December 2018, in accordance with all the conformance clauses in Section 9. This did not include interoperation with independent implementations.
Something I noticed when updating my implementation is that the StatusCode member of the Status object is optional in the JSON profile whereas it is mandatory in the XML representation. I think it was David's intention that an absent StatusCode member should be treated the same as an empty StatusCode object, and that's what I've implemented, but we don't explicitly say that anywhere. Regards, Steven