Re: [Json] Nudging the English-language vs. formalisms discussion forward

[Cyrus Daboo <[e-mail]>]

Hi Pete,

--On February 19, 2014 at 10:29:32 PM +0000 Pete Cordell 
<[e-mail]> wrote:

> I thought I'd throw down n gauntlet as a baseline for something to be
> beat. So I started with something C like, and stole stuff from other
> languages and came up with the following
>

Please take a look at Andrew Newton's spec 
(<https://datatracker.ietf.org/doc/draft-newton-json-content-rules/>).

I have used that in two specs of my own:

<http://tools.ietf.org/html/draft-douglass-timezone-service-10#section-7>
<http://tools.ietf.org/id/draft-daboo-aggregated-service-discovery-03.txt> 
Appendix B

I found it to be easy to use and provide the necessary "commentary" for the 
JSON format chosen for those specs. I know several others who have 
implemented the timezone service protocol and we had no issues with 
interoperability related to the JSON format (beyond some poor text 
descriptions on my part).

As Andrew noted earlier, his spec could probably be simplified some more - 
but we certainly don't need anything more complicated than what is there 
now.

-- 
Cyrus Daboo