15:38:44 RRSAgent has joined #prov 15:38:44 logging to http://www.w3.org/2012/01/19-prov-irc 15:38:46 RRSAgent, make logs world 15:38:46 Zakim has joined #prov 15:38:48 Zakim, this will be PROV 15:38:48 ok, Luc; I see SW_(PROV)11:00AM scheduled to start in 22 minutes 15:38:48 Zakim, this will be 15:38:49 Meeting: Provenance Working Group Teleconference 15:38:49 Date: 19 January 2012 15:38:49 I don't understand 'this will be', trackbot 15:38:57 Agenda: http://www.w3.org/2011/prov/wiki/Meetings:Telecon2012.01.19 15:39:09 Chair: Luc Moreau 15:39:09 Paolo has joined #prov 15:39:14 rrsagent, make logs public 15:45:11 Scribe: satya 15:56:04 pgroth has joined #prov 15:56:36 SW_(PROV)11:00AM has now started 15:56:43 +??P29 15:56:46 Zakim, who is on the call? 15:56:46 On the phone I see ??P29 15:56:54 Zakim, ??P29 is me 15:56:54 +pgroth; got it 15:57:16 satya has joined #prov 15:58:06 +??P4 15:58:18 zakim, ??p4 is me 15:58:20 +Paolo; got it 15:58:36 +Luc 15:58:54 +Satya_Sahoo 15:59:43 q? 15:59:54 zakim, who in on the call? 16:00:05 smiles has joined #prov 16:00:08 I don't understand your question, Luc. 16:00:14 +??P6 16:00:16 +??P18 16:00:23 zakim, who in on the phone? 16:00:23 I don't understand your question, Luc. 16:00:29 zakim, who is on the call? 16:00:29 On the phone I see pgroth, Paolo, Luc, Satya_Sahoo, ??P6, ??P18 16:00:37 tlebo has joined #prov 16:00:42 stephenc has joined #prov 16:01:06 +AlexHall 16:01:11 +tlebo 16:01:25 Mike has joined #prov 16:02:22 dgarijo has joined #prov 16:02:51 http://www.w3.org/2011/prov/meeting/2011-01-12 16:02:55 Luc: Discuss PROV-DM, identifiers, and if possible accounts 16:02:56 PROPOSED: to accepted the minutes of Jan 12 teleconference 16:03:02 +1 16:03:07 topic: Admin 16:03:14 +1 16:03:16 +1 16:03:27 -1 http://www.w3.org/2011/prov/meeting/2011-01-12 404s 16:03:34 0 (absent) 16:03:48 http://www.w3.org/2011/prov/meeting/2012-01-12 16:03:51 +[IPcaller] 16:04:00 +1 16:04:04 +1 16:04:07 +1 16:04:16 Zakim, [IPcaller] is me 16:04:25 Accepted: the minutes of Jan 12 teleconference 16:04:34 http://www.w3.org/2011/prov/track/actions/open 16:04:45 Luc: Reviewing outstanding actions 16:04:53 +dgarijo; got it 16:05:01 Luc: 1. Write a blog on PROV-DM 16:05:29 +sandro 16:05:35 http://www.w3.org/2011/prov/wiki/Meetings:Telecon2012.01.05#prov-dm 16:06:02 185, 186, 187, 188, 189, 192, 193, 200 16:06:20 (the issues that are on Satya's action) 16:06:35 Luc: 2. Action for Satya to respond to outstanding issues 16:07:01 Topic: prov-dm 16:07:02 Luc: Please sign up for scribe duties 16:07:14 http://lists.w3.org/Archives/Public/public-prov-wg/2012Jan/0073.html 16:07:21 jcheney has joined #prov 16:07:37 +OpenLink_Software 16:07:53 q? 16:07:57 +??P12 16:07:59 missed it. Didn't realize there was a vote. 16:08:03 yes, sorry, just been swamped, no other reason 16:08:05 zakim, ??P12 is me 16:08:05 +jcheney; got it 16:08:09 mostly lost in the noise for me 16:08:11 Zakim, OpenLink_Software is temporarily me 16:08:11 +MacTed; got it 16:08:12 Luc: Need to vote on issue at: http://lists.w3.org/Archives/Public/public-prov-wg/2012Jan/0073.html 16:08:13 Zakim, mute me 16:08:13 MacTed should now be muted 16:08:20 +q 16:08:21 zednik has joined #prov 16:08:31 Luc: Will send a reminder to vote 16:08:51 + +1.518.633.aaaa 16:08:55 ack pgroth 16:08:57 PROV-ISSUE-206: three proposals to vote on (deadline Jan 15th midnight GMT) 16:09:04 Paul: Indicate the content for voting in the subject line 16:09:46 -dgarijo 16:09:52 Luc: Already listed in the subject line of the mail 16:10:47 Luc: Next item - Paolo and me have been editing PROV-DM - specialization and alternateOf 16:11:09 Luc: Reaching agreement on the transitivity of these constructs 16:11:40 Luc: Have addressed all issues for the third release of DM 16:11:45 +??P27 16:11:47 @stian are you available tomorrow -- new attempt to connect re: the collections setion 16:11:48 q? 16:11:58 Luc: Outstanding issues have been listed at end of each section 16:12:09 q? 16:12:29 Zakim, ??P27 is me 16:12:29 +dgarijo; got it 16:12:34 khalidbelhajjame has joined #prov 16:12:40 Luc: Propose to vote on release of DM as third working draft for next week 16:12:42 Topic: prov-o 16:12:56 Luc: Next item - PROV-O document 16:13:56 todo list that has been making progress is in meeting notes http://www.w3.org/2011/prov/wiki/PIL_OWL_Ontology_Meeting_2012-01-16 16:14:00 +[IPcaller] 16:14:03 q? 16:14:07 +q 16:14:15 zakim, IPcaller is me 16:14:15 +khalidbelhajjame; got it 16:14:38 ack dga 16:15:14 @satya: that's great 16:16:00 Mike is joining the PROV-O team as co-editor 16:16:17 Mike: Working on blog post examples will soon post an update 16:16:34 @satya : will we be discussing the best practices doc this monday too? 16:16:45 Luc: Mike is joining the PROV-O team as co-editor 16:17:05 q? 16:17:05 +q 16:17:17 ack dg 16:17:52 +q 16:18:02 Daniel: The PROV-O is becoming unwieldy with qualified involvement construct 16:18:16 Daniel: Would it make sense to have two resources? 16:18:32 q? 16:18:35 ack pg 16:18:43 @Paul, I think we were thinking more about files, where people who are interested in a provo-light can use it 16:18:49 +q to say that we'll need "modules" for the prov-o "syntax" and prov-o "constraints" portions. So we'll need to tackele "modules" anywayy. 16:19:41 Paul: Recommend have both resources with same namespace instead of having two separate resources 16:19:42 @tim: yeah, but the modules can share the namespace, right? 16:20:02 I have to agree with paul on the namespace requirement. 16:20:06 q? 16:20:08 ack tl 16:20:08 tlebo, you wanted to say that we'll need "modules" for the prov-o "syntax" and prov-o "constraints" portions. So we'll need to tackele "modules" anywayy. 16:20:12 q- 16:20:47 Luc: Agree with Paul for using single namespace for PROV-O 16:21:02 Luc: May be premature to re-organize the ontology 16:21:03 q+ to ask for clarity in namespaces among dm, prov-o, etc. 16:21:03 q? 16:21:11 +q 16:21:38 Tim: Is there a single approach for PROV-DM and PROV-O w.r.t. namespace 16:21:41 q+ 16:21:52 Luc: It is on the table for discussion 16:22:26 ack tle 16:22:26 tlebo, you wanted to ask for clarity in namespaces among dm, prov-o, etc. 16:22:26 Luc: Proposal to have namespace for different PROV resources (XML, OWL etc.) 16:22:53 +1 tracking it as an issue. 16:22:58 Paul: This should be raised as an issue 16:23:02 it's already a comment in prov-dm 16:23:14 @paul: sounds good as a reminder. 16:23:22 ack pg 16:23:29 I've pulled some notes on this last time I heard about it: http://www.w3.org/2011/prov/wiki/PROV-O_URI_namespace 16:24:23 ack sat 16:24:25 q? 16:24:39 Topic: Identifiers in Prov-dm 16:24:55 http://www.w3.org/2011/prov/wiki/ProvenanceOfW3CReport 16:25:30 http://www.w3.org/2011/prov/wiki/ProvenanceOfW3CReport#Discussion_about_Identifiers 16:25:46 Luc: Created an example to highlight problematic issues in DM w.r.t to identifiers 16:26:10 http://www.w3.org/2011/prov/wiki/ProposalsForIdentifiers 16:26:42 Luc: Agree on some of the issues related to identifiers - enumerated proposals 16:27:05 q? 16:27:12 q+ 16:27:26 ack sm 16:28:09 Simon: What has been proposed w.r.t common relations in DM, for example wasRevisionOf and usage events 16:28:13 +q 16:28:58 GK has joined #prov 16:29:07 Simon: For example, A is revisionOf B then identify generation of A? 16:29:26 + +44.789.470.aabb 16:29:32 q- 16:29:36 davidschaengold has joined #prov 16:29:45 q? 16:29:47 to respond to simon 16:29:51 Luc: Elicit feedback on example first 16:30:00 +??P41 16:30:02 q+ 16:30:12 zakim, ??p41 is me 16:30:12 +GK; got it 16:30:13 http://www.w3.org/2011/prov/wiki/ProposalsForIdentifiers 16:30:16 q- 16:30:22 q+ 16:30:41 q+ 16:31:38 satya: what happens if in account1 I make all the assertions in account2. What would be the relation between them? 16:32:19 entity(w3:WD-prov-dm-20111215, [ prov:type="html4" ]) 16:32:20 @Daniel: thanks Daniel! 16:32:28 @satya: np 16:32:31 http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication2.prov-asn 16:32:47 entity(w3:WD-prov-dm-20111215, [ prov:type="WD" ]) 16:32:52 stainPhone has joined #prov 16:32:53 http://dvcs.w3.org/hg/prov/raw-file/default/model/examples/w3cpub/w3c-publication1.prov-asn 16:33:15 entity(w3:WD-prov-dm-20111215, [ prov:type="WD", prov:type="html4" ]) 16:33:41 it's fine 16:33:49 nothing happens 16:34:11 Zakim, unmute me 16:34:11 MacTed should no longer be muted 16:34:16 q+ 16:34:23 @satya: no special action needed I guess 16:34:33 +q 16:35:02 ack sat 16:35:04 @satya: well, accounts can be redundant, right? 16:35:11 +1 to MacTed 16:35:49 q? 16:36:02 @satya that's still fine we don't draw any conclusion from comparing the content of two accounts 16:36:39 ack pgr 16:37:24 maybe we can get a summary 16:37:28 of the problem 16:37:33 MacTed: Misapprehension about the problem and the possible solution 16:37:36 -q 16:38:20 http://www.w3.org/2011/prov/wiki/ProvenanceOfW3CReport 16:38:52 q? 16:39:14 ack Mac 16:39:21 (It seems to me that the different accounts per http://www.w3.org/2011/prov/wiki/ProvenanceOfW3CReport correspond to differing epistemological positions) 16:39:30 @Luc I suggest that we move to the specific proposals 16:40:07 @GK: I agree 16:40:09 http://www.w3.org/2011/prov/wiki/ProposalsForIdentifiers 16:40:40 There is a requirement that *all* objects of discourse are identifiable and have an identifier. 16:42:25 q? 16:42:27 Luc: Identifiers seem to denote entities and at other places it identifies records 16:42:27 "have an identifier" -- better "have one or more identifiers" 16:42:28 q+ to ask if we need *all* elements in domain of discourse to be identified. E.g. In RDF we have blank nodes. 16:42:28 q+ 16:42:43 ack GK 16:42:43 GK, you wanted to ask if we need *all* elements in domain of discourse to be identified. E.g. In RDF we have blank nodes. 16:43:09 q+ 16:43:13 GK: Not all elements in domain of discourse may be identifiable 16:44:13 Luc: Current DM states that all entities have to be identifiable but may not have an identifier? 16:44:33 Luc: If there is no identifier, then how can they be referred to? 16:44:42 q+ identifiers may be context-specific, temporary, "that thing there"... 16:44:50 q+ to say identifiers may be context-specific, temporary, "that thing there"... 16:45:06 GK: Should identifiers in DM be same identifiers as in other serializations? 16:45:29 Also, I asked if "entity records" are *in* the domain of discourse 16:45:31 @GK: If they are blank node identifiers what is their state outside of the specific RDF document? 16:45:55 I agree that *accounts* are in the domain of discourse. Are these same as records? 16:46:00 generation event of entity is akwsys identifiable as long as the entity is 16:46:04 q? 16:46:07 Luc: Need to discuss the provenance of accounts, hence accounts are part of universe of discourse 16:46:19 (have to go) 16:47:00 once I have an Account, I have an AccountCreator -- tho the latter may be "unknown" in all senses other than "CreatedAccount" 16:47:06 entity(w3:WD-prov-dm-20111215, [ prov:type="WD" ]) 16:48:24 +q 16:49:05 ack sat 16:49:06 (Seems to me: an entity record (not in domain of discourse) introduces a name that denotes the described entity in domain of discourse. Unclear to me is whether this name is expected to carry though into any concrete representation (e.g. RDF)) I think this is what Luc is saying about proposal 1. 16:49:42 Simon: There are objects in domain of discourse that may not have identifiers? 16:49:53 q+ 16:49:57 q- 16:50:03 @Simon Sorry didn't get your example 16:50:32 "*All* objects of discourse MUST be identifiable, and MAY have one or more identifiers." 16:50:34 +q 16:50:49 @Mac: +1 16:50:49 +1 to MacTed 16:51:16 @satya: he said that if a wasRevisionOf b, then the activity that generated a (revisionActivity) could not be identified 16:51:19 - +44.789.470.aabb 16:51:25 (@simon: I think DM may require/introduce identifiers for things that are described by DM records, not necessarily for everything in domain of discourse) 16:51:35 +q to answer "yes" to Simon: necessary existence of an entity is not enough to know its identifier, clearly 16:51:36 @Daniel: thanks! :) 16:51:55 ack smil 16:52:25 @macted +1 16:52:27 MacTed: If something is identifiable does not mean they have an assigned identifier 16:52:29 @simon: so maybe in your example the activity is identifiable, but we may not know the identifier. 16:52:41 @MacTed +1 16:53:11 AndroUser2 has joined #prov 16:53:44 Luc: If there is no identifier then how are they referred 16:53:47 you give it one 16:53:52 q+ to answer luc: a record /introduces/ an identifier 16:53:57 @Mac, Paul: exactly +1 16:54:16 @simon: may have not been clear earlier: we do not know the id of entities that must exist (existential quantifier) but are not the object of any assertion, i.e., they remain implicit 16:54:17 @dgarijo OK, so under what you are suggesting, you mean that if we want to refer to the activity implied by a revisionOf relation, then we would introduce an identifier at that point? 16:54:44 q- 16:54:45 "*All* objects of discourse MUST be identifiable, and MAY have one or more identifiers. For purposes of discourse, an identifier SHOULD be assigned to the object of discourse." ? 16:55:01 "There is a requirement that *all* objects of discourse are identifiable, and that entity records use or introduce an identifer for the objects described" 16:55:04 @MacTed good start 16:55:18 @smiles: I guess so. You can invent one. 16:55:52 yea! 16:55:53 q? 16:55:55 +1 to Graham 16:56:03 +1 @gk 16:56:04 @GK: +1 16:56:05 @macted - yes 16:56:17 @GK only entity records? how about activities etc. 16:56:53 @paolo ack. 16:56:58 @Paolo: that a nice point: do we have an "alternateOf" for activities? 16:57:10 MacTed: Implied objects may not have identifiers 16:57:16 There is a requirement that *all* objects of discourse are identifiable, and that entity records use a new identfier or introduce an existing identifer for the objects described 16:57:18 + "Implied entioties need not have an assigned idnetifier." 16:58:10 q? 16:58:10 ? 16:58:15 ack Ma 16:58:15 MacTed, you wanted to say identifiers may be context-specific, temporary, "that thing there"... 16:58:19 q- 16:58:30 ack Pao 16:58:30 Paolo, you wanted to answer "yes" to Simon: necessary existence of an entity is not enough to know its identifier, clearly 16:58:43 There is a requirement that *all* objects of discourse are identifiable, and that entity records use a new identfier or introduce an existing identifer for the objects described 16:58:52 q+ 16:58:53 "use a new identfier or introduce an existing identifer" --> "introduce a new identifier or reuse an existing identifer" 16:59:07 @daniel: possibly, but this ID issue is not brought in "just" for alternateOf, rather it's a general principle that we decide to adopt 16:59:48 There is a requirement that *all* objects of discourse are identifiable, and that entity records introduce a new identifier or reuse an existing identifier for the objects described. 16:59:53 There is a requirement that *all* objects of discourse are identifiable, and that entity records reuse an existing identifier or introduce a new identifier for the objects described 17:00:03 q+ 17:00:10 "provenace records" 17:00:17 There is a requirement that *all* objects of discourse are identifiable, and that records reuse an existing identifier or introduce a new identifier for the objects described 17:00:19 +q 17:00:20 q? 17:00:21 @Tim, +1 17:00:22 q? 17:00:32 ack sat 17:00:48 "*All* objects of discourse MUST be identifiable. Object descriptions MUST use an identifier (either reusing an existing identifier, or introducing a new identifier) for the objects described." 17:01:00 q- 17:01:03 Paolo: Any object should be subject to the identifier rule 17:01:04 ack pgr 17:01:07 (maybe change the second MUST to SHOULD) 17:01:43 (yes, I'm deliberately removing extraneous "there is a requirement that" wording from the text.) 17:01:44 q+ to note we haven't said anything about the nature of these identifiers. Thisis OK, but we haven't licensed any further assumptions yet. 17:01:50 Paul: Concerned that implicit elements may have identifiers and proposal 1 does not cover that? 17:01:54 Agreed with Luc - as long as record is explicit, it is fine 17:01:56 q? 17:02:05 +1 to including RFC2119 (like MacTed's) 17:02:28 q? 17:02:30 ack gk 17:02:30 GK, you wanted to note we haven't said anything about the nature of these identifiers. Thisis OK, but we haven't licensed any further assumptions yet. 17:02:36 There is a requirement that *all* objects of discourse are identifiable, and that records reuse an existing identifier or introduce a new identifier for the objects described 17:02:46 GK: Concerned that it does not lead to additional entailments from this proposal? 17:02:50 +1 17:02:52 +1 17:02:53 +1 17:02:54 PROPOSAL: There is a requirement that *all* objects of discourse are identifiable, and that records reuse an existing identifier or introduce a new identifier for the objects described 17:02:57 I need a clear PROPOSAL to vote on... 17:02:57 +1 17:03:02 +1 17:03:02 +1 17:03:03 -1 17:03:03 +1 17:03:04 -1 should include RFC2119 terms 17:03:13 the language semms deliberately obscuring 17:03:15 +1, although I liked more MacTed's 17:03:23 +1 17:03:46 (agreed -- this is not the final wording, just the idea.) 17:03:48 +1 for intent (please add RFC2119 like MacTed's) 17:03:56 +1 17:04:00 so the vote is on the "general principle" only? 17:04:25 @macted - I think the intent is same as what you said: "*All* objects of discourse MUST be identifiable.  Object descriptions MUST use an identifier (either reusing an existing identifier, or introducing a new identifier) for the objects described." 17:04:39 PROPOSAL: "*All* objects of discourse MUST be identifiable.  Object descriptions MUST use an identifier (either reusing an existing identifier, or introducing a new identifier) for the objects described." 17:04:51 +1 17:05:51 I thought we were voting for the final version of the proposal? 17:06:00 sandro: I don't think RFC 2119 language works unless it's clear who/what is constrained to follow it. 17:06:00 q+ 17:06:01 +1 to acknowledging these two have the intent and moving on. 17:06:33 Paolo: Is the current formulation reconciling record and entity? 17:06:49 whatever you want 17:06:55 Paolo: Which identifier needs to be re-used? 17:06:57 @Paolo: whatever you want 17:07:14 q? 17:07:14 @paolo - choosing to reuse an identifeir is up to the asserter based on its properties. 17:07:43 @paolo whatever you want 17:07:45 Paolo: What criteria is used to choose to re-use an identifier? 17:07:49 q? 17:07:50 +q 17:07:52 ack pao 17:08:02 @paolo - choosing to reuse an identifeir is up to the asserter based on its properties. 17:08:14 ack kh 17:08:23 PROPOSAL: "*All* objects of discourse ("entities") MUST be identifiable by all participants in discourse.  Object descriptions ("entity records" and otherwise) SHOULD use an unambiguous identifier (either reusing an existing identifier, or introducing a new identifier) for the objects described." 17:08:29 alternateOf! 17:08:38 The point is, I think, when the intent of assertion is to refer to something already described, to re-use the identifier already used. This is how names work, no? 17:08:40 (not complementOf) 17:08:59 @GK, "GK, who?" ;-) 17:09:03 Khalid: Should use same identifier for same entity? 17:09:15 q? 17:09:16 @tlebo makes sense, in principle 17:09:19 @tlebo the same GK as referred to previously :) 17:09:23 if you know someone used a name for the thing (and what that name is), then sure, you might choose to reuse their naming. what if you don't know they did, nor what name they chose 17:09:29 ? 17:09:36 Khalid: Not including a criteria for re-using identifier is fine 17:09:41 q? 17:09:53 PROPOSAL: "*All* objects of discourse ("entities") MUST be identifiable by all participants in discourse. Object descriptions ("entity records" and otherwise) SHOULD use an unambiguous identifier (either reusing an existing identifier, or introducing a new identifier) for the objects described." 17:09:56 +1 17:10:04 +1 17:10:05 q+ 17:10:05 +1 17:10:11 +1 17:10:14 +1 (for intent) 17:10:16 +1 17:10:20 +1 17:10:29 +1 to intent, just like Luc's 17:10:35 satya: is object description just an example? 17:10:38 +1 17:10:44 +1 17:10:48 s/"entity records" and otherwise/e.g., "entity records" and otherwise/ 17:10:48 +1 17:11:03 ACCEPTED: "*All* objects of discourse ("entities") MUST be identifiable by all participants in discourse. Object descriptions ("entity records" and otherwise) SHOULD use an unambiguous identifier (either reusing an existing identifier, or introducing a new identifier) for the objects described." (intent) 17:12:20 PROPOSAL: Generation and Usage events also belong to the universe of discourse. So they should be given identifiers (as per proposal 1) 17:12:29 q+ 17:12:44 q? 17:12:57 This is in line with the current formal semantics. 17:13:12 q? 17:13:15 ack saty 17:13:32 I agree, it seems a natural consequence of proposal 1 17:13:36 q+ 17:13:39 @smiles +1 17:14:39 the only problem I see is the identifiers that would be given in 2 accounts that are describing the same process with different identifiers. 17:14:45 I think there are two remaining areas for discussion: (a) what are the objects in the domain of discourse, and (b) what identifiers may be used in DM and how to the relate to, e.g., URIs used in RDF. 17:15:00 @GK - Nice point 17:15:23 @dgarijo Isn't that just an unavoidable problem for anything identifiable? 17:15:27 @dgarijo, what is wrong with "identifiers that would be given in 2 accounts that are describing the same process with different identifiers." ? 17:15:51 I think that "objects in the domain of discourse" actually include Events (Generation, Usage, and otherwise), Derivations, Notes, and otherwise 17:15:55 how would I say that both activities are the same? owl:sameAs? 17:16:01 q? 17:16:05 q- 17:16:07 ack satya 17:16:10 prov:alternativeOf or owl:sameAs 17:16:11 @MacTed - I think so too. 17:16:16 q? 17:16:19 alternativeof is for entities ;) 17:16:22 -tlebo 17:16:23 -sandro 17:16:25 - +1.518.633.aaaa 17:16:26 2 accounts using 2 identifiers for the same entity is an implementation issue -- i.e., someone needs a Reasoning Engine 17:16:27 -dgarijo 17:16:29 -khalidbelhajjame 17:16:31 -Satya_Sahoo 17:16:32 -MacTed 17:16:32 -jcheney 17:16:33 -Paolo 17:16:34 -AlexHall 17:16:36 -??P6 17:16:38 -Luc 17:16:40 -pgroth 17:16:43 to handle the owl:sameAs (or other) relationships 17:16:49 -??P18 17:16:57 -GK 17:16:57 SW_(PROV)11:00AM has ended 17:16:59 Attendees were pgroth, Paolo, Luc, Satya_Sahoo, AlexHall, tlebo, dgarijo, sandro, jcheney, MacTed, +1.518.633.aaaa, khalidbelhajjame, +44.789.470.aabb, GK 17:17:00 rrsagent, set log public 17:17:04 rrsagent, draft minutes 17:17:04 I have made the request to generate http://www.w3.org/2012/01/19-prov-minutes.html Luc 17:17:10 trackbot, end telcon 17:17:10 Sorry, Luc, I don't understand 'trackbot, end telcon '. Please refer to http://www.w3.org/2005/06/tracker/irc for help 17:17:51 @MacTed re need for reasonber... 17:17:53 a la, "Bush:43" owl:sameAs "George Walker Bush" owl:sameAs "Dubya" owl:sameAs "Shrub" 17:19:03 ... I think that depends on how identifiers relate. E.g., originally, IIRC, DM said (e.g.) entity identifiers were scoped to account. 17:19:56 all the more so, then -- as you then need to handle { Account1:"Bush:43" owl:sameAs Account2:"Bush:43" } 17:20:28 if that's true in DM, we may want to specify generation of different URIs or nodes in mapping to RDF. But for other mappings to non-URI names, maybe not so. 17:21:11 If what you mean is that when different names are used for the same thing, then a reasoner is needed to detect and apply this knowledge, then yes. (For some value of "reasoner") 17:21:13 the smaller the defined scope for a given identifier, the more important that equivalence (or other relation) can be handled 17:22:32 Yes... but this isn't a provenance-specific issue, except to the extent that provenance DM shooses to use scoping when the same thing may be referenced in different accounts? 17:25:06 absolutely true -- not provenance-specific issue. but entirely relevant and definitely present, and I think it *may* be best-addressed (or at least, most obvious and possibly most clearly definable) in the context of provenance. 19:20:10 Zakim has left #prov