ISSUE-416: how does prov-aq work with content negotiation


how does prov-aq work with content negotiation

Accessing and Querying Provenance
Raised by:
Paul Groth
Opened on:
What does prov-aq say? Do we return the provenance of the resource or the representation? This should be clarified.
Related Actions Items:
No related actions
Related emails:
  1. PROV-ISSUE-416 (contentnegotiation): how does prov-aq work with content negotiation [Accessing and Querying Provenance] (from on 2012-06-20)

Related notes:

What's not clear? PROV-AQ uses HTTP and HTTP defines content negotiation. Can you at least indicate *where* in the document some clarification might be in order?

Graham Klyne, 21 Jun 2012, 10:04:45

Lacking further input, I propose to close without further action.

Graham Klyne, 6 Nov 2012, 15:32:23

The issue here is: what happens when content negotiation takes place when retyrievibng the resource about which provenance is available. Need to note:

1. That Link: headers for provenance should not be relied upon in any 303 redirect responses, as these are generally not visible to Javascript apps in browsers
2. That returned provenance information refers to the resource identified by the target-URI rather than its representation (if these are different). Note that a separate URI MAY be used for the representation if separate provenance is required.

Graham Klyne, 14 Nov 2012, 22:00:12

Status changed to OPEN

Graham Klyne, 14 Nov 2012, 22:00:32

A new section 3.1.2 has been added describing this. Also tweaked some text in section 3.

Graham Klyne, 19 Nov 2012, 13:25:49

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: 416.html,v 1.1 2013-06-20 07:37:43 vivien Exp $