ISSUE-38: Section 3.4: Third party services are SPARQL endpoints
Section 3.4: Third party services are SPARQL endpoints
- State:
- CLOSED
- Product:
- Accessing and Querying Provenance
- Raised by:
- Khalid Belhajjame
- Opened on:
- 2011-07-22
- Description:
- It seems that SPARQL was chosen as a means for retrieving the provenance URI of a given resource. Do we need to be prescriptive about the kind of third-party service used to access provenance?
I don’t mind using it as a possible means, but if I understood well the text on Section 3.4, it seems that third party services providing information about resource provenance needs to be a SPARQL end point.
Khalid - Related Actions Items:
- No related actions
- Related emails:
- Closing issues on PROV-AQ (from graham.klyne@zoo.ox.ac.uk on 2011-12-01)
- Reviewing outstanding issues on PAQ document. (from GK@ninebynine.org on 2011-09-15)
- Re: PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-07-28)
- Re: PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-07-28)
- Re: PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance] (from mccusj@rpi.edu on 2011-07-24)
- Re: PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance] (from Khalid.Belhajjame@cs.man.ac.uk on 2011-07-24)
- Re: PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-07-24)
- PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2011-07-22)
Related notes:
I believe this has been addressed though a general reorganization of the document. An alternative simple HTTP-based mechanism is also proposed.
Graham Klyne, 5 Aug 2011, 11:36:08Display change log