16:02:52 RRSAgent has joined #prov 16:02:52 logging to http://www.w3.org/2011/09/26-prov-irc 16:02:54 RRSAgent, make logs world 16:02:54 Zakim has joined #prov 16:02:55 tlebo has joined #prov 16:02:56 Zakim, this will be 16:02:56 I don't understand 'this will be', trackbot 16:02:57 Meeting: Provenance Working Group Teleconference 16:02:58 Date: 26 September 2011 16:03:06 Zakim, this will be PROV 16:03:06 I do not see a conference matching that name scheduled within the next hour, Luc 16:03:15 wiki for this meeting: http://www.w3.org/2011/prov/wiki/PIL_OWL_Ontology_Meeting_2011-09-26 16:03:24 http://titanpad.com/wN4lUHpAcv 16:04:33 Zakim, this will be SW_(OWL) 16:04:33 ok, Luc, I see SW_(OWL)12:00PM already started 16:04:54 http://dvcs.w3.org/hg/prov/raw-file/2b514f651c03/ontology/examples/ontology-extensions/crime-file/diagrams/2011-09-26-tlebo/crime.owl.png 16:04:55 rrsagent, make logs public 16:05:03 Chair: Satya 16:05:40 +??P0 16:06:34 khalidbelhajjame has joined #prov 16:07:26 what is provenanceContainer in entity? I don't understand the notation used. 16:07:59 file:///home/stain/stuff/src/provenance-wg/prov/ontology/ProvenanceFormalModel.html#provenancecontainer I guess 16:08:14 that is a subclass 16:08:48 q+ 16:09:16 +??P3 16:09:44 TODO: break all visual abbreviations - show rdfs:subClassOf directly. 16:09:54 Luc does not like that a ProvenanceContainer is a subclass of Entity 16:10:05 TODO: ensure that the ProvenanceContainer is no longer an Entity. (Tim) 16:10:17 it's not that Luc doesn't like. It does not match the data model. 16:10:43 In PROV-DM, an entity expression is a representation of an identifiable characterized thing. 16:10:48 so is the provcontainer not one of those? 16:11:25 no 16:11:25 luc: top level classes: ProvenanceContainer, Account, Entity, ProcessExecution 16:11:55 http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#ProvenanceContainer 16:12:00 http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#ProvenanceContainer 16:12:34 q? 16:12:38 q- 16:12:44 This is PROV-ISSUE-66 16:12:50 paolo: we are not "directly" asserting provenance of ProvenanceContainer 16:14:23 dgarijo has joined #prov 16:14:35 I think we should just stick to the data model as much as possible 16:15:42 @khalid: yes, of course. But if the model is designed for asserting provenance, then it should provide the mechanisms to assert provenance about provenance records too! 16:16:10 +q 16:16:27 satya, there is a type error! 16:17:30 (the objective of the diagram was to illustrate how a third party could extend PROV - does anyone have feedback on how well/poorly this is conveyed?) 16:17:49 could you provide the link to the diagram, please? I joined late :( 16:18:01 tlebo: I think it's good, but I wonder if we could show extension by subproperties or subclass 16:18:02 http://dvcs.w3.org/hg/prov/raw-file/2b514f651c03/ontology/examples/ontology-extensions/crime-file/diagrams/2011-09-26-tlebo/crime.owl.png 16:18:20 just adding new attributes to an prov:Entity is merely how entity is to be used anyway..? 16:18:45 @stian: news:Entity subclass prov:Entity , THEN assert the domains on news:Entity ? 16:18:58 you can take multiple perspective on a provenance container: it's a curated set of assertions, it's a set of triples in a triple store, it's a 'platonic' set of triples, it's something in a database. 16:18:58 so Journalist subclass of Agent, or Publishing subclass of ProcessExecution might be interesting. But then you are very close to the danger of touching on roles.. 16:19:08 Each of them can be modelled by an entity expression. 16:19:47 An apple is represented by an entity expression, which involves selecting some attributes 16:20:10 -q 16:21:51 http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Account says 16:21:54 Note: Currently, the non-terminal asserter is defined as URI. We may want the asserter to be an agent instead, and therefore use PROV-DM to express the provenance of PROV-DM assertions. The editors seek inputs on how to resolve this issue. 16:22:03 is this what we've briefly touched on? 16:23:40 yes stain 16:23:51 I have to agree with Satya 16:23:58 I don't see the difference either. 16:25:09 if a prov container can be set of statements, and we are able to refer to them and assert triples using them as source, then it has a identifier. 16:26:47 the corollary of what Luc is saying, i.e., viewing a provenance container as a "thing in the world", is that you don't need to make ProvenanceContainer a subclass of Entity in order to do "meta-provenance" 16:27:21 so Luc's point is that there (could be) other attributes you need to specify, like the location the provenance container is stored in, or description of its content, etc - many entities 16:28:02 +q 16:28:09 En entity is a characterization of a thing, provenance container is not necessarily a characterization of a thing. 16:29:07 mm.. so there's nothing saying a ProvContainer *is not* an entity, but it would probably not be a good entity on its own because there are many ways to describe such meta-provenance 16:29:43 A provContainer can be a characterization, but not necessarily one. 16:30:33 q+ 16:30:43 ack daniel 16:31:13 -q 16:31:18 ack satya 16:32:42 q+ 16:32:45 ok, now it is clear for me. So basically Prov container and Entity are not disjoint, but not necessarily the former subclass of the latter. 16:33:16 and t might be misleading to say it is always an entity, because it hints that you *should* do meta-provenance in only a single way 16:34:08 :) 16:34:26 provenanceContainer: is a list of accounts, namespace definitions, and a collection of provenance assertions. 16:36:39 so provenanceContainer() in the model is rdf:RDF (or equivalent headers) in RDF 16:36:55 JSON needs ProvenanceContainer, while RDF/OWL does not need it "because it comes for free". 16:37:05 @tim: but it depends on the way you implement it: if you select named graphs, then your provenance container could be the named graphs. 16:37:20 mm.. and then you can do RDF->model->JSON->model->RDF and somewhat at least don't mess up namespaces and stuff 16:41:14 TODO: class diagram (Khalid) 16:41:25 how is this group proposing to model accounts? 16:41:31 http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html 16:41:33 http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html#specialization-of-provenance-ontology-classes 16:42:11 @Luc: should they be a subclass of provenance container? 16:42:30 @Luc I think we are still thinking of that as named graph / separate OWL/RDF resources per account - due to how identifiers depends on the account in the abstract model 16:43:11 since they are a collection of provenance assertions too. 16:43:13 yes, probably name graph would be the way ... but then this does not show in OWL? 16:43:26 stian: show the other subclasses of the extension. 16:43:39 (TODO: Tim show this) 16:43:40 @Luc, yes I agree, we should be as explicit as possible 16:45:28 and what about having account as subclass of prov container? I think it could be fine. 16:46:30 @daniel, an account would then inherit prov container's properties ... but accounts have no namespace, and no index of accounts 16:46:49 @Daniel yes that would be reasonable -- something we discussed in the model 16:47:11 the news crime file example: http://dvcs.w3.org/hg/prov/raw-file/2b514f651c03/ontology/examples/ontology-extensions/crime-file/instances/example-1/crime.ttl.vertical.png 16:47:41 I would suggest to do role example with a process execution with 2 or more uses or 2 or more generations 16:47:45 so that you see why you would want a role 16:47:51 or 2 or more agents 16:48:21 I have some in http://dvcs.w3.org/hg/prov/raw-file/default/ontology/examples/ontology-extensions/workflow/prov2.ttl 16:48:49 i will have to go, sorry! 16:49:00 bye! 16:49:54 ok bye Daniel 16:49:55 http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html#entity 16:50:06 those notes don't match the exxmple 16:50:23 no, I wasn't leaving, just saying bye to Luc :) 16:50:36 - +44.238.059.aabb 16:52:18 oh ok :) 16:52:41 bye Luc 16:59:00 +1 16:59:35 satya: we let the conceptual model become the logical model. 17:04:10 -??P0 17:05:29 +??P0 17:09:34 Got to go. 17:09:38 -??P27 17:09:48 see you, jcheney. 17:12:13 guys I really have to go 17:12:22 see you, paolo! 17:12:40 bye 17:13:16 -??P28 17:17:50 rrsagent, set log public rrsagent, draft minutes trackbot, end telcon 17:17:50 I'm logging. I don't understand 'set log public rrsagent, draft minutes trackbot, end telcon', tlebo. Try /msg RRSAgent help 17:18:01 rrsagent, set log public 17:18:09 rrsagent, draft minutes 17:18:09 I have made the request to generate http://www.w3.org/2011/09/26-prov-minutes.html tlebo 17:18:18 trackbot, end telcon 17:18:18 Zakim, list attendees 17:18:18 As of this point the attendees have been Satya_Sahoo, +1.315.330.aaaa, stain, +44.238.059.aabb 17:18:19 RRSAgent, please draft minutes 17:18:19 I have made the request to generate http://www.w3.org/2011/09/26-prov-minutes.html trackbot 17:18:20 RRSAgent, bye 17:18:20 I see no action items