RE: [xdi] Proposed additional X3 representation format, or areplacement for X3 Whitespace

["Barnhill, William [USA]" <barnhill_william@bah.com>]

Thanks Drummond,

I'm not a JSON expert either but have done a fair amount of it.  A nice thing about JSON is that unlike Python indenting doesn't matter to a parser. Key delimiters in JSON are '{', '}', ',', ':','[', and ']'.  Application special key identiers also often start with _ (for example _context to represent what would be a / in X3 Whitepace, and _id in couchdb). Speaking of couchdb, since it's document representation format is JSON it will store and support map/reduce operations over XDI in X3J without the need to convert to another format.  It's for this reason that a piece of what I'm working on is a rudimentary XDI messaging server built on couchdb and ejabberd.  This piece is almost done and will be released within the next two weeks. I'll post the announcement here with a download link when I do the release.  

Will do on posting formatting rules, but getting ready for travel now, should be able to do sometime tomorrow, latest on Monday eve.

=Bill.Barnhill
________________________________________
From: Drummond Reed [drummond.reed@cordance.net]
Sent: Thursday, July 02, 2009 8:53 PM
To: Barnhill, William [USA]; 'OASIS - XDI TC'
Subject: RE: [xdi] Proposed additional X3 representation format, or a replacement for X3 Whitespace

Bill, this looks pretty cool.

I'm no JSON expert, but I think the indenting needs some proofing. But
overall I think it makes sense.

Please do post the formatting rules when you have time. I've been treating
this page as "the spec" on XDI serialization formats (until we draft the
formal doc), so it's good to have a JSON format fully documented on it.

=Drummond

> -----Original Message-----
> From: Barnhill, William [USA] [mailto:barnhill_william@bah.com]
> Sent: Thursday, July 02, 2009 4:27 PM
> To: 'OASIS - XDI TC'
> Subject: [xdi] Proposed additional X3 representation format, or a
> replacement for X3 Whitespace
>
>
> I've edited http://wiki.oasis-open.org/xdi/X3Format to add text proposing
> an X3 representation that is directly in JSON as opposed to similar to
> JSON.  Given the broad adoption of JSON and the usefulness of this I'm
> seeing in my work I wanted to share it with the TC.  JSON format is still
> rough but works. I will add formatting rules section this weekend.
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php