OASIS eXtensible Access Control Markup Language (XACML) TC

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. Steven Legg Product Architect ViewDS Identity Solutions

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

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 -- David Brossard VP of Customer Relations +1 312 774-9163 +1 502 922 6538 +46(0)760 25 85 75 Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 Support: https://support.axiomatics.com Web: http://www.axiomatics.com Axiomatics Blog Events Resources, Webinars & Whitepapers Connect with us on LinkedIn Twitter Google + Facebook YouTube Stackoverflow

Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: 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: image.png It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be: { "Value": "urn:oasis:names:tc:xacml:1.0:status:ok" } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven Thanks On Mon, Feb 11, 2019 at 6:22 PM Steven Legg <steven.legg@viewds.com < mailto: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 -- David Brossard VP of Customer Relations +1 312 774-9163 +1 502 922 6538 +46(0)760 25 85 75 Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g > Support: https://support.axiomatics.com < https://support.axiomatics.com/ > Web: http://www.axiomatics.com < http://www.axiomatics.com/ > Axiomatics Blog < http://www.axiomatics.com/blog/ > Events < http://www.axiomatics.com/events.html > Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 > Twitter < http://twitter.com/axiomatics > Google + < https://plus.google.com/u/1/b/101496487994084529291/ > Facebook < https://www.facebook.com/axiomatics > YouTube < http://www.youtube.com/user/axiomaticsab > Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard >

Agreed. Here is what I suggest: Does that make sense? On Wed, Feb 20, 2019 at 4:59 PM Steven Legg < steven.legg@viewds.com > wrote: Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: > 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: > > image.png > > It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be: { "Value": "urn:oasis:names:tc:xacml:1.0:status:ok" } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven > > Thanks > > On Mon, Feb 11, 2019 at 6:22 PM Steven Legg < steven.legg@viewds.com <mailto: 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 > > > > -- > David Brossard > VP of Customer Relations > +1 312 774-9163 > +1 502 922 6538 > +46(0)760 25 85 75 > > Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g > > Support: https://support.axiomatics.com < https://support.axiomatics.com/ > > Web: http://www.axiomatics.com < http://www.axiomatics.com/ > > Axiomatics Blog < http://www.axiomatics.com/blog/ > Events < http://www.axiomatics.com/events.html > Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html > > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 > Twitter < http://twitter.com/axiomatics > Google + < https://plus.google.com/u/1/b/101496487994084529291/ > Facebook < https://www.facebook.com/axiomatics > YouTube < http://www.youtube.com/user/axiomaticsab > Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard > > -- David Brossard VP of Customer Relations +1 312 774-9163 +1 502 922 6538 +46(0)760 25 85 75 Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 Support: https://support.axiomatics.com Web: http://www.axiomatics.com Axiomatics Blog Events Resources, Webinars & Whitepapers Connect with us on LinkedIn Twitter Google + Facebook YouTube Stackoverflow

Hi David, On 22/02/2019 4:47 am, David Brossard wrote: Agreed. Here is what I suggest: image.png Does that make sense? That works. In addition, the default value is not "None" so I would change the table cell to blank or "See text.". Regards, Steven On Wed, Feb 20, 2019 at 4:59 PM Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com >> wrote: Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: > 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: > > image.png > > It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be: { "Value": "urn:oasis:names:tc:xacml:1.0:status:ok" } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven > > Thanks > > On Mon, Feb 11, 2019 at 6:22 PM Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com > < mailto:steven.legg@viewds.com < mailto: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 > > > > -- > David Brossard > VP of Customer Relations > +1 312 774-9163 > +1 502 922 6538 > +46(0)760 25 85 75 > > Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g > > Support: https://support.axiomatics.com < https://support.axiomatics.com/ > > Web: http://www.axiomatics.com < http://www.axiomatics.com/ > > Axiomatics Blog < http://www.axiomatics.com/blog/ > Events < http://www.axiomatics.com/events.html > Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html > > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 > Twitter < http://twitter.com/axiomatics > Google + < https://plus.google.com/u/1/b/101496487994084529291/ > Facebook < https://www.facebook.com/axiomatics > YouTube < http://www.youtube.com/user/axiomaticsab > Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard > > -- David Brossard VP of Customer Relations +1 312 774-9163 +1 502 922 6538 +46(0)760 25 85 75 Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g > Support: https://support.axiomatics.com < https://support.axiomatics.com/ > Web: http://www.axiomatics.com < http://www.axiomatics.com/ > Axiomatics Blog < http://www.axiomatics.com/blog/ > Events < http://www.axiomatics.com/events.html > Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 > Twitter < http://twitter.com/axiomatics > Google + < https://plus.google.com/u/1/b/101496487994084529291/ > Facebook < https://www.facebook.com/axiomatics > YouTube < http://www.youtube.com/user/axiomaticsab > Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard >

