- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Tue, 13 Nov 2012 14:58:13 +0100
- To: "'Manu Sporny'" <msporny@digitalbazaar.com>, "'Linked JSON'" <public-linked-json@w3.org>
- Cc: "'RDF WG'" <public-rdf-wg@w3.org>
Hi,
> There has been a flurry of activity on the JSON-LD issue tracker, which
> is great - lots of progress being made. We have a few outstanding
> issues
> that probably need telecon time to be resolved, the biggest of which is
> the Drupal use case for language maps, annotations, and/or graphs. This
> week will be a 90-minute call.
I would like to resolve those issues at the beginning of the call. Here are all issues we have concrete proposals for and seem to have consensus:
-- Syntax Spec --
ISSUE-165: Allow @id: null to decouple a term from @vocab
ISSUE-166: Add a conformance section
ISSUE-169: Clarify the meaning of multiple node definitions with the same @id
ISSUE-180: Make link to RDF more apparent in the specification
ISSUE-181: Limit divergence between JSON-LD and RDF data models
ISSUE-182: Graph vs DataSet
ISSUE-189: Support of {@type:{@id:xxx}} constructs
ISSUE-133: Add '@language' container type (related to ISSUE-159)
-- API Spec --
ISSUE-178: Consider renaming JSON-LD API to JSON-LD Core Processing
ISSUE-179: Consider moving WebIDL to Appendix or Note
ISSUE-184: Definition of JSON-LD processor in the Syntax doc
Since not everyone voted directly in the issue tracker I would like to resolve them on today's telecon so that we can start updating the specs accordingly. It looks like a lot but I think we can resolve all of this quite quickly (half an hour maybe).
Thanks,
Markus
--
Markus Lanthaler
@markuslanthaler
Received on Tuesday, 13 November 2012 13:58:55 UTC