Fwd: Embrace YAML or Hedge on JSON
Trans <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <CAEu+kw0ixuokzcC4z4Lq-HSe52gLcauzvo4nuTewFX8Wn9vFow@mail.gmail.com> |
On Mon, Aug 6, 2012 at 1:51 PM, Ingy dot Net <[email protected]> wrote: > JSON *is* YAML. You can't embrace YAML without supporting JSON :) JSON *is* "Simple YAML". If I use tags it's no longer "JSONable". > Also, what about JSYNC? http://jsync.org It's funny you should mention it b/c I just thought of that too. And I think I might go that route b/c I also realized that I can't guarantee that a YAML implementation won't throw an error if it doesn't recognize a tag. Ruby's Psych will just ignore it, but I don't think there is any kind of standard around that behavior is there? > Both of these examples drive home the need for YAML/JSON/JSYNC schema. If there were a YPath to work with (and in my case I need a Ruby implementation), I think I could have the YES schema project I've been working on in beta shape in only a few days. I also discovered this: http://tools.ietf.org/html/draft-zyp-json-schema-03, which looks like it has a few ideas I can use to polish off YES. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/