ISSUE-609: Specify how to locate a SPARQL endpoint for querying provenance
sparql-endpoint-uri
Specify how to locate a SPARQL endpoint for querying provenance
- State:
- PENDING REVIEW
- Product:
- Accessing and Querying Provenance
- Raised by:
- Graham Klyne
- Opened on:
- 2012-11-29
- Description:
- See:
http://lists.w3.org/Archives/Public/public-prov-wg/2012Nov/0313.html
http://lists.w3.org/Archives/Public/public-prov-wg/2012Nov/0314.html
et seq.
- Related Actions Items:
- No related actions
- Related emails:
- PROV-AQ issues pending review (from graham.klyne@zoo.ox.ac.uk on 2013-03-11)
- Re: PROV-AQ SPARQL endpoint discovery (ISSUE-609) (from GK@ninebynine.org on 2012-12-16)
- Re: PROV-AQ SPARQL endpoint discovery (ISSUE-609) (from pgroth@gmail.com on 2012-12-13)
- Re: PROV-AQ SPARQL endpoint discovery (ISSUE-609) (from lebot@rpi.edu on 2012-12-11)
- PROV-AQ SPARQL endpoint discovery (ISSUE-609) (from GK@ninebynine.org on 2012-12-10)
- PROV-ISSUE-609 (sparql-endpoint-uri): Specify how to locate a SPARQL endpoint for querying provenance [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2012-11-29)
Related notes:
Further proposal at http://lists.w3.org/Archives/Public/public-prov-wg/2013Jan/0002.html
Main points:
- propose to use single link relation type for provenance service via template and SPARQL endpoint
- stick with RDF for service description (there's some uncertainty about this among some LDPers)
- expand service description to allow either or both service option
- service description with URI template unchecked (but see below)
- SPARQL service description per http://www.w3.org/TR/sparql11-service-description/ (i.e. nothing new here)
Outstanding question: prov:ProvenanceService as RDF type: applies tom all service options or just templated service? If the latter, then no change. If the former, I propose to introduce a new type that applies to just the template version of the interface.
I think this is substantially covered by recent query service component changes, which were generally following feedback from the WG and discussion with LDP participants. Some further name-changes are in the works, but I think the basic mechanism (service description) is now in place.
I'll mark this as pending review when the current round of document edits are done.
Display change log
