All things being equal, I would prefer a Lisp-based format rather than
JSON, yes. (My involvement with that approach goes back 25 years:
https://en.wikipedia.org/wiki/Electronic_Design_Interchange_Format )
But EDN + this convention would be something only my software would
support, and anyone I
How about format which can represent either graph or structure, depending
on users needs? I would argue that EDN is more suitable for linked data
than JSON is. Its support for identifiers and tagged elements allows for
pretty straightforward serialization of linked data.
See https://gist.github
Now *that* is a pretty reasonable comparison. I would quibble here and
there: I don't find JSON-LD as heavy-weight as you; the benefit of
universal identifiers is an advantage in the domains I work in; and the
whole graph vs. struct debate... it's a lot easier to represent a struct as
a simple
Well the suggestion to consider JSON-LD was really out of place. Compared
to JSON-LD, EDN belongs to the category of lightweight, schemaless and
streaming friendly data serialization formats. JSON-LD is closer to e.g.
Turtle or RDF/XML. It serves a different purpose and has different goals
than
Brilliant analysis.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group
JSON-LD is an XML stack in JSON clothes, chained to the rusty bandwagon
called Semantic Web. For me, it is a step backwards.
Jozef
On Sat, May 31, 2014 at 4:59 AM, Patrick Logan
wrote:
> Jozef,
>
> You might be interested in the JSON-LD w3c standard which defines
> representations for most of
Jozef,
You might be interested in the JSON-LD w3c standard which defines
representations for most of the items in your table using JSON. Primarily
missing are "discards" and direct ties to clojure/script functions and
macros.
JSON-LD has several implementations, a test suite, and support of s
I've put together a table comparing JSON, EDN and CLJ formats based on
their specs [1]. Pull requests are welcome.
Jozef
[1] https://github.com/wagjo/serialization-formats
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send
