17:54:32 RRSAgent has joined #owl 17:54:32 logging to http://www.w3.org/2009/01/21-owl-irc 17:54:39 rrsagent, make log public 17:54:54 Zhe has joined #owl 17:56:26 SW_OWL()1:00PM has now started 17:56:33 +baojie 17:57:13 bijan has joined #owl 17:57:54 MarkusK_ has joined #owl 17:58:00 bcuencag has joined #owl 17:58:47 +??P13 17:58:48 schneid has joined #owl 17:58:54 Zakim, ??P13 is me 17:58:54 +bcuencag; got it 17:59:01 +??P14 17:59:03 alanr has joined #owl 17:59:13 zakim, ??P14 is me 17:59:13 +schneid; got it 17:59:17 zakim, mute me 17:59:17 schneid should now be muted 17:59:31 +??P18 17:59:48 +Peter_Patel-Schneider 17:59:48 i will dial in shortly. 17:59:48 uli has joined #owl 18:00:04 pfps has joined #owl 18:00:19 +??P24 18:00:31 zakim, I am ??p24 18:00:31 +bijan; got it 18:00:32 +??P26 18:00:35 Zakim, ??P26 is me 18:00:35 +bmotik; got it 18:00:36 zakim, mute me 18:00:37 bijan should now be muted 18:00:38 Zakim, mute me 18:00:38 bmotik should now be muted 18:00:41 Zakim, who is on the phone 18:00:41 I don't understand 'who is on the phone', Jie 18:00:58 ivan has joined #owl 18:01:12 Zakim, who is here 18:01:12 Jie, you need to end that query with '?' 18:01:15 Zakim, who is here? 18:01:15 On the phone I see baojie, bcuencag, schneid (muted), MarkusK_, Peter_Patel-Schneider, bijan (muted), bmotik (muted) 18:01:17 On IRC I see ivan, pfps, uli, alanr, schneid, bcuencag, MarkusK_, bijan, Zhe, RRSAgent, Zakim, bmotik, Jie, sandro, trackbot 18:01:21 Zakim, mute me 18:01:21 bcuencag should now be muted 18:01:31 zakim, dial ivan-voip 18:01:31 ok, ivan; the call is being made 18:01:33 +Ivan 18:01:40 +??P27 18:01:48 zakim, ??P27 is me 18:01:48 +uli; got it 18:01:48 zakim, who is on the phone'?' 18:01:49 I don't understand 'who is on the phone'?'', pfps 18:02:08 zakim, who is here? 18:02:19 +Alan 18:02:28 On the phone I see baojie, bcuencag (muted), schneid (muted), MarkusK_, Peter_Patel-Schneider, bijan (muted), bmotik (muted), Ivan, uli, Alan 18:02:35 On IRC I see ivan, pfps, uli, alanr, schneid, bcuencag, MarkusK_, bijan, Zhe, RRSAgent, Zakim, bmotik, Jie, sandro, trackbot 18:02:47 alanr has changed the topic to: http://www.w3.org/2007/OWL/wiki/Teleconference.2009.01.21/Agenda 18:03:43 msmith has joined #owl 18:04:02 +msmith 18:04:11 +Sandro 18:05:16 zakim, who is here? 18:05:16 On the phone I see baojie, bcuencag (muted), schneid (muted), MarkusK_, Peter_Patel-Schneider, bijan (muted), bmotik (muted), Ivan, uli, Alan, msmith, Sandro 18:05:19 On IRC I see msmith, ivan, pfps, uli, alanr, schneid, bcuencag, MarkusK_, bijan, Zhe, RRSAgent, Zakim, bmotik, Jie, sandro, trackbot 18:05:41 how to assign me to scribe? 18:05:42 Achille has joined #owl 18:06:05 scribe: jie 18:06:18 http://www.w3.org/2007/OWL/meeting/2009-01-14 18:06:20 Preious minutes 18:06:23 I have 18:06:25 +[IBM] 18:06:27 I have a problem 18:06:34 Zakim, IBM is me 18:06:34 +Achille; got it 18:06:41 zakim, unmute me 18:06:41 bijan should no longer be muted 18:06:47 Christine Golbreich: we should vote now becasue last time we postponed it because bijan was not there 18:07:23 q+ 18:07:26 q+ 18:07:26 Bijan: problem on vote on Manchester Sytnax as a note 18:07:42 Bijan: it is not time critical to determine this issue 18:08:01 Bijan: I suggest to postspond it 18:08:23 q- 18:08:38 alan: What Christine meant, I think, is that we had postponed it for only one week. So we postponed because Bijan wasn't there, but we only postponed for one week. 18:08:44 ack Achille 18:09:07 yes, my recollection matches achille's 18:09:10 +1 to Achille, that is what Christine tried to express 18:09:19 achille: I was scribe. Christine wanted to vote then because she didn't want it postponed again and again. 18:09:19 s/postspond/postpone 18:09:20 I agree with Achille's memory of this 18:09:29 zakim, mute me 18:09:29 bijan should now be muted 18:09:53 Alan: we will do it next week 18:10:03 s/postpone/postponed 18:10:36 alan: let's not approve the minutes yet, given no one expressing an opinion, other than this issue about what Christine said. 18:10:41 Topic: Actions 18:11:06 q+ 18:11:14 ack pfps 18:11:25 Asction 247 18:11:46 Alan: don't have time to do it, will try to finish next week 18:11:48 q- 18:12:17 ADD YOURSELF TO http://www.w3.org/2007/OWL/wiki/F2F5_People 18:12:18 pfps: several documents depend on the Manchester syntax, so there soon needs to be a final determination of what is going on here 18:12:23 Topic Reivews of LC documents 18:12:31 Alan: we don't have many 18:12:40 topic: F2F5 18:13:05 I'm not sure we need it 18:13:23 I don't need much (if any) lead time to be there. 18:13:42 zakim, unmute me 18:13:42 bijan should no longer be muted 18:14:06 Bijan: i'm not sure if we need it 18:14:21 it is an expensive trip also 18:14:48 hopefully we will be able to get good facilities for remote participation 18:14:48 q+ agenda topics 18:15:02 Bijan: unless we have major changes 18:15:03 zakim, mute me 18:15:03 bijan should now be muted 18:15:20 Tests are easy to do offline 18:15:21 Sandro: we have big test cases to go through 18:15:35 I definitely wouldn't go to a f2f in the States to do tests :) 18:15:39 if nothing else, we can have two days to get the tests done 18:15:42 :-) 18:15:45 How about a vote mechanism in the wiki for the tests 18:16:12 the thing on tests is getting people to spend the time on them. 18:16:19 Alan: let decide about F2F5 next week 18:16:25 topic: Last Call comments 18:16:57 http://www.w3.org/2007/OWL/wiki/Responses_to_Last_Call_Comments 18:17:10 Alan: let's go through the comments page 18:17:17 q+ 18:17:20 q+ 18:17:27 Comment 1: Alan Rector 18:17:27 ack pfps 18:17:38 Peter: I'm worried about it 18:17:53 q+ 18:17:55 It includes changes to the spec that is not operational yet 18:18:39 http://www.w3.org/2007/OWL/wiki/LC_Responses/ALR1 18:18:42 +1 don't say we're changing the spec until the change is fully done. 18:19:34 +Zhe 18:19:41 zakim, mute me 18:19:41 Zhe should now be muted 18:19:43 q? 18:19:45 Peter: if there are changes there, we need somehow track it 18:19:55 zakim, unmute me 18:19:55 bijan should no longer be muted 18:21:10 Bijan: do you want us to do with this page? 18:21:24 Zakim, who is talking? 18:21:34 bmotik, listening for 10 seconds I heard sound from the following: uli (41%), Alan (89%) 18:21:52 Peter: if anybody make proposal to change, he/she have to make the change trackable 18:22:00 s/have/has 18:22:08 Peter: voteable 18:22:37 Peter: the WG has to vote for a change 18:22:55 zakim, mute me 18:22:55 uli should now be muted 18:23:52 q? 18:23:58 agenda- 18:24:07 q=schneid 18:24:08 Bijan: I think we should reject 18:24:12 queue=schneid 18:24:57 q+ 18:25:43 the workaround is sufficient 18:25:49 zakim, unmute me 18:25:49 schneid should no longer be muted 18:25:49 ack schneid 18:25:50 zakim, mute me 18:25:51 bijan should now be muted 18:26:20 Mschneid: No change 18:26:47 no need to introduce a new language feature 18:26:49 One could even annotate the naming axiom saying "this is for annotation purposes, not modeling" 18:26:50 q+ to ask whether named class workaround has performance impact 18:26:58 ack uli 18:26:59 zakim, unmute me 18:27:00 zakim, mute me 18:27:00 uli was not muted, uli 18:27:01 schneid should now be muted 18:27:13 Uli: I chatted with Alan Rector 18:27:39 q- 18:27:40 If the change doesn't address his use cases, we should reject it 18:28:02 zakim, mute me 18:28:02 uli should now be muted 18:28:38 Alan: then we should respond there is workaround to this issue 18:29:05 schneid: I would keep things as they are, since naming class expressions is possible anyway, and can be used. Maybe we put an informative note in our spec to inform people about the nameing "trick" 18:29:09 I had a chat with Alan Rector and he seemed to be willing to accept that his proposed change would only help him to make work-arounds, but not really provide a solution. As a consequence, he indicated that he wouldn't insist on this change 18:29:25 ? 18:29:28 PROPOSED: Respond to ALR1 on the basis of Ian suggestions for using named classes as a workaround 18:29:34 q+ 18:29:56 ack pfps 18:30:20 PROPOSED: Respond to ALR1 on the basis of the suggestions for workarounds 18:30:29 ok 18:30:37 +1 18:30:39 +1 18:30:40 +1 18:30:41 +1 18:30:41 +1 18:30:42 +1 18:30:43 +1 18:30:43 +1 18:30:44 +1 18:30:45 +1 18:30:46 +! 18:30:49 +1 18:30:55 +1 18:30:59 +1 18:31:04 RESOLVED: Respond to ALR1 on the basis of Ian suggestions for using named classes as a workaround 18:31:12 I'm writing one right now 18:31:25 on the page 18:31:27 Already 18:31:52 not saved yet :) 18:32:00 Topic: comment COLI 18:32:05 Action: Bijan to draft response to ALR1 18:32:05 Created ACTION-265 - Draft response to ALR1 [on Bijan Parsia - due 2009-01-28]. 18:32:15 s/COLI/COL1 18:32:18 q? 18:32:28 http://www.w3.org/2007/OWL/wiki/LC_Responses/MS1 18:32:53 q+ 18:32:58 ack pfps 18:34:00 action: pfps to provide fix to MS1 in RDF Mapping and put diff on http://www.w3.org/2007/OWL/wiki/LC_Responses/MS1. 18:34:00 Created ACTION-266 - Provide fix to MS1 in RDF Mapping and put diff on http://www.w3.org/2007/OWL/wiki/LC_Responses/MS1. [on Peter Patel-Schneider - due 2009-01-28]. 18:34:03 process is then to change the document and put a diff into the reponse page (along with rationale, I guess) 18:34:20 q+ 18:34:23 ack pfps 18:35:01 PROPOSED: Peter will propose fix for MS1 in the form of edits to the RDF Mapping Document 18:35:02 Peter: we need to vote on it, if I gonna to work on it 18:35:06 +1 18:35:10 +1 18:35:11 +1 18:35:11 +1 18:35:11 +1 18:35:12 +1 18:35:13 +1 18:35:14 0 18:35:18 +1 18:35:19 +1 18:35:21 +! 18:35:22 +1 18:35:23 +1 18:35:26 RESOLVED: Peter will propose fix for MS1 in the form of edits to the RDF Mapping Document 18:35:28 +1 18:35:45 Topic: MD1 18:35:52 http://www.w3.org/2007/OWL/wiki/LC_Responses/MD1 18:36:24 lost my connection 18:36:24 Alan: anybody knows the difference between Unicode 3.0/5.0? 18:36:26 back in a sec 18:36:37 Lots and lots of characters 18:36:40 Was there a response from Martin? 18:36:43 q+ 18:36:49 zakim, unmute me 18:36:49 schneid should no longer be muted 18:37:18 No 18:37:22 Mschneid: I wonder if it is necessary to have Unicode version mentioned 18:37:23 q? 18:37:30 q- 18:37:33 zakim, mute me 18:37:33 schneid should now be muted 18:37:45 I guess it should be latest version, otherwise we will have 18:37:45 some people wondering whether they can use the latest characters. 18:37:45 For more details, please see http://www.w3.org/TR/charmod/#sec-RefUnicode. 18:37:50 Sandro: I talked with Martin Duerst 18:38:02 schneid: wonders whether it would be allowed to generically refer to the "latest Unicode version" 18:38:19 Alan: we need somebody to read this 18:38:19 q+ to respond to michael about a specific version 18:38:24 I'm finished my Alan Rector action 18:38:24 ack msmith 18:38:24 msmith, you wanted to respond to michael about a specific version 18:38:30 (I was quoting from private e-mail from Martin Duerst there) 18:38:54 q+ 18:39:08 Zakim, unmute me 18:39:08 bmotik should no longer be muted 18:39:08 ack bmotik 18:39:10 q? 18:39:11 Msmith: we need address a specific version of Unicode for datatype implementation 18:39:37 Boris: one problem is whether the set of character is infinite 18:40:11 if the number of characters in Unicode changes across versions 18:40:46 it is possible one consistent ontology to be inconsistent when using a different version of Unicode 18:40:52 q+ 18:40:53 ok, it seems I remembered it incompletely then. thanks for clarifying boris. 18:41:32 hey, we have a new testcase :) 18:42:13 ack bijan 18:42:19 zakim, unmute me 18:42:19 bijan was not muted, bijan 18:42:22 Zakim, mute me 18:42:22 bmotik should now be muted 18:42:40 but referring to the "latest version" will also refer to a finite alphabet (at every time) 18:42:43 Bijan: two places we deal with Unicode 18:42:48 yes 18:42:52 Datatype, and syntax 18:43:03 IRIs refer also to Unicode, right? 18:43:36 in the syntax, if we don't address unicode version, there may be gap between functional syntax and other syntaxes 18:44:19 e.g. XML only allow certain versions of Unicode 18:44:25 q+ 18:44:26 s/allow/allows 18:44:28 ack ivan 18:45:12 q+ 18:45:13 Ivan: Martin's question is what version we use, and he suggest 5.0 18:45:26 ack bijan 18:45:32 We just need to respond we use the lastest version 18:46:07 Bijian: XML is tied to Unicode 3 18:46:45 q? 18:46:53 [[[C064 [S] All generic references to the Unicode Standard [Unicode] must refer to the latest version of the Unicode Standard available at the date of publication of the containing specification.]]] 18:46:59 Sandro: is it the lastest version now, or lastest version ever? 18:47:30 q+ to ask why not make is finite but 2^32 18:49:12 alan: we need list on the page the points we need address 18:49:40 ... Bijan, Boris, Sandro 18:50:16 working on it 18:50:39 Er..dunno 18:50:41 Zakim, unmute me 18:50:41 bmotik should no longer be muted 18:50:43 q+ 18:50:45 I'll write and see what happens ;) 18:50:50 ack alanr 18:50:50 alanr, you wanted to ask why not make is finite but 2^32 18:50:57 ack bmotik 18:51:12 zakim, unmute me 18:51:12 bijan was not muted, bijan 18:51:18 ACTION: Bijan to write about unicode versioning issue 18:51:18 Created ACTION-267 - Write about unicode versioning issue [on Bijan Parsia - due 2009-01-28]. 18:51:27 q+ 18:51:36 Boris: after read the note, I agree that the infinite supply of characters is not relevent 18:51:47 q+ 18:52:02 q+ 18:52:03 -q 18:52:10 ack ivan 18:52:17 s/relevent/relevant 18:52:37 I've got it, ivan 18:52:41 ack Bijan 18:53:03 Zakim, mute me 18:53:03 bmotik should now be muted 18:53:04 zakim, mute me 18:53:04 bijan should now be muted 18:53:11 http://www.w3.org/2007/OWL/wiki/LC_Responses/JH1 18:53:13 next: JH1 18:53:34 zakim, mute me 18:53:34 bijan was already muted, bijan 18:53:35 Alan: it is about better documentation of key 18:53:49 zakim, unmute me 18:53:49 bijan should no longer be muted 18:53:50 ... Syntax editors 18:53:54 q? 18:54:28 Zakim, unmute me 18:54:28 bmotik should no longer be muted 18:54:29 q+ 18:54:32 Bijan: Jim is over-stating. I'm not know if to put it into Syntax 18:54:35 ack bmotik 18:54:37 ... maybe rationale 18:54:39 q+ 18:54:45 ack bijan 18:54:52 Boris: I don't understand the problem of this comment 18:54:59 they didn't grok the feature 18:55:27 Bijan: The problem is that they assume key is golbal 18:55:34 q? 18:55:36 ...but they have been now convinced, haven't they? 18:55:47 s/golbal/global 18:55:50 yes, they want some documentation so someone else doesn't make the same mistake 18:56:27 zakim, mute me 18:56:27 bijan should now be muted 18:56:32 q+ 18:56:37 ack ivan 18:56:46 I'd prefer new features and rationale 18:56:50 Alan: maybe document is in Primer or Rationale 18:56:59 Zakim, mute me 18:56:59 bmotik should now be muted 18:57:10 +1 to Ivan, this is the document meant to be read if one wants to know about the new features 18:57:20 a simple "please note that "keyfor(C P)" only concerns instances of C, not everything 18:57:35 editors of that doc? 18:57:46 PROPOSED: Respond to JH1 by adding documentation in F&R and then sending that documentation in the response. 18:57:50 +1 18:57:52 s/is/it 18:57:54 +1 18:57:57 +1 18:57:58 +1 18:57:59 +1 18:58:00 +1 18:58:00 +1 18:58:02 +1 18:58:02 +1 18:58:02 0 18:58:03 +1 18:58:10 RESOLVED: Respond to JH1 by adding documentation in F&R and then sending that documentation in the response 18:58:11 +1 18:58:11 +0 (neither christine or evan is here) 18:58:15 Rereading the syntax, I can see how o ne *might* find "A key axiom of the form HasKey( owl:Thing OPE ) is similar to the axiom InverseFunctionalProperty( OPE ); the main difference is that the first axiom is applicable only to individuals that are explicitly named in an ontology, while the second axiom is also applicable to individuals whose existence is implied by existential quantification. The structure of such axiom is shown in Figure 17." 18:58:17 a bit misleading 18:58:23 I can add a bit of clarificatory text 18:58:32 zakim, unmute me 18:58:32 bijan should no longer be muted 18:59:23 Bijan: I can add a single sentence in Syntax 19:00:11 PROPOSED: also address JH1 by Bijan adding a clarificatory sentence to the syntax specification and passing that on in the response. 19:00:13 I'd add this sentence in the example that Jim identified. 19:00:25 +1 19:00:26 +1 19:00:27 +1 19:00:29 +1 19:00:31 +1 19:00:34 +1 19:00:34 +1 19:00:37 +1 19:00:38 +1 19:00:38 +1 19:00:40 +1 19:00:41 +1 19:00:43 +1 19:00:45 RESOLVED: also address JH1 by Bijan adding a clarificatory sentence to the syntax specification and passing that on in the response 19:01:18