Re: [xacml] XPath support in the JSON profile

[Bill Parducci <bill@parducci.net>]

I do not think one can reasonably refer to escaped XML wrapped in JSON as even mildly readable. Granted, it might be useful for debugging by a well versed engineer, but is that the use case we are trying to solve? I suspect in reality even debugging would be handled by some level of decoding before human eyes attempt to extract the details. If that is true, then I tend to agree with the base64 proposal.

b



On Nov 1, 2012, at 4:37 PM, Steven Legg <steven.legg@viewds.com> wrote:

> > The
>> issue is that if JSON is meant to be for easier XACML request authoring and human readability, Base 64 goes
>> against that.
> 
> The Base64 encoding is automatically 33% longer than the original XML. I would
> expect that the JSON character escapes would bloat a typical XML document by less
> than that, and the result would still be semi-readable. So I lean towards using
> the JSON character escapes.