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

Re: Agenda: Linked JSON Telecon - Tuesday, December 20th 2011

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Sun, 18 Dec 2011 00:29:28 -0500
To: Manu Sporny <msporny@digitalbazaar.com>
CC: Linked JSON <public-linked-json@w3.org>
Message-ID: <194B36E7-C808-4158-B032-4D1ED75535A2@kellogg-assoc.com>
Regrets for Tuesday. I've made some notes on my positions below

Gregg

On Dec 13, 2011, at 9:45 PM, Manu Sporny wrote:

> Hi all,
> 
> Here is our Agenda for next week. We'll continue working through the
> issues list.
> 
> Information on how to join the call and previous minutes and audio logs
> can be found here:
> 
> http://json-ld.org/minutes/
> 
> The preliminary agenda is below. Please respond to this e-mail if you
> want to add something to the Agenda or if you have any questions.
> 
> ==========
> Tuesday, December 20th 2011
> Time: 1500 UTC, 7am San Francisco, 10am Boston, 3pm London
> Digital Bazaar Telecon Bridge
>    SIP: json-ld@digitalbazaar.com
>    Phone US: +1.540.961.4469 x6303
> irc://freenode.net/#json-ld
> Duration: 60 minutes
> Scribes: Tom, Dave, Gregg, Manu, Niklas, Markus
> ==========
> 
> Agenda
> 
> 1. ISSUE-16: Linking Instance Documents and Context Documents
>    * https://github.com/json-ld/json-ld.org/issues/16
> 2. ISSUE-41: IRI expansion within @context
>    * https://github.com/json-ld/json-ld.org/issues/41

Some dependence on resolving references of things defined in the same context. If there is a clean way to do this, great, otherwise we should probably avoid it.

One way would be to resolve non-object values in @context first and then use this to resolve uses within object (and potentially key positions).

Another would be to just loop until all dependencies are resolved and abort if a loop is made without any further resolutions.

> 3. ISSUE-42: Distinguishing a JSON-LD frame from a JSON-LD document
>    * https://github.com/json-ld/json-ld.org/issues/42
> 4. ISSUE-43: Use of IRIs and CURIEs as @context keys
>    * https://github.com/json-ld/json-ld.org/issues/43

I believe we should allow CURIEs and URIs in the key position within @context, which makes the @id key unnecessary. Chained dependencies are similar to that discussed for @id resolution and should use the same logic.

> -- manu
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: The Need for Data-Driven Standards
> http://manu.sporny.org/2011/data-driven-standards/
> 
> 
Received on Sunday, 18 December 2011 05:30:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:32 UTC