ISSUE-432: Is http get the correct form for the provenance service
post-or-get
Is http get the correct form for the provenance service
- State:
- CLOSED
- Product:
- Accessing and Querying Provenance
- Raised by:
- Paul Groth
- Opened on:
- 2012-06-23
- Description:
- According to REST principles one should not create side-effects when using GET. The question is does this apply to provenance-service.
Also, should POST be supported as well as GET in the provenance service. - Related Actions Items:
- No related actions
- Related emails:
- Re: PROV-ISSUE-432 (post-or-get): Is http get the correct form for the provenance service [Accessing and Querying Provenance] (from graham.klyne@zoo.ox.ac.uk on 2012-06-23)
- Re: PROV-ISSUE-432 (post-or-get): Is http get the correct form for the provenance service [Accessing and Querying Provenance] (from gklyne@googlemail.com on 2012-06-23)
- Re: PROV-ISSUE-432 (post-or-get): Is http get the correct form for the provenance service [Accessing and Querying Provenance] (from gklyne@googlemail.com on 2012-06-23)
- Re: PROV-ISSUE-432 (post-or-get): Is http get the correct form for the provenance service [Accessing and Querying Provenance] (from p.t.groth@vu.nl on 2012-06-23)
- Re: PROV-ISSUE-432 (post-or-get): Is http get the correct form for the provenance service [Accessing and Querying Provenance] (from mccusj@rpi.edu on 2012-06-23)
- PROV-ISSUE-432 (post-or-get): Is http get the correct form for the provenance service [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2012-06-23)
Related notes:
Seeing no dissent, I propose to close this without further action. (GET is OK.)
Graham Klyne, 6 Nov 2012, 16:41:30Discussed with proposer - agreed it's OK as is.
If provenance information is updating dynamically, and/or is being generated on-the-fly, and may vary from request to request, the provenance service should include appropriate HTTP cache control headers its its response.
Display change log
