  PROV-O in Callimachus  From: James Leigh
<james@3roundstones.com> Date: Thu, 04 Oct 2012 13:58:57 -0400
Message-ID: <1349373537.2118.73.camel@james-PBL21>  I wanted to
share some feedback on PROV-O now that we have some experience
integrating it into Callimachus.  Can PROV-O be used to capture
contributors to a resource over time, if each of the resource
revisions is not represented with a unique entity?  The
semantics of prov:used and prov:wasInformedBy seem too weak at
times. However, the prov:generated is too strong for our use
case.  For example, the way a cooking activity uses a spoon is
very different from how it uses a bag of flour. That is to say a
spoon's state is (to a large degree) unchanged after cooking
with it, but the state of a bag of flour (in many cases) may
change.  What is the recommended way to capture these consumable
resources? Must different entity URIs be used to represent the
bag of flour before and after it was used? Is there any way to
say an activity changed the state of a resou