ISSUE-620: Should PRIV-AQ bless use of JSON-LD for service description?

json-ld-service-description

Should PRIV-AQ bless use of JSON-LD for service description?

State:

CLOSED

Product:

Accessing and Querying Provenance

Raised by:

Graham Klyne

Opened on:

2013-01-31

Description:

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?

Related Actions Items:

No related actions

Related emails:

1. Re: PROV-ISSUE-620 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance] (from ivan@w3.org on 2013-02-04)
2. Fwd: Re: PROV-ISSUE-622 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance] (from graham.klyne@zoo.ox.ac.uk on 2013-02-01)
3. Re: PROV-ISSUE-620 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance] (from soiland-reyes@cs.manchester.ac.uk on 2013-02-01)
4. PROV-ISSUE-620 (json-ld-service-description): Should PRIV-AQ bless use of JSON-LD for service description? [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2013-01-31)

Related notes:

Display change log