W3C home > Mailing lists > Public > public-linked-json@w3.org > December 2014

Re: Limitations on JSON which conforms to JSON-LD spec?

From: Nicholas Bollweg <nick.bollweg@gmail.com>
Date: Mon, 1 Dec 2014 18:17:46 -0500
Message-ID: <CACejjWx9t8h68oU+fsZz4aAwzWPgHiwekzMkZV13meofmbMm_w@mail.gmail.com>
To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Cc: public-linked-json <public-linked-json@w3.org>
As we have seen a number of times here on the list, objects made from an
unknowably large set of of keys are hard to do anything compelling with...
see package.json//dependencies/, ipython.ipynb//cells/output/data/.

On Mon, Dec 1, 2014 at 5:57 PM, ☮ elf Pavlik ☮ <
perpetual-tripper@wwelves.org> wrote:

> Hello,
>
> I would like to clarify, for conversations in Social WG, what
> limitations JSON-LD puts on JSON.
>
> Currently I can only recall one related to list of lists
> http://www.w3.org/TR/json-ld/#h_note_8
>
> Any other limitations?
>
> Social WG charter states[1]:
> *Social Data Syntax* - A JSON-based syntax to allow the transfer of
> social information, such as status updates, across differing social
> systems. One input to this deliverable is ActivityStreams 2.0
>
> While discussing benefits of building around JSON-LD, I would also like
> that we can stay very clear about all the possible drawbacks.
>
> Thank you for all relevant references and comments!
>
> [1] http://www.w3.org/2013/socialweb/social-wg-charter.html#deliverables
>
>
Received on Monday, 1 December 2014 23:18:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:53:26 UTC