Re: PROV-O

Greetings All,

Long time list reader, first time poster. I would second the suggestion of
using PROV to the endpoint relation provenance. We currently are using a
small part of Hydra Core to describe an endpoint that provides provenance
information about scientific computational workflows. We've done that by
subclassing PROV:Activity to create ca:ComputationalActivity in the same
way (I think) you suggest defining hydra:"FilterActivity".  I think having
a natural hook between Hydra Core classes and PROV would be a useful thing.
We also had considered using PROV to track changes in the API (one version
is derived from another) itself by tracking the Hydra information object.

--Chuck

On Thu, 4 Feb 2016 at 07:09 Asbjørn Ulsberg <asbjorn@ulsberg.no> wrote:

> 2016-02-03 23:24 GMT+01:00 Maik Riechert <maik.riechert@arcor.de>:
>
> > I just read up a bit on the PROV ontology (https://www.w3.org/TR/prov-o)
> and
> > was wondering if this was ever considered [...]
>
> I've not seen it discussed here before and to me it looks like a great
> fit as a base for Hydra Core. Thanks for pointing it out!
>
> --
> Asbjørn Ulsberg           -=|=-        asbjorn@ulsberg.no
> «He's a loathsome offensive brute, yet I can't look away»
>
> --

—————————————————
Charles F. Vardeman II, Ph.D.
Computational Scientist, Center for Research Computing
Research Assistant Professor, Computer Science and Engineering
University of Notre Dame
charles.vardeman@gmail.com