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

Re: About @type, @ and other tokens

From: Alexandre Passant <alex@seevl.net>
Date: Mon, 11 Jul 2011 15:42:45 +0100
Message-ID: <CALF6uCnO31JXhudp2xWz8-hvZqvanuTYSk9hbnRkFjR0WdHZgw@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: public-linked-json@w3.org
Hi,

On Mon, Jul 11, 2011 at 1:10 AM, Manu Sporny <msporny@digitalbazaar.com> wrote:
> On 07/08/2011 11:07 AM, Alexandre Passant wrote:
>> Regarding the "@source instead of @" and "@type instead of a" issues
>> on the current spec.
>> I'd favor a way to let this be defined in a context, in addition to
>> the default value.
>>
>> E.g.
>>
>> {
>>   "@context":
>>   {
>>      "#tokens":
>>      {
>>        "@" : "uri",
>>        "@type" : "type"
>>      }
>>   }
>> }
>
> Why not just this?
>
> "@context":
> {
>   "@subject": "iri",
>   "@type": "a",
>   "@datatype": "type",
>   ...
> }
>
> Granted, this could be considered confusing as the keywords mean
> something very different when used in the context than elsewhere, but
> the same concern applies to their use in #tokens above.

Yes, I put the proposal into #tokens to differentiate between normal
keywords and reserve one but that's a matter of taste. Gregg's
proposal also makes sense here.

>
>> I will make the spec more flexible as allowing people to use the
>> naming they prefer - while keeping the RDF similar.
>
> If we do this, I think that we should declare some good defaults so that
> people don't have to declare a "@context" if they don't want to do so.

Sure

>
> I'm also concerned that this feature may not be as useful as we think it
> may be. That is, can somebody show us a use case that exists today that
> would benefit from this feature? I'm sure one exists, but I'd like to
> see how it could be applied to a major JSON Web services deployment
> (like Twitter, Google maps, Facebook, etc.)

See for instance he JSON from Flickr.

www.flickr.com/services/api/response.json.html

In the blogs example, "uri" would be the @subject in that case.

I think we can find similar use-cases in other deployments.

Alex.

>
> -- 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 14:43:13 UTC

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