Re: PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance]

I've revised the text at 
http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html#third-party-services:

[[
We assume that the application or person requesting provenance information has 
the URI or other unique identification of the resource for which provenance is 
required, and also has a URI for a third-party service that provides a 
provenance information service. The nature of this third party service is an 
implementation choice, to be agreed between provider and users of the service, 
but for ease of interoperation we recommend use of SPARQL [RDF-SPARQL-PROTOCOL] 
[RDF-SPARQL-QUERY]. The third party service URI would then be the URI of a 
SPARQL endpoint (or, to use the SPARQL specification language, a SPARQL protocol 
service) which is queried for the desired provenance information.
]]

#g


Provenance Working Group Issue Tracker wrote:
> PROV-ISSUE-38: Section 3.4: Third party services are SPARQL endpoints [Accessing and Querying Provenance]
> 
> http://www.w3.org/2011/prov/track/issues/38
> 
> Raised by: Khalid Belhajjame
> On product: Accessing and Querying Provenance
> 
> 
> 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
> 
> 
> 
>

Received on Thursday, 28 July 2011 12:59:24 UTC