- From: Luc Moreau <l.moreau@ecs.soton.ac.uk>
- Date: Wed, 21 Nov 2012 16:15:58 +0000
- To: Jun Zhao <jun.zhao@zoo.ox.ac.uk>
- CC: "public-prov-wg@w3.org" <public-prov-wg@w3.org>
Hi Jun,
My review focuses on the extension of PROV.
1. I agree that org:originalOrganization is subproperty of prov:used,
org:resultedFrom prov:wasGeneratedBy
org:ChangeEvent is subclass of prov:Activity
we could note that effectively, this makes org:Organization as
subclass of prov:Entity
2. While it is good to extend PROV, taking a PROV perspective, a number
of questions
arise.
if ex:o2 org:resultedFrom ex:a1
ex:a1 org:originalOrganization ex:o1
from a PROV perspective, ex:o1 and ex:o2 may be totally unrelated.
In fact, it would
be PROV-valid, if ex:o2 preceded ex:o1.
That's why in PROV we express derivation relations, such as.
ex:o2 prov:wasDerivedFrom ex:o1
This has some implications, such as that the generation of ex:o2
occurs after the generation of ex:o1.
Given this, it is not clear to me what the intent of vocab-org
regarding this subtyping of prov:used and prov:wasGeneratedBy.
In PROV, ex:o1 can continue its existence before its use. Was it
the intent to? Can ex:o2 and ex:o1
coexist as two separate organizations? Or was it the intent that
ex:o1 no longer existed after that
change event?
PROV has wasInvalidatedBy to mark the end of an entity lifetime.
3. It would be really useful to be able to know that
ex:o2 prov:wasDerivedFrom ex:o1
in the example above (if it was the intent).
If it was not the intent, then discard this comment.
There are a number of possibilities.
1. RECOMMEND that ex:o2 prov:wasDerivedFrom ex:o1 is also asserted.
2. Add a property chain
org:resultedFrom o org:originalOrganization => prov:WasDerivedFrom
Thanks,
Luc
--
Professor Luc Moreau
Electronics and Computer Science tel: +44 23 8059 4487
University of Southampton fax: +44 23 8059 2865
Southampton SO17 1BJ email: l.moreau@ecs.soton.ac.uk
United Kingdom http://www.ecs.soton.ac.uk/~lavm
Received on Wednesday, 21 November 2012 16:16:39 UTC