We need to decide whether to proceed towards Oasis Standard with the current profiles, which have now been attested to by 3 organizations or drop back and update the JSON profile, hold a 15 day public review, move it to committee spec and redo the attestations. (We previously agreed to keep the two specs together thru the COS process.)   I would like to decide this today rather than wait another month, so anyone who won t be on the call should register their opinion by email ASAP.   Hal   From: David Brossard <david.brossard@axiomatics.com> Sent: Thursday, February 21, 2019 12:47 PM To: Steven Legg <steven.legg@viewds.com> Cc: xacml@lists.oasis-open.org Subject: Re: [xacml] Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Version 1.1   Agreed. Here is what I suggest:     Does that make sense?   On Wed, Feb 20, 2019 at 4:59 PM Steven Legg < steven.legg@viewds.com > wrote: Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: > 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: > > image.png > > It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be:      {        "Value": "urn:oasis:names:tc:xacml:1.0:status:ok"      } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven > > Thanks > > On Mon, Feb 11, 2019 at 6:22 PM Steven Legg < steven.legg@viewds.com <mailto: 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 > > > > -- > David Brossard > VP of Customer Relations > +1 312 774-9163 > +1 502 922 6538 > +46(0)760 25 85 75 > > Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g > > Support: https://support.axiomatics.com < https://support.axiomatics.com/ > > Web: http://www.axiomatics.com < http://www.axiomatics.com/ > > Axiomatics Blog < http://www.axiomatics.com/blog/ >  Events < http://www.axiomatics.com/events.html >  Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html > > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 >  Twitter < http://twitter.com/axiomatics >  Google + < https://plus.google.com/u/1/b/101496487994084529291/ >  Facebook < https://www.facebook.com/axiomatics >  YouTube < http://www.youtube.com/user/axiomaticsab >  Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard > >   -- David Brossard VP of Customer Relations +1 312 774-9163 +1 502 922 6538 +46(0)760 25 85 75   Axiomatics   525 W. Monroe Suite 2310 Chicago 60661 Support:  https://support.axiomatics.com   Web:  http://www.axiomatics.com Axiomatics Blog     Events     Resources, Webinars & Whitepapers Connect with us on  LinkedIn     Twitter     Google +     Facebook     YouTube     Stackoverflow  

Hi, I think I would rather move to a standard and issue an errata later. Is that an option? David. On Thu, Feb 28, 2019, 10:58 AM Hal Lockhart < hal.lockhart@oracle.com > wrote: We need to decide whether to proceed towards Oasis Standard with the current profiles, which have now been attested to by 3 organizations or drop back and update the JSON profile, hold a 15 day public review, move it to committee spec and redo the attestations. (We previously agreed to keep the two specs together thru the COS process.) I would like to decide this today rather than wait another month, so anyone who won t be on the call should register their opinion by email ASAP. Hal From: David Brossard < david.brossard@axiomatics.com > Sent: Thursday, February 21, 2019 12:47 PM To: Steven Legg < steven.legg@viewds.com > Cc: xacml@lists.oasis-open.org Subject: Re: [xacml] Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Version 1.1 Agreed. Here is what I suggest: Does that make sense? On Wed, Feb 20, 2019 at 4:59 PM Steven Legg < steven.legg@viewds.com > wrote: Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: > 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: > > image.png > > It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be: { "Value": "urn:oasis:names:tc:xacml:1.0:status:ok" } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven > > Thanks > > On Mon, Feb 11, 2019 at 6:22 PM Steven Legg < steven.legg@viewds.com <mailto: 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 > > > > -- > David Brossard > VP of Customer Relations > +1 312 774-9163 > +1 502 922 6538 > +46(0)760 25 85 75 > > Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g > > Support: https://support.axiomatics.com < https://support.axiomatics.com/ > > Web: http://www.axiomatics.com < http://www.axiomatics.com/ > > Axiomatics Blog < http://www.axiomatics.com/blog/ > Events < http://www.axiomatics.com/events.html > Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html > > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 > Twitter < http://twitter.com/axiomatics > Google + < https://plus.google.com/u/1/b/101496487994084529291/ > Facebook < https://www.facebook.com/axiomatics > YouTube < http://www.youtube.com/user/axiomaticsab > Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard > > -- David Brossard VP of Customer Relations +1 312 774-9163 +1 502 922 6538 +46(0)760 25 85 75 Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 Support: https://support.axiomatics.com Web: http://www.axiomatics.com Axiomatics Blog Events Resources, Webinars & Whitepapers Connect with us on LinkedIn Twitter Google + Facebook YouTube Stackoverflow Attachment: image002.png Description: PNG image

