W3C home > Mailing lists > Public > public-linked-json@w3.org > September 2011

Re: Split JSON-LD spec

From: Alexandre Passant <alex@seevl.net>
Date: Fri, 2 Sep 2011 00:21:16 +0200
Message-Id: <CCB45C19-C9E6-4ACF-B3F3-0908DDB627C4@seevl.net>
Cc: Linked JSON <public-linked-json@w3.org>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Hi

On 1 Sep 2011, at 17:32, "Markus Lanthaler" <markus.lanthaler@gmx.net> wrote:

> Hi all,
> 
> I thought a bit more about the recent discussions here on the mailing list
> and came to the conclusion that it might be better to split the JSON-LD spec
> into two parts:
> 
> 1. JSON-LD (the language)

What about "JSON-LD Publishing" ? So that the title of both documents is straightforward to understand depending which side you're in

Alex.

> 2. JSON-LD Processing (APIs, algorithms, etc.)
> 
> I think doing so would reflect the fact that different people are interested
> in different aspects of JSON-LD. Of course, everyone has to understand
> JSON-LD the language, thus we should really put a strong emphasis on a
> simple, short, and easy to understand spec for that.
> 
> On the other hand there are some other aspects which I think are also
> important to standardize (think normalization, framing, etc.) but which are
> much more complex and only a few people actually have to read and understand
> how all this works.
> 
> In my opinion, splitting the spec would definitely be beneficial for the
> adoption of JSON-LD. It also allows us to get more insights (and time) for
> the tricky parts if we release the JSON-LD language spec first. Designing
> good APIs for something that hasn't existed and hasn't been used before is
> not a trivial task.
> 
> Please note that I'm strictly against about having a basic and an advanced
> spec. Think of it more as "separation of concerns".
> 
> 
> If there is enough interest, I will create a draft of the specs as a base
> for further discussion.
> 
> 
> 
> --
> Markus Lanthaler
> @markuslanthaler
> 
> 
> 
> 
> 
Received on Thursday, 1 September 2011 22:21:48 UTC

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