Re: JSYNC 1.0 Specification

Ingy dot Net <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <[email protected]>
On Fri, Jun 18, 2010 at 5:38 PM, Brad Baxter <[email protected]> wrote:
> On Thu, Jun 17, 2010 at 8:28 PM, Ingy dot Net <[email protected]> wrote:
>> I have spent much of yesterday and today putting together a JSYNC
>> Spec. I would be most happy if those interested would review it and
>> comment.
>
> I think the language is clear, and it seems to accomplish the design
> goal: Be a minimal extension of JSON.  I look forward to a Perl
> implementation.  :-)

I already started working on (and pushed out to CPAN and GitHub) a
currently fairly useless Perl implementation. I hope to create
equivalent Perl Python Ruby and JS impls over the next week.

> Out of curiosity, I'd like to see the results of these round trips:
>
> YAML1 => object => JSYNC => object => YAML2 => object
>
> JSYNC1 => object => YAML => object => JSYNC2 => object
>
> If every object is identical, it's probably moot how closely YAML1
> matches YAML2 and JSYNC1 matches JSYNC2, but it'd be
> interesting to see.

I hope that JSYNC dev, pushes YAML dev to this obvious desired conclusion.

Ingy

>
> Brad
>

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.