14:56:31 RRSAgent has joined #prov 14:56:31 logging to http://www.w3.org/2012/10/04-prov-irc 14:56:33 RRSAgent, make logs world 14:56:33 Zakim has joined #prov 14:56:35 Zakim, this will be 14:56:36 Meeting: Provenance Working Group Teleconference 14:56:36 Date: 04 October 2012 14:56:36 I don't understand 'this will be', trackbot 14:56:43 Zakim, this will be PROV 14:56:43 ok, pgroth; I see SW_(PROV)11:00AM scheduled to start in 4 minutes 14:56:55 Agenda: http://www.w3.org/2011/prov/wiki/Meetings:Telecon2012.10.03 14:57:02 Chair: Paul Groth 14:57:08 Scribe: Paolo Missier 14:57:14 Regrets: Tom De Nies 14:57:21 rrsagent, make logs public 14:57:33 SW_(PROV)11:00AM has now started 14:57:40 + +1.818.415.aaaa 14:57:51 Luc has joined #prov 14:57:59 zakim, code? 14:57:59 the conference code is 7768 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), ivan 14:58:12 +[IPcaller] 14:58:15 Paolo has joined #prov 14:58:26 +ivan 14:58:49 Dong has joined #prov 14:59:03 +??P11 14:59:40 Curt has joined #prov 14:59:41 zakim, ??P11 is me 14:59:44 +Paolo; got it 14:59:46 +??P56 15:00:01 zakim, +??P56 is me 15:00:01 sorry, Luc, I do not recognize a party named '+??P56' 15:00:06 zakim, ??P56 is me 15:00:06 +Luc; got it 15:00:09 Topic: Admin 15:00:13 +Curt_Tilmes 15:00:13 zakim, +1.818.415.aaaa is me 15:00:14 +CraigTrim; got it 15:00:15 tlebo has joined #prov 15:00:51 http://www.w3.org/2011/prov/meeting/2012-09-27 15:00:58 Minutes of the September 27, 2012 Telecon 15:01:01 +1 15:01:08 +1 15:01:14 +1 15:01:16 +1 15:01:21 zakim, who is on the phone? 15:01:21 +tlebo 15:01:24 +Luc.a 15:01:25 On the phone I see CraigTrim, [IPcaller], ivan, Paolo, Luc, Curt_Tilmes, tlebo, Luc.a 15:01:27 +??P2 15:01:35 jcheney has joined #prov 15:01:35 christine has joined #prov 15:01:47 accepted: Minutes of the September 27, 2012 Telecon 15:02:03 zakim, ??P2 is me 15:02:22 pgroth: what to do about long-lasting open actions 15:02:29 +Dong; got it 15:02:43 +stain 15:02:46 +jcheney 15:03:01 ivan: it's ok to time out on them and close them, noting that no reply was received 15:03:45 https://dvcs.w3.org/hg/prov/raw-file/dedddeedd578/presentations/wg-overview/overview/index.html 15:03:53 hook has joined #prov 15:04:20 pgroth: finally completed his action, see link above 15:04:54 action 118 (?) also taken care of 15:04:54 Sorry, couldn't find 118. You can review and register nicknames at . 15:05:27 action-113 done (issue 446) 15:05:37 action-116 still ongoing 15:05:45 q? 15:06:08 Topic: PROV Exit Criteria 15:06:21 TOPIC: PROV Exit Criteria 15:06:39 http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria 15:06:57 pgroth: exit criteria were discussed at the latest F2F meeting 15:07:27 http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html 15:07:47 + +1.818.393.aabb 15:07:48 exit criteria are here: http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria 15:08:38 q? 15:08:42 q+ 15:08:47 pgroth: these criteria apply to the DM and ontology 15:08:47 ack ivan 15:09:07 ivan: what is an "implementation" in this context 15:09:08 hook has joined #prov 15:09:22 -Luc 15:09:37 pgroth: using PROV in a dataset, e.g. markung up a web page 15:09:51 pgroth: a vocabulayr for ontologies that extend prov 15:10:14 pgroth: SW that generates and consumes PROV models 15:10:47 ivan: fine, suggest adding this phrasing to the wiki page containing the exit criteria 15:10:59 stainN7 has joined #prov 15:11:11 @Paul: Sure 15:11:17 q? 15:11:17 ivan: also, when implementations are collected, tag them according to the category where they belong 15:11:29 pgroth: are people happy with those 3 categories? 15:11:33 q? 15:12:27 pgroth: these work for DM and O primarily. What would the criteria look like for CONSTRAINTS? 15:13:05 pgroth: need to demonstrate interoperability. 15:14:07 pgroth: proposed criteria: multiple implementations, and show that they support each of the constraints defined in the doc. This is done through a catalog of reference test cases that the implementation must be able to pass 15:14:28 q+ 15:14:36 ack jcheney 15:14:45 +[IPcaller.a] 15:14:49 pgroth: the implementation must correctly evaluate the test case against the constraints it is meant to exercise 15:15:01 zakim, [IPcaller.a] is me 15:15:01 +Luc; got it 15:15:47 stainNexus7 has joined #prov 15:15:48 jcheney: clarification: the criteria include the constraints but exclude the inferences 15:16:07 pgroth: yes, but you probably need to do inferences as well as part of the implementation 15:16:11 Who would build those test cases? The wg? 15:16:46 q+ 15:16:52 ack ivan 15:16:57 jcheney: are the test cases based on 'validity' which requires inferencing? or is inferencing one possible way to do the implementation 15:17:21 so perhaps the test cases should try to *exercise* the inferences 15:17:44 +q 15:17:48 ivan: the constr doc contains inference rules, not just constraints. So are there inferences that will not be tested by the test cases? 15:18:54 jcheney: inferences are a mechanism to define validity, however in the doc we specify that other mechanisms to check validity are fine as well 15:19:31 ivan: that's fine then 15:20:14 Luc: to confirm what jcheney wrote above -- but the test case won't check that inferences have been applied 15:20:41 ack Luc 15:21:02 q+ 15:21:43 dgarijo has joined #prov 15:22:10 hook: interoperability should show that producers and consumers of provenance actually can use the spec to exchange prov 15:22:12 +??P28 15:22:22 Zakim, ??P28 is me 15:22:22 +dgarijo; got it 15:22:30 hook: the current interpretation of interop does not address that 15:23:04 pgroth: true for CONSTR, however prov DM and prov O do require demonstration of interop according to the exit criteria 15:23:05 q+ 15:23:27 ack hook 15:24:12 Luc: are we try to gain evidence for each prov-* individually, or collectively as a whole? 15:24:33 Luc: for example, what does it mean for DM to interop "on its own"? 15:25:06 pgroth: for DM, you do have to go through prov-N or prov-O. the impl. should specify which encoding it supports 15:25:14 pgroth: incl. XML 15:25:19 +??P1 15:25:23 stainNexus7 has joined #prov 15:25:25 ack Luc 15:27:04 ivan: do we really need an implementation for prov-n which is meant for human consumption? it's not meant to be a machine-exchangeable format 15:27:28 Luc: indeed machine processing initially not the primary goal 15:27:47 @Luc, when you mentioned evidence, did you mean that we need to gather proofs beyond submitted answers to the implementation questionnaire? 15:28:16 q+ 15:28:20 pgroth: this is good feedback to produce the next version of the exit criteria. we need to be more specific 15:28:22 ack ivan 15:28:23 http://www.w3.org/2007/OWL/wiki/CR_Exit_Criteria 15:28:33 @dong, submitted answers is what I think we have agreed 15:28:53 - +1.818.393.aabb 15:28:58 @luc, thanks, that's good. 15:29:03 + +1.818.731.aacc 15:29:25 was the functional syntax document a rec? 15:29:27 ivan: the EC for OWL2 is relevant because it's got an analog in a functional syntax, which is not even mentioned in the EC 15:29:36 stephenc has joined #prov 15:29:40 - +1.818.731.aacc 15:29:54 ivan: because the functional syntax can be mapped to one of the serializations 15:30:23 http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/ 15:31:04 ivan: the doc above is analogous to prov-n in our case 15:31:43 +q 15:31:47 ivan: so the EC should really apply to prov-o and prov-constr 15:31:58 ack Luc 15:32:01 + +1.818.731.aadd 15:32:26 - +1.818.731.aadd 15:32:26 Luc: should different implementations come from different institutions? 15:32:56 ivan: if EC call for two impl, then yes they should come from different institutions 15:33:13 q? 15:33:16 q+ 15:33:19 pgroth: plan to vote on EC next week 15:33:44 action: pgroth to revise exit criteria for next week 15:33:44 Created ACTION-119 - Revise exit criteria for next week [on Paul Groth - due 2012-10-11]. 15:34:54 ack Luc 15:34:56 ivan: EC should be fully completed by the time we leave CR, not when we enter CR 15:35:23 and how do we add an application to the implementation catalog? 15:35:29 pgroth: need volunteers to build test cases for the constraints 15:35:47 we can already collect all examples from our specs 15:35:55 me 15:36:05 I think Jun was interested as well 15:36:29 dong? 15:36:40 Sorry, I missed it 15:36:42 Paolo: I can help but can't commit time at this point 15:36:44 I don't see her here, so I'll contact her to see if she's interested. 15:37:12 me 15:37:18 me with Dong 15:37:25 Yes 15:37:32 q+ 15:37:40 ack Luc 15:37:42 after I see a test case or two, I'll reconsider adding some. 15:38:20 q+ 15:38:23 Luc: once they are defined, they should be validated "by expert hand" 15:38:24 ack ivan 15:39:09 @Paul, I've understood that it's a part of the work I'm involved in preparing the implementation report 15:39:10 ivan: need a dynamics in place to manage the responses. What is the reporting mechanism? 15:39:21 pgroth: we basically believe them 15:39:25 believe and document their assertion 15:39:29 q+ 15:39:58 ack Luc 15:40:04 ivan: this means that responses will be managed manually, which may be problematic to scale 15:40:45 Luc: have 100-200 tests at the moment, we should have a simple mechanism with an ID per test... 15:41:17 ivan: a basic mechanism should be defined, we must specify how implementors are expected to report back 15:41:28 q? 15:41:42 Topic: PROV-DM Issues 15:43:23 -stain 15:43:43 hook has joined #prov 15:43:50 pgroth: going through the list.... 15:44:14 + +1.818.393.aaee 15:44:49 pgroth: 520 left till next time as there was discussion 15:45:10 GK has joined #prov 15:45:18 jun has joined #prov 15:45:40 pgroth: (isolating the issues that received feedback and discussion) 15:47:32 ISSUE-531, ISSUE-528, ISSUE-517, ISSUE-501, ISSUE-516, ISSUE-514, ISSUE-513, ISSUE-511, ISSUE-510, ISSUE-512, ISSUE-497, ISSUE-515, 15:47:47 q? 15:47:52 pgroth: the issues above have reached resolution 15:48:22 proposed: ISSUE-531, ISSUE-528, ISSUE-517, ISSUE-501, ISSUE-516, ISSUE-514, ISSUE-513, ISSUE-511, ISSUE-510, ISSUE-512, ISSUE-497, ISSUE-515 are confirmed to be resolved 15:48:45 +1 15:48:48 +1 15:48:50 +1 15:48:57 +1 15:49:03 +1 15:49:04 +1 15:49:10 accepted: ISSUE-531, ISSUE-528, ISSUE-517, ISSUE-501, ISSUE-516, ISSUE-514, ISSUE-513, ISSUE-511, ISSUE-510, ISSUE-512, ISSUE-497, ISSUE-515 are confirmed to be resolved 15:49:19 khalidBelhajjame has joined #prov 15:50:16 Topic: UML and Naming 15:50:40 issue-509? 15:50:40 ISSUE-509 -- Data Model Figure 5 -- open 15:50:40 http://www.w3.org/2011/prov/track/issues/509 15:50:43 pgroth: see issue-509 15:50:55 +??P4 15:51:10 q+ 15:51:15 ack Luc 15:52:04 Luc: earlier versions of the docs show capitalized classes, and relationships not capitalized. that led to inconsistencies 15:52:06 Luc 15:52:33 Luc: we addressed by cap "class level" elements and nocap for "instance level" elements 15:52:56 Luc: diff. notations use different styles. in prov-n nothing is cap 15:53:18 Luc: so we will be inconsistent anyway whatever change we make 15:54:35 Luc: in prov-o class derivations are cap, for instance. There is no solution that works for all of them 15:54:44 q? 15:54:46 q+ 15:54:47 Luc: we tried to make prov-dm consistent with itself 15:55:06 ack ivan 15:55:25 ivan: as the one reopening the issue: looking at the primer on its own. because of its role, felt that consistency was important 15:56:00 ivan: the primer has dual syntax for examples. in prov-n there is no cap, while turtle is also consistent with prov-o 15:56:44 ivan: but fig. after sec 2 uses an inconsistent cap mode, and that is not explained. so proposed to make it consistent with prov-o 15:56:51 q+ 15:56:56 ack Luc 15:57:09 ivan: so just asking to make the figure consistent with one syntax in the text. 15:57:19 Luc: the figure uses the prov-dm convention 15:57:41 Luc: it's a class diagram, not an instance. 15:58:04 q+ 15:58:15 q+ 15:59:07 ack ivan 15:59:22 ivan: the figures in the primer may differ from those in the DM. because it's the primer, readers won't appreciate the alignment with prov, 15:59:40 ivan: rather they will be confused by the change in cap style 16:00:03 +1 to what paul suggested. 16:00:20 pgroth: we should be using the diagram in prov-o instead, it's not UML but it's "classes and properties" and may work better here 16:00:32 ivan: happy with that 16:00:39 http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/diagrams/starting-points.svg 16:01:15 q? 16:01:17 ack pgroth 16:01:31 sounds good 16:01:48 accepted: use a modified version of the prov-o starting points figure in the primer 16:04:32 q? 16:05:19 bye! Thanks, Paul. 16:05:22 -tlebo 16:05:24 -dgarijo 16:05:26 -jcheney 16:05:27 -ivan 16:05:28 -Luc 16:05:29 thanks, bye all 16:05:30 -Dong 16:05:33 bye 16:05:34 -[IPcaller] 16:05:35 -Paolo 16:05:40 - +1.818.393.aaee 16:05:41 -Luc.a 16:05:41 -??P1 16:05:43 -Curt_Tilmes 16:05:49 -??P4 16:06:06 rrsagent, set log public 16:06:09 rrsagent, draft minutes 16:06:09 I have made the request to generate http://www.w3.org/2012/10/04-prov-minutes.html pgroth 16:06:14 trackbot, end telcon 16:06:14 Zakim, list attendees 16:06:14 As of this point the attendees have been [IPcaller], ivan, Paolo, Luc, Curt_Tilmes, CraigTrim, tlebo, Dong, stain, jcheney, +1.818.393.aabb, dgarijo, +1.818.731.aacc, 16:06:18 ... +1.818.731.aadd, +1.818.393.aaee 16:06:22 RRSAgent, please draft minutes 16:06:22 I have made the request to generate http://www.w3.org/2012/10/04-prov-minutes.html trackbot 16:06:23 RRSAgent, bye 16:06:23 I see 1 open action item saved in http://www.w3.org/2012/10/04-prov-actions.rdf : 16:06:23 ACTION: pgroth to revise exit criteria for next week [1] 16:06:23 recorded in http://www.w3.org/2012/10/04-prov-irc#T15-33-44