PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance]

PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance]

http://www.w3.org/2011/prov/track/issues/77

Raised by: Luc Moreau
On product: Accessing and Querying Provenance


Terminology is not always used consistently. Sometimes, it's confusing. I group all these comments in a single issue.

To start with, the word "context" which is overloaded.  Furthermore, some sentences have two occurrences of this word, one with the technical meaning, one with the common sense meaning. In fact, we used to have a good term, "subject of provenance", which we could consider here.

Why do we have location_template and provenance_template?
Shouldn't they be provenance_location_template and provenance_content_template?
Both are indeed related to provenance.  

The discovery service is sometimes referred to as discovery and retrieval service.  Shouldn't it be consistently referred as discovery and retrieval service? But this is also referred to as provenance service.

The text seems to make the distinction between resource-uri and context-uri. But isn't it the case that a resource-uri is a context-uri?

Provenance resource is also mentioned. Is this provenance information?

Can we have a better name than provenance-location-uri? First, shouldn't we say provenance-locations-uri?  this would allow us to see that several locations are permitted (whereas we have a singe provenance information template). Is location the right term? why not set provenance-uri?

Received on Monday, 22 August 2011 22:30:52 UTC