- From: Provenance Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Wed, 22 Feb 2012 17:21:36 +0000
- To: public-prov-wg@w3.org
PROV-ISSUE-257 (TLebo): rename "Account"/"Bundle"/"AccountEntity" to "Provenance" [prov-dm] http://www.w3.org/2011/prov/track/issues/257 Raised by: Timothy Lebo On product: prov-dm Our latest stab [1] at defining "Account"/"Bundle"/"AccountEntity" is: "An AccountEntity is an entity that contains a bundle of provenance assertions." I propose to name this concept "Provenance": "Provenance is an entity that groups provenance assertions." (or, to avoid using "provenance" in its own definition: "Provenance is an entity that groups assertions about involvements among Entities and Activities.") This has a simplicity, naturalness, and even eloquence. When one says "Let me check the provenance", they are saying "Let me look at the assertions made about some thing". Further, it plainly addresses how one asserts Provenance of Provenance, since Provenance is an Entity. The fact that Provenance is an Entity also resolves many challenges that I've faced with respect to an "Account"'s specialization. Asserters may choose the level of abstraction they wish, which can be reconciled with those that demand different levels of abstraction. For example, are you querying a particular File on a particular machine to get the provenance, or are you looking at the abstract RDF graph that exists in MANY files (and one of which may have changed). Both are handled and can be used, and coherently associated using specialization. This also provides an opportunity to extend Provenance to the original notions of Account (which I say we leave for others to do). For example, :what_I_did_yesterday a prov:Provenance; prov:wasAssociatedWith :TBL . Regards, Tim [1] http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/towards-wd4.html#section-types-entities-agents
Received on Wednesday, 22 February 2012 17:21:45 UTC