14:53:18 RRSAgent has joined #prov 14:53:19 logging to http://www.w3.org/2011/09/22-prov-irc 14:53:20 RRSAgent, make logs world 14:53:21 Zakim has joined #prov 14:53:22 Zakim, this will be 14:53:22 I don't understand 'this will be', trackbot 14:53:23 Meeting: Provenance Working Group Teleconference 14:53:24 Date: 22 September 2011 14:53:28 Zakim, this will be PROV 14:53:28 ok, pgroth; I see SW_(PROV)11:00AM scheduled to start in 7 minutes 14:53:29 SW_(PROV)11:00AM has now started 14:53:36 +Curt_Tilmes 14:53:40 I will scribe 14:53:57 Agenda: http://www.w3.org/2011/prov/wiki/Meetings:Telecon2011.09.22 14:54:08 Chair: Paul Groth 14:54:14 Scribe: Curt Tilmes 14:54:25 rrsagent, make logs public 14:54:31 there you go Curt 14:54:35 thanks for stepping up 14:55:46 +??P7 14:55:59 + +44.789.470.aaaa 14:56:06 dgarijo has joined #prov 14:56:15 Zakim, +44.789.470.aaaa is me 14:56:15 +stain; got it 14:56:54 Regrets: Helena Deus, Stephan Zednik, Christine Runnegar 14:57:59 Paolo has joined #prov 14:58:11 satya has joined #prov 14:58:30 +??P48 14:58:41 zakim, ??P48 is me 14:58:41 +Paolo; got it 14:58:48 JimM has joined #prov 14:59:11 +??P49 14:59:17 +??P53 14:59:34 +??P8 14:59:41 + +1.518.276.aabb 14:59:44 Zakim, ??P8 is me 14:59:44 +dgarijo; got it 14:59:50 -??P49 14:59:51 +??P17 14:59:51 Vinh has joined #prov 14:59:59 +Satya_Sahoo 15:00:08 +??P29 15:00:08 zaim, ??P17 is me 15:00:12 Zakim, +1.518.276.aabb is me 15:00:12 +JimM; got it 15:00:18 zakim, ??p29 is me 15:00:18 +GK; got it 15:00:18 zakim, ??P17 is me 15:00:20 +Luc; got it 15:00:41 StephenCresswell has joined #prov 15:00:59 + +1.937.343.aacc 15:01:15 zakim, +1.937.343.aacc is me 15:01:15 +Vinh; got it 15:01:19 JimMcCusker has joined #prov 15:01:44 tlebo has joined #prov 15:01:45 khalidbelhajjame has joined #prov 15:01:51 + +1.518.276.aadd 15:02:03 +??P12 15:02:12 zakim, aadd is me 15:02:12 +tlebo; got it 15:02:54 Topic: Admin 15:02:58 http://www.w3.org/2011/prov/meeting/2011-09-15 15:03:04 PROPOSED to accept the minutes of Sep 15 telecon 15:03:06 +1 15:03:08 +1 15:03:09 +1 15:03:11 +1 15:03:14 +1 15:03:14 StephenCresswell_ has joined #prov 15:03:15 +1 15:03:18 +1 15:03:47 0 (did not attend) 15:03:52 +Sandro 15:03:58 http://www.w3.org/2011/prov/track/actions/open 15:04:16 +??P36 15:04:36 pgroth: action on Satya superceded by Sandro's work we'll cover later -- close it 15:04:44 zkim, ??P36 is me 15:04:51 Reviews for RDB2RDF working group specs 15:05:08 sandro has changed the topic to: Provenance WG -- http://www.w3.org/2011/prov/ -- 2011-09-22 telecon agenda: http://www.w3.org/2011/prov/wiki/Meetings:Telecon2011.09.22 15:05:09 pgroth: RDB2RDF working group has released 2 documents 15:05:21 ... may be of interest to this group 15:05:42 q? 15:06:03 zakim, ??P36 is me 15:06:03 +khalidbelhajjame; got it 15:06:05 Luc: do they want us to look at a specific section? 15:06:15 what is RDB2RFF? 15:06:28 RDB2RDF 15:06:32 jcheney has joined #prov 15:06:38 pgroth: RDB2RDF is working on relational databases 15:06:45 ... not sure which sections we might be interested in 15:06:50 @khalid: mapping from Relational to RDF 15:06:57 ... follow up to mailing list 15:06:58 http://www.w3.org/2011/prov/wiki/Scribes 15:07:08 ... need scribes, please sign up 15:07:11 I was part of the RDB2RDF incubator group and worked on a survey - may have mentioned about provenance in that, I will try to review it 15:07:27 +??P16 15:07:38 zakim, ??P16 is me 15:07:38 +jcheney; got it 15:07:46 q? 15:07:55 Topic: Report on RDF Named Graph Discussion 15:08:01 pgroth: sandro to summarize RDF discussion 15:08:11 http://www.w3.org/2011/rdf-wg/meeting/2011-09-15 15:08:32 sandro: last week we had a common meeting with RDF group, many from both groups 15:08:51 ... didn't get as far as we wanted, missing some common language 15:09:13 ... trying to determine what is needed in RDF to support provenance requirements 15:09:24 ... where will we need RDF to support provenance 15:09:34 ... provenance of RDF is needed by both groups 15:09:41 smiles has joined #prov 15:09:51 ... sandro took action item to develop use case 15:09:52 +??P24 15:10:00 ... which was sent to both groups 15:10:24 ... unifying use case combining multiple inputs to determine trust 15:10:46 ... use case of restaurant reviews is a simple stand in for overall use case 15:11:07 ... didn't schedule next telecon, but follow up on mailing list rdf-prov 15:11:22 q? 15:11:27 ... hopefully make progress on addressing issues from both groups 15:11:28 q? 15:11:57 pgroth: is it clear what this group needs to provide? 15:11:57 what was the rdf + prov list address? 15:11:58 q? 15:12:06 ... what is the path forward? 15:12:20 sandro: we haven't decided on a path forward yet 15:12:28 ... still waiting on responses to use case 15:12:47 +q 15:12:53 ... would be good to hear comments, either that is right, or here's how to change it 15:13:04 (Seems to me that we need to understand each others' language and expectations before charting a route forwards) 15:13:22 ... please comment and feed back to sandro 15:13:41 ack jcheney 15:13:57 public-rdf-prov@w3.org 15:14:09 jcheney: didn't attend telecon, use case reminded of incubator use cases 15:14:23 ... someone familiar with incubator use cases may want to take a look 15:14:42 http://www.w3.org/2005/Incubator/prov/wiki/User_Requirements 15:14:43 ... incubator had a short paper on named graphs for RDF that could help 15:14:53 http://www.w3.org/2009/12/rdf-ws/ 15:14:55 @Sandro: one reason you may not get responses is the requirement to participate in yet another mailing list 15:15:09 sandro: please summarize large documents, since people won't read the large docs. 15:15:19 q? 15:15:29 http://www.w3.org/2005/Incubator/prov/wiki/images/3/3f/RDFNextStep_ProvXG-submitted.pdf 15:15:46 pgroth: another issue - our conceptual model has different versions/serializations 15:16:09 ... we could figure out how to convert our stuff into current RDF 15:16:24 ... it is hard to determine how RDF might change 15:16:30 @pgroth +1 15:16:39 q+ to disagree with sandro 15:17:05 sandro: RDF lacks mechanism to express endorsement of triples 15:17:09 q+ 15:17:36 GK: disagree - there are ways to express those things 15:17:47 ... RDF has those mechanisms, maybe complicated, but possible 15:18:12 ... could develop simpler mechanisms to handle them 15:18:21 graph literals? 15:18:24 ... what should we call them instead of named graphs? 15:18:29 ... just 'graphs'? 15:18:31 ack GK 15:18:31 GK, you wanted to disagree with sandro 15:18:38 graph literal is interpreted differently from named graph 15:18:41 ack JimM 15:18:44 q? 15:18:47 (it's possible to do this in RDF if you define your own vocab, but there's no standard/interoperability) 15:19:13 JimM: could use graph hashes to handle referring to the graph 15:19:16 q+ 15:19:22 JimM: there are solutions out there 15:19:26 @JimM - sounds like a possibility I had in mind... 15:19:29 ack satya 15:19:32 satya: we are conflating two issues 15:19:53 JimM, please suggest them to public-rdf-prov? 15:19:57 ... when you refer to a URL, the reponse you get today is different from tomorrow 15:20:11 ... if the application needs the version, that can be modeled 15:20:25 ... it is a modeling issue 15:20:33 (it can be modeled, but we need a standard for how to model it, otherwise there is no interop.) 15:20:33 @satya +1 15:20:34 ... don't mix up that with changes needed to RDF model 15:20:41 q? 15:20:45 https://github.com/timrdf/csv2rdf4lod-automation/wiki/frbr:mccusker2012parallel 15:20:52 I'm wondering how "provenance of contents in named graphs" differs from "provenance of contents in files on disk". 15:21:01 pgroth: thanks sandro -- we'll try to help 15:21:04 tlebo, I'm not sure it does. 15:21:06 Topic: Mapping the Conceptual Model to the Formal Model 15:21:07 Sorry, use the purl: http://purl.org/twc/pub/mccusker2012parallel 15:21:24 @tlebo: at some level I don't think it does differ 15:21:26 Yogesh has joined #prov 15:21:28 One of the things I think we need from 'named graphs' is to be able to sign the statement " " - without some scoping besides files we have the graph in one file, the statement before in another and the ,thisstatement> in a third - gets messy... 15:21:33 tlebo, maybe the tools are different. n3 has nice syntax for it. 15:22:04 paolo: summarize two way process mapping conceptual model to formal model 15:22:14 ... conceptual model will drive formal model 15:22:16 sandro, I can take that as an action. 15:22:35 ... if OWL2 falls short, we can address 15:22:55 + +1.213.290.aaee 15:23:09 ... there are ways to model roles in OWL2, but that might stray from our model 15:23:21 zakim, ??24 is me 15:23:21 sorry, smiles, I do not recognize a party named '??24' 15:23:22 ... mapping onto OWL2 might not be as smooth as we might like 15:23:27 ... consider other direction 15:23:29 q? 15:23:30 zakim, ??P24 is me 15:23:30 +smiles; got it 15:23:58 ... there are fragments of the concepual model that might not be part of OWL model 15:24:21 satya: issue of how we model roles is not specific to OWL 15:24:37 ... there are some modeling approaches in some large ontology communities 15:24:45 ... they have proposed ways to model information 15:24:56 ... most of the modeling realizations are in OWL2, but there 15:25:03 ... are subtle differences 15:25:30 paolo: some things won't map into OWL2 easily 15:25:34 zakim, +1.213 is me 15:25:34 +Yogesh; got it 15:25:38 q+ to raise the issue on interoperability across technologies 15:25:46 q? 15:25:58 satya: WG should decide what we will use -- different approaches have different advantages 15:26:11 @satya - maybe, but I think we should prefer approaches that can use existing stack ... which is what I think you're saying just now 15:26:18 ... if we decide to use something, we should follow constraints of specification 15:26:43 ... if we are to follow semantic web stack, we should stick to it 15:26:57 jorn has joined #prov 15:27:08 q+ to ask if there is any question that we will use the semweb technology stack 15:27:11 paolo: if we decide to use semantic web stack, can the conceptual model be expressed? 15:27:30 The problem as I see it is that there are many possible way of translating the conceptual model to OWL, and the problem is really which way is the "best" 15:27:50 ... whatever model we decide on needs to be expressible in the semantic web stack 15:28:20 @khalid - mostly true, I think, but there might be some semantic gaps in using just OWL 15:28:31 Q? 15:28:39 @Graham, agreed 15:29:06 satya: more important than OWL2 constraints, there are certain things we need to clarify first 15:29:08 ack Luc 15:29:08 Luc, you wanted to raise the issue on interoperability across technologies 15:29:14 ... then we'll address OWL2 representation 15:29:23 can't hear you well 15:29:30 @satya +1 need to be clear about consensus on concepts 15:29:32 Luc: 15:29:44 Luc - we can't hear you well 15:29:49 Luc going dalek... 15:29:56 -GK 15:29:59 Luc: provenance ... something ... 15:30:59 pgroth: (summarize Luc): one issue is interoperability across multiple technologies 15:31:17 ... what we are doing with conceptual model must maintain interoperability across 15:31:24 thanks paul 15:31:50 q? 15:31:54 q+ 15:32:21 my point is that the WG should make a statement about what it means about interoperability 15:32:32 satya: interoperability is important and valid concern, but we are most concerned with using 15:32:49 ... semantic web stack which will enable interoperability with e.g. XML stack 15:32:52 graham you on the phone? 15:33:02 ... it may not be possible to please every technology 15:33:33 paolo: are we constrained by expressivitity of semantic web stack? 15:33:44 paolo: that can affect our design choices 15:33:56 q? 15:33:59 GK has joined #prov 15:34:01 ack Paolo 15:34:11 satya: agreed, there are semantic web constraints 15:34:34 Paolo, I think that in most cases there is no problem of translating the conceptual model to OWL, the probelm is that the mappings between the two model is not a 1 to 1 mapping, and may lead in some cases to ugly mappings if we are not careful 15:35:00 ... how we are interpreting concepts needs clarification prior to getting to representation 15:35:32 paolo: formal model informing conceptual model is a valuable realtity check 15:35:35 q? 15:35:39 ack GK 15:35:39 GK, you wanted to ask if there is any question that we will use the semweb technology stack 15:35:40 and perhaps OWL would allow many other things that is not considered in the conceptual model - like role class inheritance or what kind of identifiers we are talking about 15:35:47 +??P6 15:35:48 @khalid: I think you're right 15:36:38 GK: is there a question about building provenance specification that works with semantic web stack? 15:36:39 q? 15:37:03 as the ONLY stack supported? 15:37:11 pgroth: paolo is asking how we are constrained by things like OWL2 15:37:28 satya: semantic web = RDF, OWL, SPARQL, all together 15:37:59 pgroth: that is a clear direction in our charter -- we need to address those technologies 15:38:12 @Luc: as the _primary_ stack, not to exclude others. 15:38:22 @GK +! 15:38:24 +1 15:38:35 ... is that the only stack: broadly no, but how are we constrained to best work with semantic web technologies 15:38:36 from charter: 15:38:38 The idea that a single way of representing and collecting provenance could be adopted internally by all systems does not seem to be realistic today. 15:39:05 paolo: once we iron out some ambiguities, may not be as big a concern 15:39:12 q+ 15:39:14 btw, we can Get This Done with JUST RDF; OWL should only come into play when it provides a clear value. 15:39:18 ack satya 15:39:32 satya: ideally we should just support semantic web 15:39:48 ... but they are standards that define certain things, that may end up excluding other things 15:39:57 why do we have a conceptual model then? 15:39:59 ... we should keep that in mind 15:40:10 +q 15:40:14 @luc, regarding "just RDF"? 15:40:20 ack khalidbelhajjame 15:40:24 q? 15:40:39 khalidbelhajjame: semantic web doesn't exclude other technologies 15:40:59 q? 15:41:03 ... conceptual model is needed to address mapping to other technologies 15:41:12 thanks khalid 15:41:28 pgroth: not clear how conceptual model might violate any semantic web constraints 15:41:50 @pgroth +1 (but we may want to think about engineering issues too) 15:41:53 ... some things may be harder with semantic web, but it isn't clear yet what might break 15:41:53 q+ 15:41:59 but we can't depend too much on various OWL mechanisms that would be difficult to express in other formats like JSON. I think we should have some kind of nicely degradation to those formats, where everything expressed by PROV is retained, but other attributes are lost 15:41:59 ack Paolo 15:42:13 paolo: modeling of roles still needs work 15:42:30 ... if we model it as a subclass of entity, it makes sense to me 15:42:56 ... we are still working on role modeling we need to think about implications 15:42:59 q? 15:42:59 @stian: I see the role (sic) of OWL as something roughly like a schema and formal semantics spec for proveance exchanged as RDF 15:42:59 if roles are the only problem, can we solve everything else, and then revisit roles both in conceptual model and owl ontology? 15:43:33 @GK +1 15:43:38 pgroth: we need to see where things are hard to represent 15:43:48 @GK +1 15:44:02 ... we may need to make things ugly to handle conceptual mode 15:44:12 +stain.a 15:44:20 paolo: it is an ongoing process, 15:44:24 q? 15:44:25 -stain 15:44:49 q? 15:44:53 satya: what about trying to represent in OWL/SPARQL, just trying to guage feeling of group 15:44:54 q+ 15:45:15 Luc: how do we progress? 15:45:35 pgroth: conceptual model needs feedback from formal model 15:45:38 proposal: park roles for now, and move on 15:45:57 ... if group likes conceptual model, then goal of formal model to represent that 15:45:57 q? 15:46:03 ack 15:46:05 ack Luc 15:46:33 satya: if we have a clear view of notions in conceptual model, formal model is easy 15:46:51 ... problem is defining conceptual model enough to develop formal model 15:46:58 why not rename 'role' in conceputal model into 'function'? 15:47:00 @satya: +1 15:47:01 ... some terms aren't clear enough to drive formal model 15:47:09 ... iterative feedback to make them match 15:47:29 satya: roles is one issues, there are others 15:47:51 satya: e.g. versioning perspectives 15:47:52 q+ to say that I think the latest prov model doc will make this discussion easier 15:48:07 +??P5 15:48:09 saty, for versioning, you have not raised any issue against conceptual document 15:48:12 zakim, ??p5 is me 15:48:12 +jorn; got it 15:48:17 ack GK 15:48:17 GK, you wanted to say that I think the latest prov model doc will make this discussion easier 15:48:42 GK: difficulty is in coming to understanding. latest version of the model has helped clarify some things 15:48:48 sorry Luc, I am still reviewing - I will start posting issues on a section-wise basis 15:48:57 ... recent direction has helped discussion progress 15:49:00 GK: I agree, the last version is much clearer 15:49:21 I think we also should do some "cleaning" in the owl documents and html. I don't think they are currently synchronized, and could lead to confussion. 15:49:26 pgroth: raise issues out of formal model with conceptual model to clarify them 15:49:39 Topic: Conceptual Model 15:49:49 @Daniel: Agree, working on it now :) 15:49:51 paolo: New iteration released for discussion 15:49:58 paolo: few comments so far. 15:50:09 ... that version has many improvements that address issues 15:50:15 @Satya :) 15:50:19 ... several things resolved pending review 15:50:45 ... addressing Khalid's comments 15:50:53 ... process is converging 15:51:11 ... some issues open, some are old and will be closed soon 15:51:20 ... will F2F with Luc to resolve some things 15:51:34 ... planning to address remaining issues 15:51:35 +1 paolo: "if the process is convergent, no need to over-fromalize the process" :) 15:52:08 ... good input on several issues, some have more discussion than others 15:52:09 the key question at this stage is are they issues that would block the release as FPWD. We need to prioritize them. 15:52:23 the key question at this stage is are there issues that would block the release as FPWD. We need to prioritize them. 15:52:26 @Tim, Jim - can you please share your work on RDF named graph - maybe as a technical report? 15:52:33 ... when issues don't get a lot of input, little guiidance to resolve them, we do what we can 15:52:34 q? 15:52:49 ... issue 89, 99 need work 15:52:54 -Vinh 15:53:01 Ideally, an issue will have a proposed resolution that the editors can accept or discuss 15:53:11 q? 15:53:41 pgroth: next week we will vote on whether to release public working draft? 15:53:47 Luc: Yes, correct 15:54:12 Luc: We need to flag outstanding issues and prioritize and address them prior to release 15:54:13 q+ to check that FPWD doesn have to imply group consensus 15:54:23 pgroth: please raise major blocks asap 15:54:40 GK: a public working draft doesn't need complete consensus, some things can remain open 15:54:47 @GK - I agree 15:54:51 pgroth: correct 15:54:53 agreed. wd does not need to be consensus. 15:54:55 i am very happy to write in document issues still to be addressed 15:55:18 but it's very good to point out in the draft wherever there is still an open issue. 15:55:20 pgroth: some issues may be open, that's ok and need discussion, but if there are major blockers, 15:55:27 ... prior to release to public, raise them now 15:55:55 GK: are we ready to release and ask for public comment. 15:56:08 paolo: are there showstoppers we need to be aware of? 15:56:33 paolo: please raise them asap, we are meeting tomorrow, please let us know right away about any red flags 15:56:55 @GK, you mention by email you had issues you wanted to raise, can you give us a preview for us to work on? 15:56:56 I don't mind doc going FPWD if I'm still allowed to disagree with bits :) 15:57:10 Topic: Formal Model 15:57:13 @luc I'll try 15:57:32 @GK, thanks, if you want we can also have quick call tomorrow 15:57:38 satya: formal model has been updated with help 15:57:58 ... some parts missing, diagrams, taking longer than we had hoped 15:58:11 ... pre-release to this group soon 15:58:39 ... changes illustrating how to extend to handle domain specific may be helpful 15:58:57 ... scientific workflow extension to be included 15:59:08 -Luc 15:59:25 ... New concepts in conceptual model not yet in formal model 15:59:35 ... still need to digest new additions to conceptual model 16:00:01 ... some gaps need clarifications to map notions from conceptual model to formal model 16:00:12 +q to ask if the OWL ontology should include all the concepts in the conceptual model 16:00:13 ... some continuous updates will happen as conceptual model changes 16:00:17 ... iterative process 16:00:27 Q? 16:00:29 q- 16:00:34 ack khalidbelhajjame 16:00:34 khalidbelhajjame, you wanted to ask if the OWL ontology should include all the concepts in the conceptual model 16:00:48 @satya, regarding content identity and named graphs, we will talk to our co-authors to see if we can do that. 16:00:52 q? 16:00:57 khalidbelhajjame: will every concept in conceptual model need to be in formal model, or a subset? 16:01:18 @Jim - thanks 16:01:22 pgroth: a correct set is more important than to be complete 16:01:32 q? 16:01:33 @Paul, thanks 16:01:35 @Paul: thanks 16:01:38 q? 16:01:43 @khalid: I thought the formal model was supposed to be a lightweight notion of the conceptual model. 16:02:03 @Daniel: no 16:02:07 pgroth: please get comments on everything in 16:02:12 ... need to vote on public releases 16:02:13 -tlebo 16:02:15 -smiles 16:02:16 -Paolo 16:02:18 -Satya_Sahoo 16:02:20 -Yogesh 16:02:22 -Sandro 16:02:24 -jcheney 16:02:26 -stain.a 16:02:26 jorn has left #prov 16:02:28 -JimM 16:02:30 -jorn 16:02:31 rrsagent, set log public 16:02:40 rrsagent, draft minutes 16:02:40 I have made the request to generate http://www.w3.org/2011/09/22-prov-minutes.html pgroth 16:02:42 -??P6 16:02:47 trackbot, end telcon 16:02:47 Zakim, list attendees 16:02:48 -Curt_Tilmes 16:02:48 RRSAgent, please draft minutes 16:02:48 I have made the request to generate http://www.w3.org/2011/09/22-prov-minutes.html trackbot 16:02:49 RRSAgent, bye 16:02:49 I see no action items