- From: Stephan Zednik <zednis@rpi.edu>
- Date: Tue, 17 Jan 2012 10:59:29 -0700
- To: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Cc: public-prov-wg@w3.org
Sounds good to me. I have reviewed the modifications to the PROV-DM and agree with closing the issue (which I have done). --Stephan On Jan 17, 2012, at 3:19 AM, Luc Moreau wrote: > Hi Stephan, > > I have made some minor edits to reflect your comment. > See http://dvcs.w3.org/hg/prov/rev/312911932910 > > I am proposing to close this issue, pending review. > Regards, > Luc > > On 01/16/2012 09:35 PM, Stephan Zednik wrote: >> On Jan 16, 2012, at 2:27 PM, Luc Moreau wrote: >> >> >>> Hi Stephan, >>> >>> The inference rule >>> http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#traceability-inference >>> does not propagate attributes. >>> >>> I think it would be difficult to do this in a general way, since the meaning of attributes >>> is application specific. >>> >> Also record specific. >> >> >>> Do you have some use case requiring inference of attributes? >>> >> Not at all. >> >> I just wanted to be precise on what transivity of a 'record' implied. Somehow, I missed the inference section... I see it now. Thanks. >> >> --Stephan >> >> >>> Luc >>> >>> On 16/01/12 18:02, Provenance Working Group Issue Tracker wrote: >>> >>>> PROV-ISSUE-218: Clarification on the transitivity of Traceability Record [prov-dm] >>>> >>>> http://www.w3.org/2011/prov/track/issues/218 >>>> >>>> Raised by: Stephan Zednik >>>> On product: prov-dm >>>> >>>> I would just like to get clarification on the transitivity of the Traceability Record. >>>> >>>> 1) I am assuming that tracedTo attributes are NOT transitive. >>>> >>>> 2) Can these attributes be inferred in any way? >>>> >>>> http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#record-traceability >>>> >>>> 6.1 Traceability Record >>>> >>>> It is common that we may want to know who or what may have some influence, whether direct or indirect, on a given entity, or who may, directly or not, have some responsibility for a given outcome. Hence, we may want to infer such a notion from an existing set of PROV-DM records. Vice-versa, we may have knowledge of this influence and responsibility, but without knowing its actual details. Thus, we may also want to assert such a notion. >>>> >>>> A traceability record states the existence of a "dependency path" between two entities, indicating that one entity can be shown to be in the lineage of another, and may have influenced it, or may bear some responsibility for it, in some way. A traceability record subsumes derivation, activity association, and responsibility, and is defined to be transitive. >>>> >>>> A traceability record, written tracedTo(id,e2,e1,attrs) in PROV-ASN: >>>> >>>> id: an optional identifier id identifying the traceability record; >>>> entity: an identifier e2 identifying an entity; >>>> ancestor: an identifier e1 identifying an ancestor entity in the lineage of e2; >>>> attributes: an optional set attrs of attribute-value pairs to further describe this record. >>>> In PROV-ASN, a traceability record's text matches the traceabilityRecord production of the grammar defined in this specification document. >>>> >>>> traceabilityRecord ::= tracedTo ( identifier , eIdentifier , eIdentifier optional-attribute-values ) >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> > > -- > 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 Tuesday, 17 January 2012 18:00:25 UTC