ISSUE-11: Is the provenance requirement in scope?

provenance

Is the provenance requirement in scope?

State:
CLOSED
Product:
Use Cases and Requirements
Raised by:
Frans Knibbe
Opened on:
2015-05-11
Description:
Currently, there is a requirement about provenance (http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#Provenance):

"It should be possible to add provenance metadata."

This seems not to be special for spatiotemporal data. Shall we remove this requirement because it is not in scope?
Related Actions Items:
No related actions
Related emails:
  1. FW: "Year", "January" - RE: Time Ontology outstanding Issue 11 (from kerry.taylor@anu.edu.au on 2016-12-22)
  2. RE: "Year", "January" - RE: Time Ontology outstanding Issue 11 (from kerry.taylor@anu.edu.au on 2016-12-22)
  3. RE: Requirement for 'Valid Time' Issue-16 (from chris.little@metoffice.gov.uk on 2015-11-11)
  4. Re: Requirement for 'Valid Time' Issue-16 (from frans.knibbe@geodan.nl on 2015-11-11)
  5. Re: Requirement for 'Valid Time' Issue-16 (from frans.knibbe@geodan.nl on 2015-11-11)
  6. RE: Requirement for 'Valid Time' Issue-16 (from chris.little@metoffice.gov.uk on 2015-11-11)
  7. Re: Requirement for 'Valid Time' (from frans.knibbe@geodan.nl on 2015-11-11)
  8. [Minutes] 2015-07-22 (from phila@w3.org on 2015-07-22)
  9. Likely regrets (was: [sdwwg] meeting tomorrow) (from andrea.perego@jrc.ec.europa.eu on 2015-07-22)
  10. Re: [sdwwg] meeting tomorrow (from bill@swirrl.com on 2015-07-21)
  11. [sdwwg] meeting tomorrow (from kerry.taylor@acm.org on 2015-07-21)
  12. Re: Frozen copy? (from frans.knibbe@geodan.nl on 2015-06-10)
  13. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from frans.knibbe@geodan.nl on 2015-05-28)
  14. RE: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from Simon.Cox@csiro.au on 2015-05-27)
  15. RE: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from Simon.Cox@csiro.au on 2015-05-27)
  16. RE: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from Kerry.Taylor@csiro.au on 2015-05-27)
  17. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from andrea.perego@jrc.ec.europa.eu on 2015-05-27)
  18. RE: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from Kerry.Taylor@csiro.au on 2015-05-25)
  19. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2015-05-21)
  20. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from gil@isi.edu on 2015-05-21)
  21. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from andrea.perego@jrc.ec.europa.eu on 2015-05-21)
  22. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from jlieberman@tumblingwalls.com on 2015-05-20)
  23. RE: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from Kerry.Taylor@csiro.au on 2015-05-20)
  24. Re: UCR isssue: Is provenance in scope? [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2015-05-18)
  25. RE: UCR isssue: Is provenance in scope? (from Kerry.Taylor@csiro.au on 2015-05-13)
  26. Re: UCR isssue: Is provenance in scope? (from frans.knibbe@geodan.nl on 2015-05-13)
  27. Re: UCR isssue: Is provenance in scope? (from jlieberman@tumblingwalls.com on 2015-05-13)
  28. UCR isssue: Is provenance in scope? (from frans.knibbe@geodan.nl on 2015-05-13)

Related notes:

Discussion seems to indicate that provenance is in scope if we consider alignment of existing models for provenance that exist in the geospatial (OGC) and the semantic web (W3C) domains.

Therefore the following proposal for rephrasing the requirement:

"Ensure alignment of models or vocabularies for describing provenance that exist in the geospatial and semantic web domains. Examples are the W3C provenance ontology (PROV-O) and the OGC metadata specfication (ISO-19115)"

With this phrasing the only deliverable this requirement is related to is the Best Practices.

Frans Knibbe, 28 May 2015, 09:55:41

A correction on the previous note that said the the Best Practices deliverable is the only related deliverable when the proposed description is accepted: Other deliverables foresee work on vocabularies that might have elements of provenance. That means that the proposed description should be related to all deliverables.

Frans Knibbe, 22 Jul 2015, 08:54:47

The proposed solution was accepted in the weekly meeting of 2015-07-22

Frans Knibbe, 22 Jul 2015, 14:08:12

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 <w3t-sys@w3.org>.
$Id: 11.html,v 1.1 2018/10/09 10:07:47 carine Exp $