>I did wonder about the encoding but did not put it in my original set of questions. I know that from the current system documents come down from the server in base64 format and so they have to be converted first before throwing them into a file. I am not sure what the new proposed system will do (because it has not yet been proposed!) but just asking questions at this point.
>
>As for your image, should a sentance not just have an exclamation point if it is to be said with increased emphasis :-) Someone with better grammer skills than I will have to answer that one...my grammer teacher from 4 decades ago would have been able to tell me the answer but I remember distinctly in that class that I said to myself "I don't need to pay attention - when will I ever use this stuff...".

Interestingly, though, Americans never misuse (or abuse?) quotation marks when mimicking them with fingers while speaking - then they always use them correctly, as a way to denote something as a fake or not what it actually means, never to emphasize.

p.s. grammar, not grammer


>>>Dragan pretty much answered from my POV.
>>>There is only one aspect where XML has benefits over JSON, that is in wrapping text fields with delimiters / not forcing any encoding to the string or memo field.
>>>
>>>XML got worse when interlocking schema definitions came with SOAP, but there are also some different flavors of JSON - but those most of the time present no or small parsing problems.
>>>
>>>To honor https://xkcd.com/927/ I often wonder if text/memo fields in JSON should be wrapped in <txt></txt> instead of ["], as then chars inside the delimiters could be left alone.
>>
>>I think we've found a way to use base64 encoding in json, but in the end didn't need it, so I have no example to show it. But IMO much cleaner than the current implementation of backslash-this and backslash-that for "special" characters (and I do mean the quotation marks seriously, not as emphasis). All characters should have equal rights!
>>