- From: Curt Tilmes <Curt.Tilmes@nasa.gov>
- Date: Thu, 19 Apr 2012 10:35:33 -0400
- To: <public-prov-wg@w3.org>
On 04/12/2012 05:06 PM, Luc Moreau wrote: > Hi Jun and Satya, > > Following today's call, ACTION-76 [1] and ACTION-77 [2] were raised > against you, as we agreed. > > [1] https://www.w3.org/2011/prov/track/actions/76 > [2] https://www.w3.org/2011/prov/track/actions/77 I've been going over the "collections" traffic. I mentioned this briefly on the call last week, but I'll state it once more for the record, then keep my peace. The bulk of PROV-DM is describing what I'll call core or fundamental concepts for describing provenance. You have a general 'entity', it gets 'used' by an 'activity' and 'generates' a new 'entity'. Those concepts are all necessary to the data model, and it doesn't hold together without them. Collections, IMHO, don't fall into that category. They should be a layer on top of the DM, not a set of fundamental concepts beside the others or integrated with them. A collection is simply another type of entity, it changes in several ways, the previous instance of it getting used by various activities, resulting in the generation of a new entity. We should model that just like any other entity that gets changed in any number of ways. Insertion/Removal are just like any other activities. They use one entity (the previous collection), make some changes, and generate a new entity (the next version of the collection). They aren't 'special' enough to include in PROV-DM. One could argue (several of you have) that collections are very important, since they cross so many domains. I could buy that, but there are also many different types of collections (touched on by the discussion) and the types of representations and changes that happen to the collections, and importance of various aspects of provenance of those changes are different for each of them. Take what we have here, make it a Collection Provenance Model or something like that, and propose it separately as a middle layer on top of PROV, below all the "Provenance of XXX"s that will be needed for various domains, but leave it out of PROV-DM. My 2 cents, Curt
Received on Thursday, 19 April 2012 14:36:18 UTC