Re: [xacml] Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Ve

Subject: Re: [xacml] Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Version 1.1

Hi Steven,

I think my intent was that the absence of a status code in JSON meant a status code of OK (per its default value). Here is what WD19 says:

It's not very clear indeed. How do you suggest we make it easier to understand?

Thanks

On Mon, Feb 11, 2019 at 6:22 PM Steven Legg <steven.legg@viewds.com> wrote:

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

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.Â Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

xacml message