Re: Split JSON-LD spec

On 9/1/11 8:32 AM, Markus Lanthaler 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)
+1

But maybe Syntax instead of Language.

>   2. JSON-LD Processing (APIs, algorithms, etc.)

+1

> 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.

+1

> 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.

Boiler room items.

> In my opinion, splitting the spec would definitely be beneficial for the
> adoption of JSON-LD.

+1

>   It also allows us to get more insights (and time) for
> the tricky parts if we release the JSON-LD language spec first.
s/Language/Syntax .

>   Designing
> good APIs for something that hasn't existed and hasn't been used before is
> not a trivial task.

+1

> Please note that I'm strictly against about having a basic and an advanced
> spec. Think of it more as "separation of concerns".

Yes!


Kingsley
>
> If there is enough interest, I will create a draft of the specs as a base
> for further discussion.
>
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
>
>


-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen