W3C home > Mailing lists > Public > public-linked-json@w3.org > January 2015

Re: yaml-ld?

From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Date: Fri, 23 Jan 2015 09:54:07 +0000
Message-ID: <CAPRnXtmu36hy5DTHh3Bx57OD81eyHXJft9T9A3G9XtfAPNcjQg@mail.gmail.com>
To: "David I. Lehn" <dil@lehn.org>
Cc: Linked JSON <public-linked-json@w3.org>, Peter Amstutz <peter.amstutz@curoverse.com>
Agree about hand editing, the two big pains in JSON are the "quotes"
required for keys, : required, and that lists/objects can't end with ,
(arrrrgh). Editor syntax highlight helps.

The sandbox is also better now at explaining JSON errors.

You can avoid quoting for "@id" by mapping "id": "@id".

Does YAML allow some forms which can't exist easily in JSON, like mixing
lists and objects?

I would not expect to see "YAML-LD" published as Linked Data, that would be
confusing the landscape, but as a format you "compile" to JSON-LD, great!
On 22 Jan 2015 18:08, "David I. Lehn" <dil@lehn.org> wrote:

> On Thu, Jan 22, 2015 at 11:03 AM, peter <peter.amstutz@curoverse.com>
> wrote:
> > Has anyone tried using yaml (http://www.yaml.org/) as an alternate
> > serialization to express json-ld structured data?  Are there any
> > pitfalls to this approach?
> >
> Sometimes I convert between JSON-LD to YAML just because YAML is
> usually more compact and easier to read and write.  It's easy to
> convert back and forth.  One pitfall is that unfortunately you do need
> to quote all the keywords starting with '@'.  I've just used the basic
> syntax but more advanced features like types and linking could
> probably be used to do interesting things.  I have wanted to add YAML
> input/output support to the playground but haven't found time to do
> it.
> -dave
Received on Friday, 23 January 2015 09:54:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:43 UTC