14:51:29 trackbot, start telcon 14:51:29 logging to http://www.w3.org/2012/05/24-prov-irc 14:51:31 RRSAgent, make logs world 14:51:31 I have made the request, trackbot 14:51:33 Zakim, this will be 14:51:33 I don't understand 'this will be', trackbot 14:51:34 Meeting: Provenance Working Group Teleconference 14:51:34 Date: 24 May 2012 14:51:38 Zakim, this will be PROV 14:51:38 ok, pgroth; I see SW_(PROV)11:00AM scheduled to start in 9 minutes 14:52:02 Agenda: http://www.w3.org/2011/prov/wiki/Meetings:Telecon2012.05.24 14:52:13 Chair: Paul Groth 14:52:18 Scribe: Curt Tilmes 14:52:25 Regrets: Paolo Missier 14:52:33 rrsagent, make logs public 14:52:33 I have made the request, pgroth 14:53:20 SW_(PROV)11:00AM has now started 14:53:27 +jfuller 14:53:35 Zakim, who is here? 14:53:35 On the phone I see jfuller 14:53:37 On IRC I see TomDN, Zakim, RRSAgent, pgroth, Luc, trackbot, stain, sandro 14:55:00 + +329331aaaa 14:55:13 Zakim, +329331aaaa is me 14:55:13 +TomDN; got it 14:55:33 Zakim, mute me 14:55:34 TomDN should now be muted 14:55:55 Zakim, who is here? 14:55:55 On the phone I see jfuller, TomDN (muted) 14:55:57 On IRC I see TomDN, Zakim, RRSAgent, pgroth, Luc, trackbot, stain, sandro 14:59:06 +Luc 14:59:32 +??P22 15:00:36 + +1.518.276.aabb 15:00:40 +jfuller.a 15:01:00 zakim, who is here? 15:01:00 On the phone I see jfuller, TomDN (muted), Luc, ??P22, +1.518.276.aabb, jfuller.a 15:01:06 zakim, ??P22 is me 15:01:06 On IRC I see jun, SamCoppens, tlebo, Curt, TomDN, Zakim, RRSAgent, pgroth, Luc, trackbot, stain, sandro 15:01:06 zakim, I am aabb 15:01:12 +jun; got it 15:01:15 +tlebo; got it 15:01:41 zakim, SamCoppens is with TomDN 15:01:46 +SamCoppens; got it 15:01:48 +Curt_Tilmes 15:02:04 +??P15 15:02:12 Zakim, ??P15 is me 15:02:14 +dgarijo; got it 15:02:20 hi all 15:02:32 Topic: Admin 15:02:43 +??P17 15:02:48 http://www.w3.org/2011/prov/meeting/2012-05-17 15:03:02 zakim, ??P17 is me 15:03:02 +khalidbelhajjame; got it 15:03:02 proposed: approve Minutes of the May 17 2012 Telecon 15:03:05 +1 15:03:06 +1 15:03:07 +1 15:03:07 +1 15:03:10 +jfuller.aa 15:03:11 +1 15:03:11 +1 15:03:21 +1 15:03:22 0 (did not attend the meeting) 15:03:39 approved: Minutes of the May 17 2012 Telecon 15:03:49 pgroth: 2 open actions 15:04:05 +??P3 15:04:05 ... sandro to send working drafts 15:04:08 sandro? 15:04:42 +??P7 15:04:44 ... graham to review constraints. some emails flowing. 15:04:52 there is an email that just arrived on the mailing list 15:05:08 zakim, ??p7 is me 15:05:08 +GK1; got it 15:05:18 pgroth: scribes, need them, please sign up 15:05:27 Topic: PROV-DM Restructuring 15:05:42 + +44.131.467.aacc 15:05:46 pgroth: past weeks, discussed several options 15:05:56 ... graham made a proposal discussed last week 15:06:04 ... chairs actioned to counter-propose 15:06:09 Sorry I'm late ... re actions, I just took a look at constraints. Basically looking good. Comments in email. 15:06:34 ... many comments going around. Consensus proposal looking good, good approach 15:06:58 ... core vs. extended has support on mailing list, try to confirm that today 15:07:32 http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html 15:07:38 luc: worked on text based on mailling list feedback 15:08:00 ... revised section 2, now an overview with 3 subsections 15:08:15 ... core, extended, organization and components 15:08:39 ... 2.1 now has the diagram 15:09:04 ... some work to go on content, ready for external review/feedback soon 15:09:10 q+ 15:09:13 q? 15:09:16 ack pgroth 15:09:40 My only comment is that it looks good 15:10:07 See figure: http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#prov-core-structures 15:10:21 pgroth: core structures in editors draft, are these what we want? 15:10:23 q? 15:10:28 +q to ask about wasInformedBy 15:10:29 I think it's about right. 15:10:37 +Sandro 15:10:53 tlebo: prov-o also has wasInformedBy as a starting point, propose to add to DM core 15:11:08 q+ 15:11:12 ack tlebo 15:11:12 tlebo, you wanted to ask about wasInformedBy 15:11:17 ack luc 15:11:42 luc: that's the only difference between dm and prov-o now... 15:12:11 +1 to @tlebo 15:12:18 ... a good reason to add wasInformedBy is that it makes sense in the core 15:12:22 I'm OK either way... I can see the case. 15:12:29 Structure looks good; also makes sense for someone who's just read the primer, I think 15:12:35 ... but it isn't really 'primitive' -- it is really a shortcut for other concepts in the core 15:12:40 Isn't the same true of derivation? 15:12:47 so is wasDerivedFrom, technically... 15:13:18 q? 15:13:21 q+ 15:13:22 ... I lean toward not including wasInformedBy in the core, but it is somewhat subjective 15:13:26 ack GK 15:13:41 GK: Could go either way 15:13:48 ... I see Tim's point 15:13:49 not sure that "primitiveness" should be the dominating consideration - the point is to give a conceptual basis to begin the story for any potential adopter. 15:14:22 +1 @GK ! 15:14:24 q+ 15:14:32 GK: Is its primitiveness similar to wasDerivedFrom? 15:14:36 ack Luc 15:14:57 used(a,e1) wasGeneratedBy(e2,a) 15:15:29 used(a2,e) wasGeneratedBy(e,a1) 15:15:39 wasInformedBy(a2,a1) 15:15:42 +q 15:15:50 Perhaps we should point out that this is the "core" of the DM, not the "core" of the constraints document. ("primitiveness" would be more appropriate in dm-constraints) 15:15:55 luc: ^used + wasGeneratedBy implies wasInformedBy 15:16:05 used(a,e1) wasGeneratedBy(e2,a) does not imply wasDrivedFrom(e2,e1) 15:16:18 That's unexpected to me 15:16:36 q? 15:16:43 ... wasInformedBy is a real shortcut, but wasDerivedFrom isn't a shortcut, since you can't make such an implication 15:16:45 (Hunts in spec...) 15:17:13 pgroth: is having it in the core of value? 15:17:14 q+ 15:17:24 Definition currently given at: http://www.w3.org/TR/prov-constraints/#component-1--entities-and-activities 15:17:25 +q to restate that the purpose is to orient potential adopters, not to slip into the semantics among the constructs. 15:17:34 ... people have asked about constructs to show certain relationships 15:17:46 ... having it in the core helps understanding 15:17:59 ack pgroth 15:18:34 activities aren't functions 15:18:54 An activity does not have to use all inputs to produce a given output 15:19:06 GK: notion of influence is captured by derivation, you need an activity to create the new entity 15:19:06 @Khalid: +1 15:19:29 ... if we have got the consumption/generation, we have derivation 15:19:31 Graham, you may be talking about traceability 15:19:38 @Khalid: it may use e1 for a later generation than e2 15:20:31 ... if an activity uses an entity, and generates another, then derivation is happening 15:20:35 ack GK 15:20:53 tlebo: the purpose of 'core' is to orient new adopters 15:21:02 q? 15:21:10 ack tlebo 15:21:10 tlebo, you wanted to restate that the purpose is to orient potential adopters, not to slip into the semantics among the constructs. 15:21:11 @tlebo +1 that's more compelling :) 15:21:14 @GK: Activities have an star time and an end time. That does not imply that all used entities influence all generated entities... 15:21:14 q+ 15:21:16 ... other distinctions are secondary 15:21:33 used(a,e1) wasGeneratedBy(e2,a) does not imply wasDerivedFrom(e2,e1) 15:21:41 used(a,e1,t1) wasGeneratedBy(e2,a,t2) where t2 luc: dgarijo is right, you can't imply derivation in that way 15:22:02 @gklyne, I don't know whether what @Luc said is in the DM or not. But that notion was the part of the reason for the provenance community to have wasDerivedFrom 15:22:14 s/gklyne/GK/ 15:22:45 I see the point Luc makes, but I also agree @tlebos point 15:23:01 q+ 15:23:09 pgroth: Current core contents except for wasInformedBy is ok, is there strong objection to including it? 15:23:25 @GK, yes. I think the discussion was a bit off the original topic:) 15:23:28 if it helps (as Tim suggested), then I think it should go in there.. 15:23:42 luc: we haven't formally defined what is 'core', but it is misleading to consider wasInformedBy on the same level as the others 15:24:03 luc: but it is subjective, and we could include if the groups wants to 15:24:28 luc: I think it should not be there, since it is misleading 15:24:46 @Luc, misleading, but might still be helpful? 15:25:43 proposed: the core consists of entity, activity, agent, wasDerivedFrom, used, wasGeneratedBy, wasAttibutedTo, actedOnBehalf, wasAssociatedWith, wasInformedBy 15:25:48 @jun, of course, i am not suggesting to drop it from the model, it is among the extended structures 15:26:09 +0.5 (happy either way, lean to this, but slightly) 15:26:09 +1 15:26:10 +1 15:26:16 +1 15:26:18 +1 15:26:19 +1 (ambivalent about wasInformedBy) 15:26:23 +1 15:26:31 +0.5 (ambivalent as well) 15:26:34 +0.5 15:26:35 +1 15:26:46 +0.5 (because time was all excluded, but I am fine with it) 15:26:47 +0.5 15:27:23 accepted: the core consists of entity, activity, agent, wasDerivedFrom, used, wasGeneratedBy, wasAttibutedTo, actedOnBehalf, wasAssociatedWith, wasInformedBy 15:27:28 q+ 15:27:34 pgroth: ambivalence plus support, so that seems the way to go 15:28:11 luc: should consider the choice 15:28:12 proposed: the core consists of entity, activity, agent, wasDerivedFrom, used, wasGeneratedBy, wasAttibutedTo, actedOnBehalf, wasAssociatedWith 15:28:17 +0 15:28:19 +1 as well 15:28:22 +1 15:28:27 +0 15:28:30 +1 15:28:31 +0.5 15:28:37 +1 happy either way 15:28:42 +1 15:29:01 q+ to ask if prov-o must remove "startedAtTime" and "endedAtTime" because of this resolution. 15:29:06 -1 15:29:17 ack Luc 15:29:47 q|+ 15:29:51 tlebo: what does this mean for startedAtTime/endedAtTime for its starting point 15:29:51 ack tlebo 15:29:51 tlebo, you wanted to ask if prov-o must remove "startedAtTime" and "endedAtTime" because of this resolution. 15:30:05 pgroth: prov-o should remove those, so core is consistent 15:30:08 I assumed that each document could make it's own evaluation 15:30:18 +0 fine either way 15:30:26 luc: no, prov-dm core doesn't talk about some things like time 15:30:44 @Tim: when you say remove you mean to put it in expanded terms, right? 15:30:49 luc: we could, but I don't think prov-o would have to remove those from its starting point 15:31:01 @dgarijo, yes. Moving them to expanded. 15:31:04 q- 15:31:07 thanks! 15:31:08 @tlebo: ok, thx 15:31:12 pgroth: ok, you could leave them in the starting points 15:31:23 The question is: wasInformedBy core or not? 15:31:40 pgroth: looking at votes, leans to add wasInformedBy to core 15:31:49 @GK: according to the votes it should be included in the core. 15:32:17 proposed: is wasInformedBy including in the core in prov-dm 15:32:32 +0 15:32:35 0 15:32:37 +0 15:32:38 0 15:32:38 I assume +foires for, - votes against? 15:32:41 +0.5 15:32:45 +0.5 15:32:50 +1 15:33:04 0 15:33:21 +0.5 15:33:44 +1 seems useful to cover it for symmetry with derivation even if it is redundant 15:33:45 what does 0.5 mean? Is that support, partial support or that you don't care? 15:33:47 +0 15:33:52 (dropped off audio briefly there) 15:34:24 @dgarijo I use +0.5 to mean I lean towards, but happy either way. 15:34:24 pgroth: fairly positive, ok luc? 15:34:26 luc: that's fine. 15:34:28 means that I wouldn't object if it goes the other way 15:34:28 accepted: wasInformedBy included in the core 15:34:33 @GK: ok, thx! 15:35:02 pgroth: want to confirm other terminology 'core' vs. 'extended', other options? 15:35:23 proposed: Use the term core and extended to categorize the constructs 15:35:27 +1 15:35:28 +1 15:35:29 +1 15:35:29 +1 15:35:34 +1 15:35:35 +1 15:35:40 +1 15:35:45 +1 15:35:46 +1 15:35:47 +1 15:35:54 +1 15:35:57 does it mean that prov-o starting points becomes prov-o core? 15:35:59 +1 (for the DM, right? not in every document) 15:36:11 accepted: Use the term core and extended to categorize the constructs 15:36:39 pgroth: these decisions are on prov-dm, what is the impact on prov-o? 15:36:53 ... prov-o editors? what do you want to do with this? 15:37:23 tlebo: I'm comfortable changing 'starting point' to 'core', but the time concepts are inconsistent with that 15:37:24 q? 15:37:54 q+ in prov-o we also have terms for qualified patterns 15:37:57 +??P12 15:38:19 I propose no immediate impact on PROV-O, unless some one raises an issue. I have no problem with apparent inconsistency, since it doesn't have any technical impact. 15:38:22 jun: we have further categorization for other sections, what about those? 15:38:27 +q 15:38:31 q? 15:39:04 pgroth: It is reasonable for prov-o to keep starting point and mention these are similar to the prov-dm core 15:39:12 q- 15:39:22 ... different terminology might help limit confusion, even if there is less parallelism 15:39:28 q? 15:39:30 q+ 15:39:32 ack pgroth 15:39:32 q+ 15:39:34 ... prov-dm doesn't have the qualified terms 15:39:35 ack Luc 15:39:43 -??P12 15:40:09 luc: in section 2.1 of prov-dm, it just talks about the key classes/types/associations, it doesn't get into the notion of time 15:40:32 ... that comes in much later, 2.1 is just conceptual, doesn't get into syntax 15:40:53 ... it doesn't preclude time being part of the core, shouldn't be a problem with prov-o having that in its starting points 15:41:27 q- 15:41:28 Luc: "examples of syntax don't come until section 4" 15:41:37 q? 15:41:39 ... with regard to the qualified relations, there are association classes later 15:41:54 pgroth: include time in the core points? 15:42:04 +??P5 15:42:25 luc: the representation in dm core doesn't really allow discussion of time, but it isn't really a problem to consider time part of that 15:42:45 q? 15:42:50 WFM 15:42:57 pgroth: Keep that terminology? Core for DM and 'starting points' for prov-o? 15:43:03 I thought that Luc was suggesting that the core in dm and starting points in provo are the same 15:43:10 which I think is the case 15:43:26 @khalid - I think he said they were not incosistent, just that 15:43:35 pgroth: they aren't the same, since time isn't in the dm core 15:43:58 I don't show any attribute in this class diagram 15:44:56 http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#component1 15:44:59 q+ 15:45:16 -??P5 15:45:33 http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#component2 15:46:08 luc: to clarify: activities in figure do show time, but those attributes aren't really discussed in the core 15:46:36 http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-Activity - st and et are mandatory, so I think their appearance (as distinct terms) in PROV-O start is entirely consistent as it can be due to nature of RDF representation. 15:46:46 pgroth: either we align, or we don't, tim is right, we do know what is part of dm core, maybe we can address alignment later 15:46:53 +1 15:46:55 +1 15:46:56 +1 15:46:56 +1 15:47:01 +1 15:47:04 +1 15:47:13 Topic: Name for Responsibility 15:47:17 pgroth: luc can proceed based on this for now 15:47:29 http://www.w3.org/2011/prov/wiki/Renaming_the_concept_Responsibility 15:47:50 tlebo: name for responsibility is ambiguous 15:48:32 ... tlebo too broad, too general, would like to rename to 'delegation' 15:48:51 q? 15:49:00 ack Luc 15:49:01 q+ 15:49:09 ack Luc 15:49:20 luc: confirm you are now happy with 'delegation'? 15:50:31 tlebo: choosing between delegation or OnBehalfOf 15:50:47 q? 15:51:02 q+ 15:51:02 q? 15:51:06 ack Luc 15:51:06 tlebo: I would problem lean toward actedOnBehalfOf, but either that or delegation better than responsibility 15:51:10 Responsibility is the fact that an agent is accountable for the actions of a "subordinate" agent, in the context of an activity. 15:51:16 s/problem/probably/ 15:51:22 + +44.789.470.aadd 15:51:39 @Tim: so, if we choose delegation, would we change "actedOnBehalfOf" to something like delegated? 15:51:49 @luc, it is strange. 15:51:59 luc: behalf sounds strange 15:52:06 GK: yes, it does 15:52:22 luc: it isn't really used on its own like that 15:52:31 pgroth: does it have to be one noun? 15:52:32 luc: yes 15:52:33 "Act" ? 15:52:43 @tlebo, too close to activity 15:52:50 q? 15:52:52 true 15:53:08 q+ 15:53:11 "Action" also too close? 15:53:14 ack Luc 15:53:18 pgroth: delegation does sound good 15:53:27 "actedFor"? 15:53:46 POI: we already have "qualified" v. "unqualifed" naming mismatches, so it's not a show stopper. 15:53:48 luc: delegation has a benefit, and clarifies the presentation in both documents 15:53:55 (wasinformedBy and Communication) 15:54:33 proposed: Use Delegation as the name for what is now Responsibility 15:54:57 +1 unless it means changing actedOnBehalfOf to wasDelegatedTo 15:54:59 +1 (it "stands along" better than "Behalf") 15:55:04 s/along/alone/ 15:55:05 +1 15:55:06 +1 15:55:07 +1 15:55:09 +1 15:55:13 +1 15:55:13 +1 15:55:15 +.999 15:55:18 +1 (it seems clearer) 15:55:19 +1 15:55:22 +1 15:55:40 pgroth: simon -- I don't like 'wasDelegatedTo' either 15:55:48 q+ 15:55:53 smiles: actedOnBehalfOf is better 15:55:56 +1 (Delegation better than Responsibility) 15:56:07 luc: yes, wouldn't want to change it to 'wasDelegatedTo' 15:56:17 Delegation is the fact that an agent is accountable for the actions of a "subordinate" agent, in the context of an activity. 15:56:37 luc: can I simply replace 'responsibility' with 'delegation'? 15:56:41 +q 15:56:46 zakim, unmute me 15:56:46 TomDN should no longer be muted 15:56:47 ack Luc 15:56:52 ack TomDm 15:57:01 ack TomDN 15:57:27 TomDN: keyword subordinate doesn't really work -- you can delegate to a peer 15:57:29 q? 15:57:29 And what is "accountable" now. 15:57:46 Yes, I find it fine just replacing Responsibility with Delegation 15:57:49 "assignment of responsibility" -> "delegation" 15:58:11 q? 15:58:15 pgroth: simple search replace should be ok 15:58:31 I think an editorial pass may be needed. 15:58:32 from wikipedia, slightly longer definition 15:58:34 Delegation (or deputation) is the assignment of authority and responsibility to another person (normally from a manager to a subordinate) to carry out specific activities. However the person who delegated the work remains accountable for the outcome of the delegated work. 15:58:39 I don't disagree, but it is what we define it is 15:58:54 one can look at "senior" with a localized context - even a peer is "senior" if they give a responsibility to a peer (or if a peer "just does it" without the "senior" asking). 15:58:54 http://www.bynkii.com/archives/2004/11/on_authority_and_responsibilit.html 15:58:54 so basically it is up to us, no? 15:59:01 @zednik: I like your text 15:59:06 Scribe please? I could not hear what pgroth said. 15:59:19 accepted: use Delegation as the name for what is now Responsibility 15:59:36 Topic: Reviewers 15:59:53 Sorry, lag on irc.. 15:59:58 - +44.789.470.aadd 16:00:02 pgroth: who is willing to review when they are ready to go? 16:00:02 prov-dm 16:00:06 @luc, @zednick, I think we should also cover the case where an agent "just does it without asking" for another agent. (altruism) 16:00:06 I do 16:00:10 I'll review it as well 16:00:11 I do 16:00:12 +1 16:00:35 reviewers for prov-o 16:00:42 so, just to be sure, the document to review is : http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html ?? 16:00:44 +1 16:00:44 i will 16:01:00 @tlebo, ok, i will circulate definition suggestions 16:01:02 @pgroth: ok, thanks 16:01:12 i will 16:01:13 pgroth: Just picking reviewers to review in 1-2 weeks when documents are ready 16:01:15 +1 16:01:31 prov-constraints 16:01:34 +1 16:01:43 I'll read this one too 16:01:52 prov-n 16:02:08 +1 16:02:14 +1 16:02:17 +1 16:02:45 -khalidbelhajjame 16:02:45 bye! 16:02:47 -tlebo 16:02:47 -Sandro 16:02:48 -TomDN 16:02:48 - +44.131.467.aacc 16:02:48 bye 16:02:50 -jfuller.aa 16:02:51 -dgarijo 16:02:56 @gk 16:02:58 -Curt_Tilmes 16:02:59 rrsagent, set log public 16:02:59 I have made the request, pgroth 16:03:01 -??P3 16:03:04 rrsagent, draft minutes 16:03:04 I have made the request to generate http://www.w3.org/2012/05/24-prov-minutes.html pgroth 16:03:11 trackbot, end telcon 16:03:11 Zakim, list attendees 16:03:11 As of this point the attendees have been jfuller, TomDN, Luc, +1.518.276.aabb, jun, tlebo, SamCoppens, Curt_Tilmes, dgarijo, khalidbelhajjame, GK1, +44.131.467.aacc, Sandro, 16:03:14 ... +44.789.470.aadd 16:03:15 -jfuller 16:03:16 -Luc 16:03:19 RRSAgent, please draft minutes 16:03:19 I have made the request to generate http://www.w3.org/2012/05/24-prov-minutes.html trackbot 16:03:20 RRSAgent, bye 16:03:21 -jfuller.a 16:03:22 I see no action items 16:03:39 -jun 16:04:27 -GK1 16:04:28 SW_(PROV)11:00AM has ended 16:04:28 Attendees were jfuller, TomDN, Luc, +1.518.276.aabb, jun, tlebo, SamCoppens, Curt_Tilmes, dgarijo, khalidbelhajjame, GK1, +44.131.467.aacc, Sandro, +44.789.470.aadd