Re: JSON parse tree example Re: [xdi] Agenda: XDI TC Telecon Friday 09:00 - 10:30AM PT 2013-04-05

[Markus Sabadello <markus.sabadello@gmail.com>]

I did an experimental implementation of this.

1. Go to http://xdi2.projectdanube.org/XDIConverter?sample=1
2. Select XDI/JSON/GOM in the "to" drop down box.
3. Turn on "pretty=1"
4. Click Go.

Markus

On Sun, Apr 7, 2013 at 2:11 AM, Joseph Boyle <planetwork@josephboyle.net> wrote:

Thanks Phil - I've written it up in https://wiki.oasis-open.org/xdi/JSONSerializationRules/Discussion for further scrutiny.

I've included recently discussed terminology revisions like segment => address (some still under discussion)

On Apr 6, 2013, at 3:34 PM, Phil Windley <phil@windley.org> wrote:

Like. 

On Apr 5, 2013, at 10:08 AM, Joseph Boyle <planetwork@josephboyle.net> wrote:

This is an example of the kind of parse tree I naturally get from _javascript_ code I'm writing to parse XDI.

It is probably similar to the Java data structures Markus's XDI2 creates from parsing XDI.

If we can simply JSON-serialize a parse tree that is convenient for programmers, then they can simply JSON-deserialize and use it without more complicated parsing steps.

On Apr 4, 2013, at 11:33 PM, Drummond Reed <drummond.reed@xdi.org> wrote:

JSON SERIALIZATION OPTIONS

Today (Thursday) Joseph and Drummond were able to meet and go over new options for the JSON serialization that could be more “developer friendly” by not requiring parsing of the subject/predicate keys in order to build an XDI graph object model (GOM).

Joseph will present an example of what the GOM could look like an how to serialize it.

=drummond<+email>!uuid:f81d4fae-7dec-11d0-a765-00a0c91e0001<<$string>>/<>/

"dsr@ex1.com"

Version 1:  Separate context symbol and identifier

Compact: [[{"cs":"=","id":"drummond"},{"cs":"<","id":{"cs":"+","id":"email"}},{"cs":"!","id":"uuid:f81d4fae-7dec-11d0-a765-00a0c91e0001"},{"cs":"<<","id":{"cs":"$","id":"string"}}],{"cs":"<","id":""},"dsr@ex1.com"]

Formatted:

[
   [
      {
         "cs":"=",
         "id":"drummond"
      },
      {
         "cs":"<",
         "id":{
            "cs":"+",
            "id":"email"
         }
      },
      {
         "cs":"!",
         "id":"uuid:f81d4fae-7dec-11d0-a765-00a0c91e0001"
      },
      {
         "cs":"<<",
         "id":{
            "cs":"$",
            "id":"string"
         }
      }
   ],
   {
      "cs":"<",
      "id":""
   },
   "dsr@ex1.com"
]

Version 2: Bottom-level context symbol - identifier sequence left in one string. Context functions still (usually>) require separate object.

Compact: [["=drummond",{"cs":"<","id":"+email"},"!uuid:f81d4fae-7dec-11d0-a765-00a0c91e0001",{"cs":"<<","id":"$string"}],{"cs":"<"},"dsr@ex1.com"]

Formatted:

[
   [
      "=drummond",
      {
         "cs":"<",
         "id":"+email"
      },
      "!uuid:f81d4fae-7dec-11d0-a765-00a0c91e0001",
      {
         "cs":"<<",
         "id":"$string"
      }
   ],
   {
      "cs":"<"
   },
   "dsr@ex1.com"
]