Hi David, On 1/03/2019 7:39 am, David Brossard wrote: Hi, I think I would rather move to a standard and issue an errata later. Is that an option? I expressed the same preference in the meeting and that's what we have decided to do. Regards, Steven David. On Thu, Feb 28, 2019, 10:58 AM Hal Lockhart <hal.lockhart@oracle.com < mailto:hal.lockhart@oracle.com >> wrote: We need to decide whether to proceed towards Oasis Standard with the current profiles, which have now been attested to by 3 organizations or drop back and update the JSON profile, hold a 15 day public review, move it to committee spec and redo the attestations. (We previously agreed to keep the two specs together thru the COS process.)____ __ __ I would like to decide this today rather than wait another month, so anyone who won t be on the call should register their opinion by email ASAP.____ __ __ Hal____ __ __ *From:*David Brossard <david.brossard@axiomatics.com < mailto:david.brossard@axiomatics.com >> *Sent:* Thursday, February 21, 2019 12:47 PM *To:* Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com >> *Cc:* xacml@lists.oasis-open.org < mailto:xacml@lists.oasis-open.org > *Subject:* Re: [xacml] Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Version 1.1____ __ __ Agreed. Here is what I suggest:____ __ __ image.png____ __ __ Does that make sense?____ __ __ On Wed, Feb 20, 2019 at 4:59 PM Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com >> wrote:____ Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: > 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: > > image.png > > It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be: { "Value": "urn:oasis:names:tc:xacml:1.0:status:ok" } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven > > Thanks > > On Mon, Feb 11, 2019 at 6:22 PM Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com > < mailto:steven.legg@viewds.com < mailto: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 < https://urldefense.proofpoint.com/v2/url?u=https-3A__www.oasis-2Dopen.org_apps_org_workgroup_portal_my-5Fworkgroups.php&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=9qwnHvsbgjbHVrbUe8_uR_nqJ1TIBiVdd6qOIUhVCKg&e= > > > > > -- > David Brossard > VP of Customer Relations > +1 312 774-9163 > +1 502 922 6538 > +46(0)760 25 85 75 > > Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D525-2BW.-2BMonroe-2BSuite-2B2310-2B-257C-2BChicago-2B60661-26entry-3Dgmail-26source-3Dg&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=hCt3k99kfaMy8NfKtoAYPL8Izkn_1DAbKdhWShI1juI&e= >> > Support: https://support.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=https-3A__support.axiomatics.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=t0clO9cRnzEB3Ka6prZR01YzcPo1n5CNKuR-nu5MccI&e= > < https://support.axiomatics.com/ < https://urldefense.proofpoint.com/v2/url?u=https-3A__support.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=j2PVvUnZYE3utBZTDbyMG9PFlk196F3N7dcjlrXLXpU&e= >> > Web: http://www.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Be3Xa-Bw_-wJDoYFKvyG9UUnPyvGjLts-QbixqfzFPU&e= > < http://www.axiomatics.com/ < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=LzQQ7p3YwJiJHWDtL2Q_XmnSk-eCjn5_MrvRLlq_-ac&e= >> > Axiomatics Blog < http://www.axiomatics.com/blog/ < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_blog_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Lvkdx9Uv3NBvyDQO9MyGL5Fk7MtMx1JglwtIMxcPcxg&e= >> Events < http://www.axiomatics.com/events.html < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_events.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=TJmmusfsLlTkCFm8usElLqRltEt_kiyQq9toAXrL9GQ&e= >> Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_resources.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=E7SZkqImGMg_6fP55mkZ5CNWS7JIQOQ5PUKPMLuCkeI&e= >> > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_companies_536082&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Ly1zrbP1VTPEt3A7jlAmpDxkBXdP9CJ56uo3dNnUfvI&e= >> Twitter < http://twitter.com/axiomatics < https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kiCdykUnt3s-wznAomeaywV97L_5UcSpwUi4B1MzVPE&e= >> Google + < https://plus.google.com/u/1/b/101496487994084529291/ < https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_u_1_b_101496487994084529291_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=ODUNpjW0_v83Sgq8Kkrv1x9nsP5vV1cOz6tpjME_teY&e= >> Facebook < https://www.facebook.com/axiomatics < https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=weM4ElAjUdeifFi3Ylmy9xSQrBCDemCV1GyJypuTldU&e= >> YouTube < http://www.youtube.com/user/axiomaticsab < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_user_axiomaticsab&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kbkVYRC8h638legIY4TNDgjg4-exKhwOQJ7Kh3ZeCs0&e= >> Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard < https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_users_1021725_david-2Dbrossard&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=jnZpvv75zknChUpMhxg88tsHgxjAAQup7zR_ynHpbKI&e= >> > ____ ____ __ __ -- ____ David Brossard VP of Customer Relations____ +1 312 774-9163____ +1 502 922 6538____ +46(0)760 25 85 75____ __ __ Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D525-2BW.-2BMonroe-2BSuite-2B2310-2B-257C-2BChicago-2B60661-26entry-3Dgmail-26source-3Dg&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=hCt3k99kfaMy8NfKtoAYPL8Izkn_1DAbKdhWShI1juI&e= >____ Support: https://support.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=https-3A__support.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=j2PVvUnZYE3utBZTDbyMG9PFlk196F3N7dcjlrXLXpU&e= > Web: http://www.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=LzQQ7p3YwJiJHWDtL2Q_XmnSk-eCjn5_MrvRLlq_-ac&e= >____ Axiomatics Blog < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_blog_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Lvkdx9Uv3NBvyDQO9MyGL5Fk7MtMx1JglwtIMxcPcxg&e= > Events < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_events.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=TJmmusfsLlTkCFm8usElLqRltEt_kiyQq9toAXrL9GQ&e= > Resources, Webinars & Whitepapers < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_resources.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=E7SZkqImGMg_6fP55mkZ5CNWS7JIQOQ5PUKPMLuCkeI&e= >____ Connect with us on LinkedIn < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_companies_536082&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Ly1zrbP1VTPEt3A7jlAmpDxkBXdP9CJ56uo3dNnUfvI&e= > Twitter < https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kiCdykUnt3s-wznAomeaywV97L_5UcSpwUi4B1MzVPE&e= > Google + < https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_u_1_b_101496487994084529291_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=ODUNpjW0_v83Sgq8Kkrv1x9nsP5vV1cOz6tpjME_teY&e= > Facebook < https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=weM4ElAjUdeifFi3Ylmy9xSQrBCDemCV1GyJypuTldU&e= > YouTube < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_user_axiomaticsab&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kbkVYRC8h638legIY4TNDgjg4-exKhwOQJ7Kh3ZeCs0&e= > Stackoverflow < https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_users_1021725_david-2Dbrossard&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=jnZpvv75zknChUpMhxg88tsHgxjAAQup7zR_ynHpbKI&e= >____ __ __

