14:24:31 RRSAgent has joined #prov 14:24:31 logging to http://www.w3.org/2012/09/13-prov-irc 14:24:33 RRSAgent, make logs world 14:24:33 Zakim has joined #prov 14:24:35 Zakim, this will be 14:24:35 I don't understand 'this will be', trackbot 14:24:36 Meeting: Provenance Working Group Teleconference 14:24:36 Date: 13 September 2012 14:24:52 zakim, this will be prov 14:24:52 ok, ivan; I see SW_(PROV)11:00AM scheduled to start in 36 minutes 14:55:19 Luc has joined #prov 14:55:41 satya has joined #prov 14:57:49 SW_(PROV)11:00AM has now started 14:57:56 +Satya_Sahoo 14:58:14 pgroth has joined #prov 14:58:25 +Luc 14:59:00 +??P2 14:59:07 trackbot, start telcon 14:59:09 RRSAgent, make logs world 14:59:11 Zakim, this will be 14:59:11 I don't understand 'this will be', trackbot 14:59:12 Meeting: Provenance Working Group Teleconference 14:59:12 Date: 13 September 2012 14:59:15 Zakim, this will be PROV 14:59:15 ok, pgroth, I see SW_(PROV)11:00AM already started 14:59:16 + +1.315.330.aaaa 14:59:20 Chair: Paul Groth 14:59:25 Scribe: Satya Sahoo 14:59:36 zakim, dial ivan-voip 14:59:36 ok, ivan; the call is being made 14:59:37 +Ivan 14:59:44 Regrets: Simon Miles, James Cheney, Curt Tilmes, Khalid Belhajjame, Graham Klyne 14:59:51 rrsagent, make logs public 15:00:42 Topic: Admin 15:01:04 hook has joined #prov 15:01:32 http://www.w3.org/2011/prov/meeting/2012-09-06 15:01:37 Paul: Agenda items: updates on F2F, PROV-O admin issues, outstanding issues, and implementation reports 15:01:39 Minutes of the September 6, 2012 Telecon 15:01:52 +1 15:01:58 +1 15:02:08 + +1.818.731.aabb 15:02:27 Dong_ has joined #prov 15:02:51 jun has joined #prov 15:02:51 approved: Minutes of the September 6, 2012 Telecon 15:03:04 +[IPcaller] 15:03:10 zednik has joined #prov 15:03:16 zakim, IPcaller is me 15:03:16 CraigTrim has joined #PROV 15:03:22 +jun; got it 15:03:27 Paul: Open action on Paulo, Paul still open 15:04:11 Paul: Action item regarding XML schema definition 15:04:13 +??P8 15:04:23 Hook: Completed the XSD 15:04:29 Paul: Action item on Hook closed 15:04:52 Topic: F2F4 15:04:52 Paul: Please sign up for scribe 15:04:58 http://www.w3.org/2011/prov/wiki/F2F4 15:05:04 Paul: Next agenda item regarding 4th F2F 15:05:20 +??P5 15:05:21 Paul: Please sign for the F2F either remotely or in person 15:05:28 q? 15:05:30 stephenc has joined #prov 15:05:34 +OpenLink_Software 15:05:35 Paul: Question regarding F2F? 15:05:38 Topic: Prov-o telcon 15:05:43 +Luc.a 15:05:51 Zakim, OpenLink_Software is temporarily me 15:05:54 +MacTed; got it 15:05:56 Zakim, mute me 15:06:01 MacTed should now be muted 15:06:16 Paul: PROV-O telcon was important for development of the ontology, currently responding to the comments 15:06:29 q? 15:06:44 q? 15:06:45 q+ to suggest prov-xml team could use the prov-o slot 15:06:46 Paul: Discussed with prov-o team to roll in the prov-o discussion items into the regular PROV call 15:06:50 ack Luc 15:06:50 Luc, you wanted to suggest prov-xml team could use the prov-o slot 15:07:17 +TomDN 15:07:19 Luc: PROV-XML team may want to use the PROV-O time slot on Monday for discussion 15:07:22 q+ 15:07:23 q? 15:07:23 TomDN has joined #prov 15:07:29 ack zednik 15:07:43 SamCoppens has joined #prov 15:07:44 Stephan: Agree if rest of the PROV-XML team agrees 15:07:51 Zakim, who is on the phone? 15:07:51 On the phone I see Satya_Sahoo, Luc, ??P2, +1.315.330.aaaa, Ivan, +1.818.731.aabb, jun, ??P8, ??P5, MacTed (muted), Luc.a, TomDN 15:07:57 sounds good 15:08:05 Zakim, Samcoppens is with TomDN 15:08:05 +Samcoppens; got it 15:08:11 q? 15:08:23 Paul: PROV-XML will use the monday timeslot for meetings 15:08:26 Topic: PROV-Constraints Dissemination 15:08:27 Zakim, mute me 15:08:27 TomDN should now be muted 15:08:35 http://www.w3.org/TR/prov-constraints/ 15:08:40 Paul: Next agenda item: PROV constraints dissemination 15:08:57 Paul: Congrats to the editors of PROV constraints! 15:09:19 http://www.w3.org/blog/SW/2012/09/12/last-call-constraints-of-the-provenance-data-model-2/ 15:09:37 Paul: Paolo, Luc created a blog post describing the PROV constraints 15:09:48 Paul: Please share the blog with others 15:10:05 Paul: Can someone volunteer to share this with various maling lists 15:10:26 maling/mailing 15:10:30 ivan to semweb list 15:10:53 satya to hclrs 15:11:23 Paul: Luc can share with provenance challenge 15:11:23 luc provenance challenge mailing list 15:11:46 Paul: James to share with Dagstuhl mailing list 15:11:46 james cheney to mailing list 15:11:48 q? 15:12:21 Topic: Resolving Issues 15:12:57 Zakim, who's noisy? 15:12:57 Paul: Issues raised for PROV-DM (primarily from Robert@Mayo clinic) 15:13:02 Zakim, who's noisy 15:13:02 I don't understand 'who's noisy', pgroth 15:13:10 MacTed, listening for 10 seconds I heard sound from the following: Luc (69%), ??P2 (9%), Ivan (9%) 15:13:11 zakim, who is noisy? 15:13:17 zakim, mute me 15:13:17 Ivan should now be muted 15:13:27 pgroth, listening for 10 seconds I could not identify any sounds 15:13:29 Luc: Reviewed the feedback for comments that require changes to the data model 15:13:41 Luc: Drafted responses to these specific issues 15:14:00 Luc: ISSUE 532 regarding roles, to allow roles for more relations 15:14:17 http://lists.w3.org/Archives/Public/public-prov-wg/2012Sep/0141.html 15:14:31 Luc: WG decided against this as there was no satisfactory resolution 15:15:19 Paolo has joined #prov 15:15:24 Luc: Protocol to follow to resolve these issues - vote or put it up for discussion on a wiki page 15:15:53 yes 15:15:58 Paul: If there are no objections raised by a particular date, then confirm with the person who raised the issue 15:16:14 zakim, unmute me 15:16:14 Ivan should no longer be muted 15:17:22 Ivan: It is good to have a confirmation to the proposed solution, but it may not be always possible 15:17:43 +??P10 15:18:40 Dong has joined #prov 15:18:57 q? 15:19:15 Paul: Let the WG consider the response by Monday and then get back to the person raising the issue 15:19:28 Luc: Where should the response be posted? 15:19:37 Ivan: In the tracker 15:20:24 Ivan: The response should include links to the person's confirmation 15:20:49 Luc: ISSUE 525: Specialization and Alternate to be subtype of Influence 15:21:15 Luc: WG resolution on this issue 15:21:29 note, working group members should respond to these suggestions by monday 15:21:37 q? 15:21:40 q+ 15:21:45 Luc: Questions/comments on ISSUE 525 15:22:31 Luc: Include attributes for these relations, create patterns similar to the relations 15:22:50 Luc: There was decision against this approach 15:22:50 ack pgroth 15:23:07 Paul: Should include this discussion in the response 15:23:49 Paul: Add a section to the wiki page for the issue to include updates 15:23:56 ivan? 15:24:42 Luc: ISSUE 507: wasAssociatedWith in DM, PROV-O includes this property and also an inverse relation - to include the inverse relation in DM 15:25:03 q+ 15:25:29 ack ivan 15:25:31 Luc: In relational design, we do not include inverse relations. PROV-O includes inverse relations due to OWL/RDF 15:25:37 dgarijo has joined #prov 15:25:47 q+ 15:25:55 Zakim, unmute me 15:25:55 MacTed should no longer be muted 15:26:03 Ivan: Understands Luc's point, Is it necessary to have an inverse relation? 15:26:08 +??P15 15:26:15 Zakim, ??P15 is me 15:26:15 +dgarijo; got it 15:26:22 q+ 15:26:37 Ivan: It is usual to have this pattern in an ontology, but it may lead to complexity 15:26:42 ack MacTed 15:27:06 Mac: The notion of what is a relation and what is its inverse is arbitrary 15:27:07 ack zednik 15:27:16 Mac: So, both should be there 15:28:04 Stephen: There was a lot of discussion in PROV-O regarding this, it is currently a suggestion for the inverse properties (to ensure consistent naming) 15:28:19 Stephen: The inverse is not always explicitly specified 15:28:44 Ivan: Not sure what does it mean - are they part of the OWL file? 15:29:02 Tim: They are not, the inverse are in a separate OWL file 15:29:32 Ivan: Not convinced, not having them at all is a better solution 15:30:10 Tim: PROV-O tried to reach a compromise and the current solution is after long discussion 15:30:49 Luc: PROV-O does not include inverse relation, hence it is normative - so PROV-O and DM are aligned 15:30:56 Luc: Will rephrase the answer 15:30:58 q? 15:31:04 http://www.w3.org/2011/prov/track/issues/504 15:31:12 issue-504? 15:31:12 ISSUE-504 -- Data Model Section 2.2.2 -- open 15:31:12 http://www.w3.org/2011/prov/track/issues/504 15:31:20 Luc: ISSUE-504, regarding bundles and collections 15:32:48 Luc: WG has discussed this issue on multiple points - WG resolved not to have identifiers on provenance assertions, bundles allow assertion of identifiers and make statements about bundles 15:33:11 q? 15:33:12 Luc: WG considers this as a good compromise 15:33:44 Paul: Include a change in definition of collections? 15:34:33 http://www.w3.org/2011/prov/track/issues/503 15:34:55 Luc: ISSUE 503: regarding agents that adopt a plan 15:35:35 Luc: wasAdoptedBy should be a new definition in PROV to allow plan to be assigned to agent without use of activity 15:35:42 zakim, mute me 15:35:42 Ivan should now be muted 15:36:05 Luc: Responded to Paul separately, not sure what is to be done here 15:36:22 q? 15:36:32 +q 15:36:41 ack dgarijo 15:37:03 Daniel: Does he have a use case that would justify the introduction of this new relation? 15:37:15 Luc: Not to my knowledge 15:37:23 Zakim, mute me 15:37:23 MacTed should now be muted 15:37:37 Daniel: We have enough relations to cover this use, so would not vote to have a new relation 15:37:57 that makes sense 15:38:06 Paul: Is this relation an easy extension to existing PROV model? 15:38:40 Tim: Would it be a property chain or qualified association based rule? 15:39:04 Paul: This suggestion can be included in the response 15:40:16 Luc: Will edit the wiki page tomorrow and send mail - give time till Tuesday 15:40:35 Paul: Any objections to have responses to this discussion by Tuesday? 15:41:03 accepted: to have responses to the issues in the agenda by tuesday 15:41:20 q? 15:41:57 Topic: Subactivity 15:41:58 Paul: Next agenda item is discussion about subactivity 15:42:05 http://www.w3.org/2011/prov/track/issues/447 15:42:32 Paul: ISSUE 447, several request to introduce a sub activity relation in the model followed by mailing list discussion 15:43:38 Paul: It may be a good idea according to some members, but others have reservations that introduction of the new relation will have repurcussions across model and constrains (some of which may have not be considered at all) 15:43:57 Paul: One proposed option is use dc partOf relation 15:44:19 constrains/constraints 15:44:24 q? 15:44:24 q? 15:44:32 I think we should go for dcterms:hasPart. 15:44:35 Paul: Whether to include or leave out this? 15:44:41 q+ 15:44:41 q+ 15:44:44 @Daniel +1 15:45:22 I expressed my view on the list -- I'd rather leave it out of the model 15:45:34 ack zednik 15:45:35 Stephan: Can this be included in the best practices document? But not include this in specs 15:45:41 ack Luc 15:46:08 Luc: Daniel please clarify proposed use of dcterms:hasPart 15:46:20 +q 15:47:12 Daniel: Keen to have it in a document, but not in ontology - is there a proposal for a best practices document as it would allow inclusion of some issues currently pending in PROV-O also 15:47:52 http://dvcs.w3.org/hg/prov/raw-file/tip/bestpractices/BestPractices.html 15:47:52 @zednik: should it be an FAQ? 15:47:59 Stephan: (answering to Luc) Last F2F discussed creation of best practices document - it will be a note and not a spec 15:48:18 Stephan: It will be a kind of FAQ, maybe part of FAQ 15:48:30 +1 "this is a common need; here's how best to satisfy it with what we've done" 15:49:17 proposed: subactivity relation will not be included in normative documents, but instead would be described in light weight document, such as FAQ/best practice 15:49:19 Paul: We have identified the DC document as a best practice document, strongly support a FAQ document 15:49:57 Paul: FAQ will sidestep the complications associated with a spec, so this FAQ can also be updated 15:50:00 proposed: subactivity relation will not be included in normative documents, but instead would be described in light weight document, such as FAQ/best practice 15:50:12 +1 15:50:24 +1 15:50:29 +1 15:50:31 +1 15:50:32 +1 15:50:34 +1 15:50:34 +1 15:50:39 +1 15:50:41 +1 15:50:55 Tim: +1 15:50:57 +1 15:51:06 +1 15:51:23 accepted: subactivity relation will not be included in normative documents, but instead would be described in light weight document, such as FAQ/best practice 15:51:51 Paul: Will setup FAQ that can also be referenced when responding to feedback 15:51:56 action: setup faq 15:51:56 Sorry, couldn't find user - setup 15:52:00 q+ 15:52:04 ack ivan 15:52:11 action: pgroth setup faq 15:52:11 Created ACTION-115 - Setup faq [on Paul Groth - due 2012-09-20]. 15:52:16 http://www.w3.org/2001/sw/wiki/Main_Page 15:52:16 ack pgroth 15:52:18 ack ivan 15:53:14 Ivan: There is a SW activity wiki, which can be used after WG formally closes - create a separate section on the wiki that can be continously used 15:53:23 Paul: Nice idea 15:53:45 zakim, mute me 15:53:45 Ivan should now be muted 15:53:49 Topic: Implementation Report 15:53:51 Paul: Will set up a PROV subsection on SW wiki 15:53:55 http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html 15:54:13 Paul: Thanks to Dong and Stephan to creating the implementation document 15:54:45 Paul: The skeleton of the document mirrors Stephan's questionnaire 15:55:18 Paul: Reviewing the implementation document 15:57:14 q? 15:57:21 Paul: Comments/questions about the structure of the implementation document? 15:57:24 (looked fine to me...) 15:58:01 Tim: Are there instructions to allow responders to add to this document? 15:58:09 Paul: Part of the questionnaire 15:58:29 q? 15:58:38 Stephan: Questionnaire is a spreadsheet so should be easy to map to document 15:59:21 Paul: Have a question about constraint section, it currently does not have a test case for implementation of the constraints 15:59:48 Paul: Should there be a test harness for this - concern that this will require significant work 15:59:50 q? 16:00:06 zakim, unmute me 16:00:06 Ivan should no longer be muted 16:00:08 Paul: Question is whether it is needed and who will do it? 16:00:11 q+ 16:00:32 Ivan: Not sure about test case environment 16:01:08 Paul: This environment allows testing a set of provenance assertions to be valid or invalid 16:01:09 - +1.818.731.aabb 16:01:40 + +1.818.731.aacc 16:01:58 Ivan: Nice to have an environment to make testing easier, but making a complete test environment requires lot of effort so not sure it can be done 16:03:00 Luc: I am implementing a validator and it involves lot of work - tests unification algorithm and requires lot of test cases (excludes temporal constraints) 16:03:20 hook has joined #prov 16:03:35 Luc: Does not guarantee complete coverage and not sure when a stable state test cases can be shared with rest of WG 16:04:19 Luc: So, not sure how the test cases can be re-used by others 16:04:44 Luc: May require development of a common API, so not an easy task 16:05:09 @zednik PROV-CONSTRAINTS now has 58 in total, I think the questionnaire still uses the constraints from the previous version of the document. 16:05:23 @Paul: sorry, I have to leave now can someone take over as scribe 16:05:29 ok 16:05:29 @dong, thanks I'll look into that 16:05:34 can someone scribe? 16:05:43 I can 16:05:45 thanks 16:05:52 scribe: dgarijo 16:05:52 thanks Dani! 16:06:10 -Satya_Sahoo 16:06:19 Ivan: we need test cases when we can infer additional things. If it can be automatized, good. 16:07:03 Luc: the complete normal form is not necessarily represented in Prov. 16:07:04 -??P10 16:07:24 Ivan: that is a lot of work. This formats may have their own live after the group finishes 16:08:00 Paul: even if we divide ourselves, we can't guarantee complete cover 16:08:58 hm, how 10 minuets becomes an hour.. I missed the whole thing! 16:09:00 Ivan: that's different. Test cases are never 100% complete (corner cases not covered). It should be possible to come up with a collection of test cases that the group supports. If not, we have a problem 16:09:30 is it still going on? Where in the agenda are we? 16:09:45 ... everybody will have to have his own test cases and be able to report them back to us 16:09:54 @stain: we are discussing the implementation 16:09:57 SPARQL working group have a nice vocabulary for defining their test cases. 16:10:27 pgroth: the next thing to do is to find how to define the test cases. 16:11:06 Ivan: there are many other groups that have been doing this. It may be worth taking a look 16:11:19 ok, sure 16:11:24 +stainPhone 16:11:29 pgroth: stephen, dong would you take a look at that? 16:11:34 stephen: ok 16:11:41 pgroth: we are out of time 16:11:53 ... we'll catch up online 16:11:59 - +1.315.330.aaaa 16:12:07 thanks, bye 16:12:09 stainPhone has joined #prov 16:12:11 -dgarijo 16:12:12 -Ivan 16:12:13 -MacTed 16:12:14 -Luc 16:12:14 -TomDN 16:12:15 - +1.818.731.aacc 16:12:15 -??P2 16:12:18 -Luc.a 16:12:20 rrsagent, set log public 16:12:22 -stainPhone 16:12:26 rrsagent, draft minutes 16:12:26 I have made the request to generate http://www.w3.org/2012/09/13-prov-minutes.html pgroth 16:12:30 trackbot, end telcon 16:12:30 Zakim, list attendees 16:12:30 As of this point the attendees have been Satya_Sahoo, Luc, +1.315.330.aaaa, Ivan, +1.818.731.aabb, jun, MacTed, TomDN, Samcoppens, dgarijo, +1.818.731.aacc, stainPhone 16:12:38 RRSAgent, please draft minutes 16:12:38 I have made the request to generate http://www.w3.org/2012/09/13-prov-minutes.html trackbot 16:12:39 RRSAgent, bye 16:12:39 I see 2 open action items saved in http://www.w3.org/2012/09/13-prov-actions.rdf : 16:12:39 ACTION: setup faq [1] 16:12:39 recorded in http://www.w3.org/2012/09/13-prov-irc#T15-51-56 16:12:39 ACTION: pgroth setup faq [2] 16:12:39 recorded in http://www.w3.org/2012/09/13-prov-irc#T15-52-11