ISSUE-77: terminology issues


terminology issues

Accessing and Querying Provenance
Raised by:
Luc Moreau
Opened on:
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?

Related Actions Items:
No related actions
Related emails:
  1. Reviewing outstanding issues on PAQ document. (from on 2011-09-15)
  2. Re: PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance] (from on 2011-08-26)
  3. Re: PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance] (from on 2011-08-26)
  4. Re: PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance] (from on 2011-08-25)
  5. PROV-ISSUE-77 (paq-terminology): terminology issues [Accessing and Querying Provenance] (from on 2011-08-22)

Related notes:

I believe these issues have now been addressed throughout the document. Section 1.1 summarizes the key concepts and terminology used.

Graham Klyne, 1 Dec 2011, 13:25:14


Graham Klyne, 5 Jan 2012, 11:13:39

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 77.html,v 1.1 2013-06-20 07:38:00 vivien Exp $