- From: Alexandre Passant <alex@seevl.net>
- Date: Mon, 11 Jul 2011 20:11:19 +0100
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: public-linked-json@w3.org
On Mon, Jul 11, 2011 at 1:02 AM, Manu Sporny <msporny@digitalbazaar.com> wrote:
> On 07/06/2011 11:46 AM, glenn mcdonald wrote:
>> If it's a goal to be able to impose context on an "existing" JSON
>> feed, it might be even more effective, instead of allowing @context
>> to point to an external file, to invert this and have a context file
>> that can point to a data file. That way the data file itself can be
>> completely untouched.
>
> Would something like this work for you, Glenn?
>
> {
> "@context": "http://example.org/microblog",
> "@data": "http://foo.bar/posts/15"
> }
>
That would mean that you have a new file saying where's the context
and where's the data ?
In that case, how could you get the context from a data file ? (or
Manu, are you also thinking of the headers thing I mentioned)
Alex.
> I'm not saying that we should do that - just wondering if this is the
> type of data mashing you were thinking of doing with this feature?
> Context comes from one location, data from another.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny)
> President/CEO - Digital Bazaar, Inc.
> blog: PaySwarm Developer Tools and Demo Released
> http://digitalbazaar.com/2011/05/05/payswarm-sandbox/
>
>
--
Dr. Alexandre Passant - @terraces
Founder, CEO - seevl.net - @seevl
Reinventing Music Discovery
Received on Monday, 11 July 2011 19:11:51 UTC