- From: Gregg Kellogg <gregg@kellogg-assoc.com>
- Date: Fri, 8 Jul 2011 13:42:50 -0400
- To: Niklas Lindström <lindstream@gmail.com>
- CC: Alexandre Passant <alex@seevl.net>, "public-linked-json@w3.org" <public-linked-json@w3.org>
With some minor processing rule changes, this could just use regular @context term/prefix definitions.
{ "iri": "@source" ...}
Gregg Kellogg
Sent from my iPhone
On Jul 8, 2011, at 9:52 AM, "Niklas Lindström" <lindstream@gmail.com> wrote:
> Hi,
>
> On Fri, Jul 8, 2011 at 5:07 PM, Alexandre Passant <alex@seevl.net> wrote:
>> Hi all,
>>
>> 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.
>> [...]
>> I will make the spec more flexible as allowing people to use the
>> naming they prefer - while keeping the RDF similar.
>
> Absolutely. I do a similar thing in the new Gluon profile sketch at [1]:
>
> "reserved": {
> "vocab": "vocab",
> "about": "id",
> "multipleSuffix": "Set",
> ...
>
> (as mentioned in [2]).
>
> Best regards,
> Niklas
>
> [1]: http://code.google.com/p/oort/source/browse/etc/gluon/drafts/profile-redesign.json?r=b7e4f413603a
> [2]: http://dustfeed.blogspot.com/2011/07/resources-in-various-frames-of-json.html
>
Received on Friday, 8 July 2011 17:43:45 UTC