- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Fri, 1 Feb 2013 16:31:19 +0000
- To: Provenance Working Group <public-prov-wg@w3.org>
As a note, here is how the Open Annotation spec defines their JSON-LD serialization: http://www.openannotation.org/spec/future/publishing.html#Serialization (note that the URL http://www.w3.org/ns/openannotation/core/context-20130204.json does not reference as this is still a community draft) On Thu, Jan 31, 2013 at 5:23 PM, Provenance Working Group Issue Tracker <sysbot+tracker@w3.org> wrote: > PROV-ISSUE-620 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance] > > http://www.w3.org/2011/prov/track/issues/620 > > Raised by: Graham Klyne > On product: Accessing and Querying Provenance > > In http://lists.w3.org/Archives/Public/public-prov-wg/2013Jan/0121.html, around issues 42) and/or 43), Stian has proposed specifying use of JSON-LD as a format for service descriptions. I'll paste the specific proposal as a separate comment to this issue. > > I note that such use of JSON-LD is not disallowed by the current specification, just not explained. The general recommendation is that service descriptions are presented as RDF, though other formats are negotiable in keeping with REST principles. JSON-LD would be a specific [presentation of RDF. > > The question is: should we consider making specific mention of JSON-LD for service descriptions? Considerations would include: > - does it make the specification more complex? > - does it make the specification more presriptive? Is this desirable? > - is JSON-LD sufficiently well-used to be considered a blessed format fort RDF data? > - should we wait to see what consensus the W3C LDP group may form around the general topic of linked data service descriptions? > > > > -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester
Received on Friday, 1 February 2013 16:32:07 UTC