[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] JSON Profile of XACML - WD 19 ready to move on
Thanks David.
Some minor followups to my original comments: RE my comment about 4.2.3 (line item 7): I have no problem with leaving it to inference based on the content. My comment is about improving the text to reflect
this. So I suggest the text in Section 4.2.3 be update from: “The request parser must determine whether XML escaping or Base 64 encoding is used”
To something to the effect of: “The request parser must determine whether XML escaping or Base 64 encoding is used
based on the content according to [BASE64].” Or: “The request parser must determine whether XML escaping or Base 64 encoding is used
based on the first character according to [BASE64].”. Also RE my comment about XML equivalent for examples (line item 9): I think since the profile does not use a schema for defining the JSON structures and JSON structures are being defined *based on* the existing XML structures
(which are in turn well-defined by the schema) it is important to provide the XML equivalent of at least some examples. With the exception of 3.3.3.1 there are no other examples in the document that provide the XML equivalent.
Regards, Mohammad Jafari, Ph.D. Veteran Health Administration, Department of Veteran Affairs (Edmond Scientific Company) From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org]
On Behalf Of David Brossard Hi, I have now updated the JSON profile to include the <StatusCode/> fix. I've also updated the Excel sheet with additional comments as to why a comment has been rejected. See attached. Cheers, David. -- David Brossard, M.Eng, SCEA, CSTP Support:
https://support.axiomatics.com Axiomatics for developers:
http://developers.axiomatics.com |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]