[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: JSON parse tree example Re: [xdi] Agenda: XDI TC Telecon Friday 09:00 - 10:30AM PT 2013-04-05
Looks great! Maybe I should just try writing client code expecting this format from the server, instead of writing _javascript_ to parse Display Format. The object (3rd member of the triple - how do we distinguish this from JSON {} and other kinds of objects?) "markus.sabadello@gmail.com" is a plain JSON value which seems right to me. The <<>> operator is represented as {"<>":{"<>":{ while I was thinking {"<":{"<":{ or maybe {"<<":{ if it is a single operator, though ideally I wish we could avoid needing double-character operators. I didn't get Drummond's mail, so maybe I'm behind on the latest syntax. JSON.stringify appears to take an indent argument where a number means to use that many spaces, and a string means to use the string itself as the indent. Not sure if there is a standard for display though http://www.freeformatter.com/json-formatter.html defaults to 3 spaces. JSON.stringify with no extra arguments is what _javascript_ code would likely use to serialize a graph to upload to the server. Not sure yet if it has any quirks we need to know about http://freshbrewedcode.com/jimcowart/2013/01/29/what-you-might-not-know-about-json-stringify/ On Apr 8, 2013, at 1:41 AM, Markus Sabadello <markus.sabadello@gmail.com> wrote: I did an experimental implementation of this. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]