Re: JSON as a subset of YAML, closing the last caveat

Clark C. Evans wrote:
> On Thu, Aug 09, 2007 at 01:34:11PM -0700, Michael G Schwern wrote:
> | Clark C. Evans wrote:
> | > Thank you for your detailed email.  According to the JSON specification,
> | > at http://www.json.org/, and also RFC 4627, there are no comment
> | > structures in JSON.
> | 
> | Wow, color me surprised!  If JSON wants to shoot themselves in the foot in our
> | favor, great!
> 
> Douglas Crawford has been quite helpful in working through issues to
> increase compatibility with YAML.  So have many of the JSON serializer
> authors, such as Bob Ippolito, who have done things (such as using a
> space after colon and commas) to improve YAML compatibility. 
> 
> A few of us have even discussed a JSON++/YAML-- that maintains the same
> minimalistic parsing requirement as JSON, but uses the YAML information
> model -- permitting structured keys, graph structures via an alias/ref,
> and a type declaration method for indicating data types.  It's really
> just finding time [1].
> 
> I've got nothing but praises to sing for the JSON people with whom I've
> had the pleasure of interacting.

Didn't mean to come off snarky, but it does seem like a Very Bad Idea to have
a commentless format.  Either way, I withdraw my request to add JSON
compatible comments as it has already been handled.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/