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.

>Hi all,
>
>In discussion with another developer about re-doing a system. This system interacted with a document database and the integration with the VFP app was done with calls that always returned an xml string. The other developer had mentioned using json to return back data from the server.
>
>I have done the wikipedia lookup and have an idea what json data looks like but have some questions:
>
>1) are their json parsers out there for VFP or would I have to write my own; with xml, there were the built in xml functions which I used
>
>2) does json have any advantages over xml?
>
>3) any "gotchas" to watch out for?
>
>Albert