All, I have tidied up the JSON profile section of the errata page on the TC wiki and added an item for StatusCode. Regards, Steven On 1/03/2019 7:55 am, Steven Legg wrote: Hi David, On 1/03/2019 7:39 am, David Brossard wrote: Hi, I think I would rather move to a standard and issue an errata later. Is that an option? I expressed the same preference in the meeting and that's what we have decided to do. Regards, Steven David. On Thu, Feb 28, 2019, 10:58 AM Hal Lockhart <hal.lockhart@oracle.com < mailto:hal.lockhart@oracle.com >> wrote: We need to decide whether to proceed towards Oasis Standard with the current profiles, which have now been attested to by 3 organizations or drop back and update the JSON profile, hold a 15 day public review, move it to committee spec and redo the attestations. (We previously agreed to keep the two specs together thru the COS process.)____ __ __ I would like to decide this today rather than wait another month, so anyone who won t be on the call should register their opinion by email ASAP.____ __ __ Hal____ __ __ *From:*David Brossard <david.brossard@axiomatics.com < mailto:david.brossard@axiomatics.com >> *Sent:* Thursday, February 21, 2019 12:47 PM *To:* Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com >> *Cc:* xacml@lists.oasis-open.org < mailto:xacml@lists.oasis-open.org > *Subject:* Re: [xacml] Re: ViewDS Statement of Use for JSON Profile of XACML 3.0 Version 1.1____ __ __ Agreed. Here is what I suggest:____ __ __ image.png____ __ __ Does that make sense?____ __ __ On Wed, Feb 20, 2019 at 4:59 PM Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com >> wrote:____ Hi David, On 20/02/2019 5:03 pm, David Brossard wrote: > 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: > > image.png > > It's not very clear indeed. How do you suggest we make it easier to understand? The place that needs clarification is the default value for the "StatusCode" member in CD01 Section 5.2.2 (The Status object representation). Instead of "None", the default value should be: { "Value": "urn:oasis:names:tc:xacml:1.0:status:ok" } It may be problematic fitting that in the width of the table/page. It would be sufficient for the default value to be {}. The "Value" member would default to "urn:oasis:names:tc:xacml:1.0:status:ok" in that case, but it is less clear and would deserve a paragraph in 5.2.2 to point that out. Regards, Steven > > Thanks > > On Mon, Feb 11, 2019 at 6:22 PM Steven Legg <steven.legg@viewds.com < mailto:steven.legg@viewds.com > < mailto:steven.legg@viewds.com < mailto: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 < https://urldefense.proofpoint.com/v2/url?u=https-3A__www.oasis-2Dopen.org_apps_org_workgroup_portal_my-5Fworkgroups.php&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=9qwnHvsbgjbHVrbUe8_uR_nqJ1TIBiVdd6qOIUhVCKg&e= > > > > > -- > David Brossard > VP of Customer Relations > +1 312 774-9163 > +1 502 922 6538 > +46(0)760 25 85 75 > > Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://maps.google.com/?q=525+W.+Monroe+Suite+2310+%7C+Chicago+60661&entry=gmail&source=g < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D525-2BW.-2BMonroe-2BSuite-2B2310-2B-257C-2BChicago-2B60661-26entry-3Dgmail-26source-3Dg&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=hCt3k99kfaMy8NfKtoAYPL8Izkn_1DAbKdhWShI1juI&e= >> > Support: https://support.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=https-3A__support.axiomatics.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=t0clO9cRnzEB3Ka6prZR01YzcPo1n5CNKuR-nu5MccI&e= > < https://support.axiomatics.com/ < https://urldefense.proofpoint.com/v2/url?u=https-3A__support.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=j2PVvUnZYE3utBZTDbyMG9PFlk196F3N7dcjlrXLXpU&e= >> > Web: http://www.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Be3Xa-Bw_-wJDoYFKvyG9UUnPyvGjLts-QbixqfzFPU&e= > < http://www.axiomatics.com/ < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=LzQQ7p3YwJiJHWDtL2Q_XmnSk-eCjn5_MrvRLlq_-ac&e= >> > Axiomatics Blog < http://www.axiomatics.com/blog/ < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_blog_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Lvkdx9Uv3NBvyDQO9MyGL5Fk7MtMx1JglwtIMxcPcxg&e= >> Events < http://www.axiomatics.com/events.html < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_events.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=TJmmusfsLlTkCFm8usElLqRltEt_kiyQq9toAXrL9GQ&e= >> Resources, Webinars & Whitepapers < http://www.axiomatics.com/resources.html < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_resources.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=E7SZkqImGMg_6fP55mkZ5CNWS7JIQOQ5PUKPMLuCkeI&e= >> > Connect with us on LinkedIn < http://www.linkedin.com/companies/536082 < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_companies_536082&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Ly1zrbP1VTPEt3A7jlAmpDxkBXdP9CJ56uo3dNnUfvI&e= >> Twitter < http://twitter.com/axiomatics < https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kiCdykUnt3s-wznAomeaywV97L_5UcSpwUi4B1MzVPE&e= >> Google + < https://plus.google.com/u/1/b/101496487994084529291/ < https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_u_1_b_101496487994084529291_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=ODUNpjW0_v83Sgq8Kkrv1x9nsP5vV1cOz6tpjME_teY&e= >> Facebook < https://www.facebook.com/axiomatics < https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=weM4ElAjUdeifFi3Ylmy9xSQrBCDemCV1GyJypuTldU&e= >> YouTube < http://www.youtube.com/user/axiomaticsab < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_user_axiomaticsab&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kbkVYRC8h638legIY4TNDgjg4-exKhwOQJ7Kh3ZeCs0&e= >> Stackoverflow < https://stackoverflow.com/users/1021725/david-brossard < https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_users_1021725_david-2Dbrossard&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=jnZpvv75zknChUpMhxg88tsHgxjAAQup7zR_ynHpbKI&e= >> > ____ ____ __ __ -- ____ David Brossard VP of Customer Relations____ +1 312 774-9163____ +1 502 922 6538____ +46(0)760 25 85 75____ __ __ Axiomatics 525 W. Monroe Suite 2310 Chicago 60661 < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D525-2BW.-2BMonroe-2BSuite-2B2310-2B-257C-2BChicago-2B60661-26entry-3Dgmail-26source-3Dg&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=hCt3k99kfaMy8NfKtoAYPL8Izkn_1DAbKdhWShI1juI&e= >____ Support: https://support.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=https-3A__support.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=j2PVvUnZYE3utBZTDbyMG9PFlk196F3N7dcjlrXLXpU&e= > Web: http://www.axiomatics.com < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=LzQQ7p3YwJiJHWDtL2Q_XmnSk-eCjn5_MrvRLlq_-ac&e= >____ Axiomatics Blog < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_blog_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Lvkdx9Uv3NBvyDQO9MyGL5Fk7MtMx1JglwtIMxcPcxg&e= > Events < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_events.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=TJmmusfsLlTkCFm8usElLqRltEt_kiyQq9toAXrL9GQ&e= > Resources, Webinars & Whitepapers < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.axiomatics.com_resources.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=E7SZkqImGMg_6fP55mkZ5CNWS7JIQOQ5PUKPMLuCkeI&e= >____ Connect with us on LinkedIn < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_companies_536082&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=Ly1zrbP1VTPEt3A7jlAmpDxkBXdP9CJ56uo3dNnUfvI&e= > Twitter < https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kiCdykUnt3s-wznAomeaywV97L_5UcSpwUi4B1MzVPE&e= > Google + < https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_u_1_b_101496487994084529291_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=ODUNpjW0_v83Sgq8Kkrv1x9nsP5vV1cOz6tpjME_teY&e= > Facebook < https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_axiomatics&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=weM4ElAjUdeifFi3Ylmy9xSQrBCDemCV1GyJypuTldU&e= > YouTube < https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_user_axiomaticsab&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=kbkVYRC8h638legIY4TNDgjg4-exKhwOQJ7Kh3ZeCs0&e= > Stackoverflow < https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_users_1021725_david-2Dbrossard&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=6AnA6HsPbexOrQIxhTfLcU7sWoqWPDG6PxQCWHeutC0&m=eOiAZ0EGbVdKum8uTn0Y3piPy8tlayGkYTy-DQ4ivt4&s=jnZpvv75zknChUpMhxg88tsHgxjAAQup7zR_ynHpbKI&e= >____ __ __

> 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. So a null is treated as ? thanks b

Actually no, "" would be an empty string. Null would fall back to the default value. Either way on the greater scale of things, status code is only really interesting when it carries a value other than OK and only in Indeterminate / NotApplicable cases. Actually what does the spec say in regard to setting values? Policies have no control over that. On Wed, Feb 20, 2019, 8:01 AM William Parducci < bill@parducci.net wrote: > 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. So a null is treated as ? thanks b --------------------------------------------------------------------- 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

Curious as to how that would be handled differently from a functional perspective ? I think to answer this better it would be helpful to walk through a Use Case or two to understand the underlying functional intent. thanks b On Feb 20, 2019, at 6:35 AM, David Brossard < david.brossard@axiomatics.com > wrote: Actually no, would be an empty string. Null would fall back to the default value. Either way on the greater scale of things, status code is only really interesting when it carries a value other than OK and only in Indeterminate / NotApplicable cases. Actually what does the spec say in regard to setting values? Policies have no control over that. On Wed, Feb 20, 2019, 8:01 AM William Parducci < bill@parducci.net wrote: > 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. So a null is treated as ? thanks b --------------------------------------------------------------------- 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