17:36:01 RRSAgent has joined #owl 17:36:01 logging to http://www.w3.org/2009/01/28-owl-irc 17:36:13 Zakim, this will be owlwg 17:36:13 ok, MartinD; I see SW_OWL()1:00PM scheduled to start in 24 minutes 17:36:42 RRSagent, make records public 17:52:44 bijan has joined #owl 17:52:53 baojie has joined #owl 17:53:16 Zhe has joined #owl 17:54:20 SW_OWL()1:00PM has now started 17:54:27 +??P0 17:54:33 zakim, ??p0 is me 17:54:33 +bijan; got it 17:54:55 + +0190827aaaa 17:54:58 -bijan 17:54:59 +bijan 17:55:05 zakim, aaaa is me 17:55:05 +MartinD; got it 17:55:15 zakim, mute me 17:55:15 MartinD should now be muted 17:55:20 zakim, mute me 17:55:20 bijan should now be muted 17:55:58 ratnesh has joined #owl 17:58:13 bcuencag has joined #owl 17:58:23 Achille has joined #owl 17:59:04 + +1.914.421.aabb 17:59:24 Zakim, aabb is me 17:59:25 + +86528aacc 17:59:25 +Achille; got it 17:59:39 Zakim, mute me 17:59:39 Achille should now be muted 17:59:48 +IanH 17:59:56 ewallace has joined #owl 18:00:00 zakim, who is here? 18:00:00 On the phone I see bijan (muted), MartinD (muted), Achille (muted), +86528aacc, IanH 18:00:02 On IRC I see ewallace, Achille, bcuencag, ratnesh, Zhe, baojie, bijan, RRSAgent, Zakim, MartinD, IanH, sandro, trackbot 18:00:21 - +86528aacc 18:00:30 +Evan_Wallace 18:00:30 bmotik has joined #owl 18:00:43 ScribeNick: MartinD 18:00:54 +??P5 18:00:55 Martin, are you ready to scribe? 18:01:02 + +0186528aadd 18:01:05 yep... 18:01:06 +pfps 18:01:13 Good -- thanks! 18:01:15 Zakim, ++0186528aadd is me 18:01:15 sorry, bmotik, I do not recognize a party named '++0186528aadd' 18:01:19 zakim, ??P5 is me 18:01:19 +ratnesh; got it 18:01:20 Zakim, +0186528aadd is me 18:01:20 +bmotik; got it 18:01:23 zakim, who is here? 18:01:23 On the phone I see bijan (muted), MartinD (muted), Achille (muted), IanH, Evan_Wallace, ratnesh, bmotik, pfps 18:01:25 On IRC I see bmotik, ewallace, Achille, bcuencag, ratnesh, Zhe, baojie, bijan, RRSAgent, Zakim, MartinD, IanH, sandro, trackbot 18:01:26 Zakim, mute me 18:01:27 +baojie 18:01:27 bmotik should now be muted 18:01:39 +bmotik.a 18:01:54 Topic: Admin matters 18:02:09 zakim, who is here? 18:02:09 On the phone I see bijan (muted), MartinD (muted), Achille (muted), IanH, Evan_Wallace, ratnesh, bmotik (muted), pfps, baojie, bmotik.a 18:02:12 On IRC I see bmotik, ewallace, Achille, bcuencag, ratnesh, Zhe, baojie, bijan, RRSAgent, Zakim, MartinD, IanH, sandro, trackbot 18:02:16 msmith will be a bit late 18:02:16 pfps has joined #owl 18:02:19 Zakim, mute me 18:02:19 sorry, bcuencag, I do not know which phone connection belongs to you 18:02:21 q+ 18:02:23 Ian: checking who's here; any agenda ammendments? 18:02:28 q? 18:02:33 ack pfps 18:02:35 -bmotik.a 18:02:39 +Zhe 18:02:48 zakim, mute me 18:02:49 Zhe should now be muted 18:02:59 Peter: agenda was messed up - e.g., the minute approval for 14 instead of 21 January 18:03:09 +bmotik.a 18:03:22 Ian: extra item needed -- approving both sets of minutes (14 Jan, 21 Jan) 18:03:26 My actions aren't on 18:03:28 schneid has joined #owl 18:03:29 q? 18:03:30 Peter: action status has also changed 18:03:33 +Sandro 18:03:38 q? 18:03:46 q+ 18:03:57 Ian: let's look at the agenda from 14 Jan 18:04:01 Can we we resolve my pending review actions? 18:04:09 +??P15 18:04:10 +??P14 18:04:11 q? 18:04:16 zakim, unmute me 18:04:16 bijan should no longer be muted 18:04:17 q+ 18:04:20 ack bijan 18:04:25 ivan has joined #owl 18:04:28 ...there was a problem with incorrect records, which needed fixing 18:04:30 christine has joined #owl 18:04:30 Zakim, ??P15 is me 18:04:30 +bcuencag; got it 18:04:31 zakim, ??P15 is me 18:04:32 I already had ??P15 as bcuencag, schneid 18:04:37 zakim, dial ivan-voip 18:04:37 ok, ivan; the call is being made 18:04:38 zakim, ??P14 is me 18:04:39 +schneid; got it 18:04:39 +Ivan 18:04:44 Zakim, mute me 18:04:44 bcuencag should now be muted 18:04:50 zakim, mute me 18:04:50 schneid should now be muted 18:04:56 zakim, mute me 18:04:56 bijan should now be muted 18:04:56 Bijan: is it correct, there is only one item under pending review? 18:05:00 yes 18:05:05 q? 18:05:11 Zakim, unmute me 18:05:11 Achille should no longer be muted 18:05:15 ack Achille 18:05:36 thanks 18:05:52 zakim, mute me 18:05:52 bijan was already muted, bijan 18:05:55 Achille: I just send an email about the issues/concerns raised in those minutes from 14 Jan 18:05:58 zakim, unmute me 18:05:58 bijan should no longer be muted 18:06:03 q? 18:06:15 Bijan: changes look fine 18:06:40 zakim, mute me 18:06:40 bijan should now be muted 18:06:46 Zakim, mute me 18:06:46 Achille should now be muted 18:06:47 14 jan acceptable 18:07:00 PROPOSED: Accept minutes from 14 January (http://www.w3.org/2007/OWL/meeting/2009-01-14) 18:07:11 12 jan minutes minimally acceptable ... 18:07:14 RESOLVED: Accept minutes from 14 January (http://www.w3.org/2007/OWL/meeting/2009-01-14_ 18:07:16 They looked good to me. 18:07:28 21 jan MINIMALLY acceptable ... 18:07:41 one thing that scribes should do is reorder headings to get things in the right place 18:07:56 Ian: from people's opinion it looks 21 Jan is also acceptable, although minimally 18:08:05 but I'm not going to hold up this time, as the intent can be deciphered 18:08:10 ...any more work needs to be done by scribe? 18:08:23 ... let's accept the other ones too 18:08:37 PROPOSED: Accept minutes from 21 January (http://www.w3.org/2007/OWL/meeting/2009-01-21) 18:08:46 RESOLVED: Accept minutes from 21 January (http://www.w3.org/2007/OWL/meeting/2009-01-21) 18:08:55 Topic: Action items status 18:08:55 http://www.w3.org/2007/OWL/tracker/actions/pendingreview 18:09:16 Ian: we have several actions from Bijan, most are done afaik 18:09:21 q+ 18:09:29 ack pfps 18:09:35 q+ 18:09:43 Peter: a number of these have to do with last call's actions, but not sure what's the process here 18:10:10 ... do we need to re-vote or re-send message or approve message(s) from Bijan or ?? 18:10:18 zakim, unmute me 18:10:18 bijan should no longer be muted 18:10:23 q? 18:10:26 Ian: unsure what's the official line... 18:10:32 ack bijan 18:10:57 Bijan: this is not about my ownership of the docs written... 18:11:03 q? 18:11:51 Ian: if someone was in charge of acting on some changes, that person would send it as a "proposal" and if no objections then approved... but let's get back to this later 18:12:07 Ian: all actions in pending category can be cleared now... 18:12:08 q+ 18:12:12 q? 18:12:16 ack pfps 18:12:23 ACTION-269 is done ormotted 18:12:25 mooted 18:12:49 Peter: one of alan's action (action 247) was outstanding for quite a while... 18:13:04 Ian: yes, this needs to be concluded soon 18:13:33 ACTION: Ian to talk to Alan about acting on action 247 or withdraw the comment... 18:13:33 Created ACTION-271 - Talk to Alan about acting on action 247 or withdraw the comment... [on Ian Horrocks - due 2009-02-04]. 18:13:49 the point is that 247 is blocking other work 18:14:06 Ian: other actions cannot be moved on, at this point 18:14:15 Topic: face to face meeting (no.5) 18:14:17 q? 18:14:39 Ian: we are confirming, this meeting goes ahead... 18:15:03 ... F2F5 = http://www.w3.org/2007/OWL/wiki/F2F5 18:15:24 ... would be useful if as many people as possible come and join, as there is quite some important stuff to do 18:15:36 Topic: Last call comments 18:16:00 q+ 18:16:02 Ian: see here http://lists.w3.org/Archives/Public/public-owl-comments/ and http://www.w3.org/2007/OWL/wiki/Responses_to_Last_Call_Comments 18:16:08 zakim, unmute me 18:16:08 bijan was not muted, bijan 18:16:08 ack bijan 18:16:34 ... first let's talk about how to approach the situation if somebody has an action to draft a response, what should we do with the outcome 18:16:41 q+ 18:16:46 q? 18:16:59 Bijan: depends on type of action - whether it proposes to change something or only to clarify 18:17:39 ack pfps 18:17:45 Ian: might be useful to look at the last call page on the wiki... so that we can go down, see the status, see the response and if happy, just go on with it 18:18:17 Peter: we already had this response to the call; that is THE thing we did... the affected doc does map correctly? 18:18:35 Ian: might be useful to say explicitly which doc needs touching 18:19:30 Bijan: I would update keys with what I understand happened... no draft there to doc on syntax? do we need another column on this? 18:19:46 q? 18:20:03 Ian: maybe enough to just put in who does work on it, otherwise bookkeeping is going to take too much overhead 18:20:38 Bijan: if chairs are not sending those responses, then each response should have a concrete owner - who would then respond, right? 18:21:07 Peter: the response would link to an email, point made earlier 18:21:13 zakim, mute me 18:21:13 bijan should now be muted 18:21:21 Ian: should also point to incoming email and perhaps copied to public owl list 18:21:42 Peter: there is quite a few msgs in the "response" column... 18:21:48 zakim, unmute me 18:21:48 bijan should no longer be muted 18:21:50 q+ 18:21:56 q? 18:22:05 Ian: do we need to contact the people making responses that we provided comments? 18:22:22 q+ 18:22:26 ack bijan 18:22:30 zakim, mute me 18:22:30 bijan should now be muted 18:22:38 q- 18:22:48 ... we should have a template for email going out to people with a response, asking them whether this satisfies the objections, etc. 18:22:57 yep 18:22:57 ... provide this later... 18:22:58 +1 18:22:58 good 18:23:18 q+ 18:23:31 ack ivan 18:23:33 ... so, we will add an "owner" to each objection/response, and the "response" will actually point to the email sent to the original objection 18:23:57 Ivan: we may need another column - need pointer to the email from commentator saying "yes happy with changes" 18:24:11 commentor responses could go in status column 18:24:30 ... we need a trace from "objection" - "our response" - "their acceptance of change or otherwise" 18:24:55 q? 18:25:00 ack christine 18:25:01 ... in between these recorded points there may be some discussion, but at least resolutions would be clear 18:25:14 q? 18:25:22 msmith has joined #owl 18:25:25 +msmith 18:25:48 Christine -- we can't hear you! 18:26:13 a columm about who answers 18:26:21 q+ 18:26:23 -schneid 18:26:25 zakim, mute me 18:26:25 bijan was already muted, bijan 18:26:27 Ian: what are we doing about comments on new features/requirements 18:26:30 ack bijan 18:26:43 seems there is a mix wi 18:27:04 Bijan: suggestion - treat these separately, comments on draft are different from suggestions for new features; 18:27:24 please wait for the connection 18:27:27 ... we may then contact proposers separately with what is going to happen with their suggestions 18:27:34 +??P21 18:27:35 just use a special status flag for these 18:27:39 q? 18:27:55 Ian: but we may still want to trace these responses somehow... some of them might be quite substantial 18:27:56 zakim, P21 is christine 18:27:56 sorry, christine, I do not recognize a party named 'P21' 18:28:02 zakim, mute me 18:28:02 bijan should now be muted 18:28:12 zakim, ?p21 is christine 18:28:12 sorry, MartinD, I do not recognize a party named '?p21' 18:28:13 q? 18:28:20 zakim, ??p21 is christine 18:28:20 +christine; got it 18:28:47 Christine: regarding that special column for replies... I didn't understand how the owner is going to be appointed 18:29:08 Ian: volunteering or general agreement? but there will be a column on the owner 18:29:09 Do we need a place to collect the comments on NF and R? 18:29:28 Christine: regarding how to comment / react on new features 18:29:49 ewallace, i suggested that we put them into one issue in the tracker 18:29:57 but a wiki page are good 18:30:13 ... pick points from mailing list and sort them into two type - "can't fix them directly" vs. "somehow linked to LC comments - need reply"? 18:30:15 q+ 18:30:19 zakim, unmute me 18:30:19 bijan should no longer be muted 18:30:38 Bijan: not sure we need to have them as LC 18:30:58 +q 18:31:02 Ian: the issue is that LC comments are mixed with new feature proposal.. 18:31:22 q? 18:31:30 zakim, mute me 18:31:30 bijan should now be muted 18:31:37 ... "can't see feature X" now; but then the amendments may be included in the final version... 18:31:54 ack bijan 18:32:03 zakim, mute me 18:32:03 bijan should now be muted 18:32:05 ... christine's point on a concrete wiki page, similar to LC comments may do... trying to categorize as suggested 18:32:08 ack christine 18:32:28 Christine: agree that these are not LC comments, it's just they may need reply and we should be consistent 18:32:47 Ian: you take action then to produce the page consolidating new features and rationale? 18:33:14 q? 18:33:19 ACTION: Christine to produce a wiki page to consolidate new features/rationales from email responses that got mixed into LC comments 18:33:19 Created ACTION-272 - Produce a wiki page to consolidate new features/rationales from email responses that got mixed into LC comments [on Christine Golbreich - due 2009-02-04]. 18:33:36 Ian: was asked by Alan to include comment from Mike here... 18:33:48 q? 18:34:03 Mike: related to issue 135, resolved earlier... 18:34:08 http://www.w3.org/2007/OWL/wiki/index.php?title=Mapping_to_RDF_Graphs&diff=11045&oldid=10323 18:34:22 ... resolution embedded in the RDF mapping doc 18:34:53 q+ 18:34:54 ... then it was written in a way that any RDF graph with no typing triple will become "an anonymous OWL ontology"? 18:35:03 q? 18:35:11 pointers? 18:35:12 zakim, unmute me 18:35:12 bmotik should no longer be muted 18:35:16 ... in my email I gave example how this may affect our test cases 18:35:17 ack bmotik 18:35:42 Boris: at last f2f this was the decision taken - imports vs. inclusions vs. etc. 18:35:53 ... alan was for allowing imports of arbitrary graphs 18:36:21 One example http://km.aifb.uni-karlsruhe.de/projects/owltests/index.php/TestCase:WebOnt-I5.2-001 18:36:42 Ian: the point may be subtler - if RDF graph with no typing header was allowed, now this is reversed, it should work? 18:37:03 Boris: targets of import statements would be merged into graphs... 18:37:08 q? 18:37:15 q+ 18:37:27 ... no aware that these graphs were ok in owl 1... 18:37:28 ack pfps 18:37:56 Peter: discussion turned on the backward compatibility... this was the solution to regain that back compatibility 18:38:06 q? 18:38:08 q+ 18:38:18 q- 18:38:19 q? 18:38:22 zakim, unmute me 18:38:22 bijan should no longer be muted 18:38:22 +1 to pfps 18:38:25 Zakim, mute me 18:38:25 bmotik should now be muted 18:38:28 Ian: so should we treat headerless RDF graphs as OWL ontologies 18:38:34 Peter: as OWL DL ontologies 18:38:38 q+ 18:38:58 Ian: currently they are treated as OWL FULL ontologies, if I follow Peter and Boris correctly 18:38:59 q+ 18:39:02 ack msmith 18:39:07 http://km.aifb.uni-karlsruhe.de/projects/owltests/index.php/TestCase:WebOnt-I5.2-001 18:39:29 Mike: ontologies like the ones in test case above will not be valid OWL 2 DL, if the doc remains as it is now 18:39:42 ack bijan 18:39:46 q? 18:39:46 Ian: so, there is some back compatibility issue and a case that reveals the point 18:40:10 Bijan: confused now; we would normally handle this case, surprised we are not following this up 18:40:54 Ian: this is a kind of along Alan's repair idea... include the graphs, import even graphs that do not satisfy header requirements - treat them as merging with other content 18:41:02 q+ 18:41:09 Bijan: importing seems fine, treating them as standalone is tricky 18:41:17 ack pfps 18:41:27 Ian: yes, they should be imported into "unbroken" one 18:41:35 q+ 18:41:36 q+ 18:41:44 ack bijan 18:41:56 Peter: current broken ontologies are those that miss certain declarations; the discussion was not about importing 18:42:28 q? 18:42:38 zakim, unmute me 18:42:38 sorry, schneid, I do not know which phone connection belongs to you 18:42:39 zakim, mute me 18:42:39 bijan should now be muted 18:42:44 Bijan: standalone fragments remain OWL FULL, if imported into properly typed ontologies, they may become OWL 2 DL - but only via import (kind of inherit typing info) 18:42:45 ack mschneid 18:42:51 ack schneid 18:43:22 what with the RHS of an entailment: does it need an ontology header? 18:43:25 -christine 18:43:30 zakim, mute me 18:43:30 sorry, schneid, I do not know which phone connection belongs to you 18:43:32 Ian: are we happy that we knew about this and nothing needs changing right now? 18:43:41 Let O1 be the OWL Full but not OWL DL ontology, and O2 another ontology. If O2 imports O1 results in a OWL DL ontology, that is fine and does not involve repair. 18:43:47 I am extatic 18:44:03 there was a mix between scnheid and me ! 18:44:03 q? 18:44:05 Fixing O1 is changing the ontology, which puts it into repair mode 18:44:08 ... mike raised this, are you accepting this? 18:44:09 -bcuencag 18:44:29 Mike: good that other people are comfortable, I just came across a case raising this 18:44:44 Ian: let's go to last call comments 18:45:00 +??P15 18:45:07 q? 18:45:08 ... thing that wasn't discussed - do we go down the list, quick discussion and allocate ownership? 18:45:14 q+ 18:45:16 chair's pero.. perrog.. choice 18:45:18 ... suggeestions? 18:45:19 q? 18:45:23 zakim, ??P15 is christine 18:45:23 +christine; got it 18:45:55 Ivan: there is a number of comments of type "good job" and many editorial - those might be useful to get out of our way, done 18:46:04 How about the chairs, or some person, does it 18:46:06 offline 18:46:13 ... we need to know which comments are serious and require serious work 18:46:14 and then we do a batch agreement 18:46:18 +??P21 18:46:20 can't the chairs do this sort of thing? I don't view it as a good thing to do now. 18:46:29 zakim, ??P21 is me 18:46:29 +schneid; got it 18:46:29 ... otherwise we may waste time on minor points and find the big ones too late 18:46:43 q+ 18:46:49 ack ivan 18:46:55 zakim, unmute me 18:46:55 schneid was not muted, schneid 18:46:57 chairs could just send back 'we're happy that you are happy' 18:47:00 Ian: chairs can go through the list, filter minor comments, editorial ones = no discussion required... etc. 18:47:07 ack schneid 18:47:10 chairs could assign editorial fixes to some editor 18:47:24 Yes 18:47:27 yes 18:47:29 q+ 18:47:33 Both sides do 18:47:35 yes, otherwise the rhs is not an ontology 18:47:37 Michael: there are still situations when you have entailment, does the right side need onto header 18:47:40 q? 18:47:47 ack msmith 18:47:48 Mike: RHS cannot exist as ontology without its header 18:47:58 zakim, mute me 18:47:58 schneid should now be muted 18:47:58 Tools are free to be more liberal of course, but then they aren't checking "ontologies" 18:48:17 Ian: we should then go through those comments offline, and focus/discuss the important ones 18:48:29 ... it's not that clear which one had attention until now 18:48:45 it's actually a little formal problem with the correspondence theorem, since ontology headers are not interpreted by the Direct Semantics... but I will solve this :) 18:48:46 q? 18:48:51 q+ 18:48:52 ... obvious thing - how to deal with points raised by TopQuadrant - quite a large one 18:48:52 number, please? 18:48:56 zakim, unmute me 18:48:56 bijan should no longer be muted 18:48:56 q? 18:49:01 ack bijan 18:49:05 number 34 18:49:25 found it, but do we have a final version? 18:49:29 Bijan: TQ is a bunch of comments, we can now go through them now or just filter them as suggested earlier 18:49:55 Ian: either chairs or somebody should split TQ comments into "proper" focused comments 18:50:01 q+ 18:50:07 q? 18:50:15 ack ivan 18:50:19 Bijan: do the pointer first and then check if they match... 18:50:21 http://www.w3.org/mid/003801c98000$a83794e0$f8a6bea0$@com 18:50:37 Ivan: Jeremy sent separately email above - the main TQ comment... 18:50:54 q? 18:50:56 ... how to treat this separate page he edited - what is the comment, what is the blurb around 18:51:00 zakim, unmute me 18:51:01 bijan was not muted, bijan 18:51:06 the mail ivan pasted is much smaller 18:51:27 Bijan: the key point is second to last paragraph 18:51:37 ... about unmotivated new features, etc. 18:51:56 ... alternatives they suggest might not be key for us at the moment 18:52:18 ... the only hard comments are those last two paragraphs on OWL2.. 18:52:34 ... they are mostly detailing what means "undermotivated" 18:52:59 ... the substantive point is about OWL XML, OWL Manchester syntax 18:53:33 ... we should do enumeration of those features, weigh the benefit of feature vs. motivation... this is what they may expect from us as response 18:53:52 Ian: it's a bit strange email "we ask many 18:54:07 q+ 18:54:11 ... asking many unmotivated features to be dropped 18:54:15 q? 18:54:21 ... a way to address is to add motivation to all features? 18:54:24 zakim, unmute me 18:54:24 schneid should no longer be muted 18:54:28 ack schneid 18:54:33 q? 18:54:53 Michael: the story talks about cost problem 18:55:34 ... is this about extension of any kind of ontology language? is there something specific they want to have extended here? Some points apply to C, Java, etc. 18:55:43 Zakim, mute me 18:55:43 bmotik was already muted, bmotik 18:55:52 zakim, mute me 18:55:52 schneid should now be muted 18:55:55 ... there are features that have additional cost, always... which we may not want to start including 18:55:56 no 18:56:01 q? 18:56:29 Ian: rough agreement here 18:56:40 q+ 18:56:51 q? 18:56:52 ... what is the concrete action - breaking the email down into detailed list? (BIjan thinks no need for this) 18:56:57 +q 18:56:58 ack bijan 18:57:01 Bijan: I may draft the response 18:57:30 ... we should identify what we see as substantive comment, and then respond to this - WG doesn't think there are unmotivated features 18:57:31 q+ 18:57:45 q? 18:57:48 +1 to bijan 18:57:49 ack christine 18:57:52 ... so, thanking them for listing them, raising them and we will definitely address explicit motivation in the further drafts 18:57:56 +1 to bijan 18:58:09 Christine: not sure this is about motivation for new features 18:58:26 ... they suggested there are too many features, maybe not needed 18:58:37 ... many features will not change anything 18:58:45 q? 18:58:48 ack ivan 18:58:53 Ivan: two issues here 18:59:22 q+ 18:59:27 q? 18:59:36 q+ 18:59:43 ... one point is that answer as suggested above by Bijan (that feature doc is extended, etc.) may open us to the objection that we now work with many features that do not have explicit cases/motivation 18:59:48 not all concerns were actually about "unmotivated features". there were a few more concrete things 18:59:56 url please ? 18:59:57 ... then there are some technical issue, which can be treated as such 19:00:23 ... property chain inclusion, how RDF is treated, etc. etc. 19:00:24 q? 19:00:32 ... these should not be forgotten 19:01:04 +1 to ian, this is not a software development project 19:01:17 Ian: one about requirements - always clear that we are not producing fully fledged requirements doc, it was more about capturing some experiences from previous work in WG, elsewhere 19:01:26 That's what I meant 19:01:37 pfft 19:01:44 zakim, unmute me 19:01:44 bmotik should no longer be muted 19:01:53 ... this is not about acquiring all requirements, about continuously formulating needs as things emerge... this is not a "done" req. doc 19:02:38 ... one of the jobs of chair should be to go through comments, to filter those technical ones, and then we can give a part response to TQ in general terms, and a part in concrete technical points raised to LC 19:02:44 q? 19:02:52 ack bmotik 19:03:15 Boris: if we go through those comments from TQ, he agrees with most substantive logical changes 19:04:06 ... another thing to include in our response, is about symmetry issue - people were not sure why certain things are included, so this syntactic sugar helps them to make sense of changes 19:04:25 ... there should not be problem with RDF compatibility, we have RDF-friendly fragment 19:04:27 Zakim, mute me 19:04:27 bmotik should now be muted 19:04:36 q? 19:04:38 zakim, unmute me 19:04:38 bijan was not muted, bijan 19:04:40 ack bijan 19:04:46 Ian: the basic plan of a general reply on motivation + adding points on technical aspects, remains valid 19:04:59 +q 19:05:14 zakim, mute me 19:05:14 bijan should now be muted 19:05:24 Ian: can we take some action here? 19:05:30 no 19:05:37 q? 19:05:39 want to speak 19:05:45 q? 19:05:48 ack christine 19:06:02 Christine: how many new features are a matter of concern here? 19:06:21 q+ 19:06:21 q+ 19:06:32 q? 19:06:34 Ian: still working on documenting all the feature motivations - may get more motivation on some features 19:07:02 Christine: I would like to be involved in the reply, to see which specific feature is without motivation, etc. 19:07:17 I'm happy to yeidl 19:07:19 I don't have to do it 19:07:27 Ian: we should start with drafting, the others would then see the draft and react to it 19:07:51 Christine: I don't want to have many new additions to new features, this was addressed by WG for long enough 19:08:19 Ian: yes, we should not promise a large number of new features; but everybody will be able to react to Bijan's draft 19:08:20 ack ivan 19:09:07 Ivan: there is one criticism we raised at F2F - the motivation doc has bias towards life science, issue we found earlier 19:09:07 zakim, unmute me 19:09:07 bijan should no longer be muted 19:09:17 ... trying to rebalance this bias may be really helpful 19:09:27 +q 19:10:01 Ian: unless people come with use cases from other domains, obviously Christine worked her case from the life sciences, she needs to rely on other to provide input 19:10:08 ack bijan 19:10:45 Bijan: two points - what we need to add to the list of things - XML syntax may need a new section (e.g.) 19:11:13 ... we should either have one umbrella section or concrete sections to respond to things raised, so that we don't get the same comments again 19:11:21 ... some comments came from me as well 19:11:44 ... there is a lot of work to be done, but this is only first publicly released working draft 19:11:55 zakim, mute me 19:11:55 bijan should now be muted 19:12:07 Ian: the doc is only working draft, correct - there will be changes to it 19:12:09 ack christine 19:12:39 Ian: let's get back to actions 19:13:03 christine has joined #owl 19:13:13 ACTION: Ian to sift through Jeremy's / TQ email and web page to filter those aspects requiring further work 19:13:13 Created ACTION-273 - Sift through Jeremy's / TQ email and web page to filter those aspects requiring further work [on Ian Horrocks - due 2009-02-04]. 19:13:17 ACTION: Bijan to draft general response w.r.t. motivation issue raised in the TQ email/comment 19:13:18 Created ACTION-274 - Draft general response w.r.t. motivation issue raised in the TQ email/comment [on Bijan Parsia - due 2009-02-04]. 19:13:21 Or someone else! 19:13:26 Oh, too late 19:13:31 :-) 19:13:53 Ian: probably concludes that aspect 19:14:12 ... we currently don't have that status column on comments 19:14:23 ... quite a few issues discussed, people drafted responses 19:14:24 First one: http://www.w3.org/2007/OWL/wiki/LC_Responses/ALR1 19:14:29 +1 19:14:31 ... we can look at them and move them forward 19:14:33 q? 19:14:52 ALR1, MS1 19:14:55 zakim, unmute me 19:14:55 bijan should no longer be muted 19:14:59 Ian: without owner/status tracking it's abit confusing, but let's try 19:15:16 Bijan: the pointer to the first is above 19:15:30 Ian: the actual comment is at the bottom "The WG has decided" 19:15:35 Bijan's response looks fine to me (and quite subdued) 19:16:00 Bijan: this was discussed, at least two people saw it 19:16:07 q? 19:16:16 victory! 19:16:27 Ian: unless anybody has a problem, let's declare this done - as soon as boilerplating is ready we can move on 19:16:34 q+\ 19:16:36 MS1, but it requires a technical change 19:16:37 q+ 19:16:44 ... any other responses in the same category - drafted, ready to go? 19:16:45 ack \ 19:16:49 ack ivan 19:16:59 There's a decision to be made on Martin Duerst 19:17:08 Ivan: issue with unicode... in RDF comments, where are we? 19:17:20 http://lists.w3.org/Archives/Public/public-owl-wg/2009Jan/0094.html 19:17:27 Bijan: decide how to reply to the issue (I only summarized the point, not replied) 19:17:46 ... we can send this to RDF list... 19:17:58 ... we talk now about number 5 19:18:34 ... my proposal - send generic syntax ref doc, as now, may XML syntax too, and ..... 19:19:14 q? 19:19:16 +1 to generic 19:19:21 rather complex and not optimal, but I guess the legalese is required 19:19:21 ... according to conformance doc, we restrict parsing to certain minimal levels, so characters of unicode5 should not be serialized, as tthey are not supported at these levels? 19:19:34 no LC for this 19:19:48 ... would require some changes to syntax doc, and all other docs referencing unicode 19:19:50 q+ 19:19:50 but we need to document the change 19:19:57 Ian: how difficult to draft response? 19:20:23 Bijan: we now updated all docs, metacomment to RDF group to tie it normatively to XML... 19:20:50 ack ivan 19:20:51 ack ivan 19:20:56 ... we need to change references, docs and probably consider the conformity doc 19:21:12 Ivan: we should make it clear we are aware of the problem 19:21:25 Ian: Bijan, will you take ownership of this too? 19:21:48 ... somebody needs to own the reply, although not being editor of the touched docs 19:21:53 Bijan can kick the editors and get them to "do the right thing" 19:22:00 Bijan: happy to coordinate, to track those references 19:22:19 ... will send email to the list to change conformance aspects... 19:22:21 +q 19:22:25 q? 19:22:30 metacomment -- does this need formal action 19:22:30 ack christine 19:22:57 Its' not clear that jim means it as a LC comment 19:23:13 ACTION: Bijan to track references to unicode 5 in the current drafts and propose changes needed to the conformance doc 19:23:13 Created ACTION-275 - Track references to unicode 5 in the current drafts and propose changes needed to the conformance doc [on Bijan Parsia - due 2009-02-04]. 19:23:18 q+ 19:23:37 ACTION: Bijan to draft response/actions w.r.t. [5] 19:23:37 Created ACTION-276 - Draft response/actions w.r.t. [5] [on Bijan Parsia - due 2009-02-04]. 19:23:52 q? 19:23:55 +q 19:23:56 ack bijan 19:23:56 quote: RECOMMENDATION FROM THE AC MEMBER OF RPI 19:23:56 I think the WG should seriously consider taking the profiles off of the Rec track for now, getting the rest through, and then putting the profiles either into a separate CR or leaving them as WG notes. 19:24:04 Bijan: there is also points from Jim following our discussion, but they are not in the category LC 19:24:15 q? 19:24:24 ack christine 19:24:27 q+ to point at another issue to dispose of 19:24:33 Ian: there is formal suggestion from AC member... as quoted above 19:24:48 q+ 19:25:02 ack bijan 19:25:02 bijan, you wanted to point at another issue to dispose of 19:25:06 ... we have treated comments from other members of WG as last call comments, but not sure how to treat this specific one 19:25:15 q- 19:25:28 Bijan: chair may want to ask the sender if they want to have their comment as LC or not 19:25:54 ... if they want to be LC commenting, fair enough... if not, no need to reply formally at this stage 19:26:04 Ian: this is about having some more documentation 19:26:15 have to know before reply 19:26:40 go, Bijan, go! 19:26:44 Bijan: we already made changes, we only need to send an email - does that satisfy the needs/points? 19:26:47 Oy 19:27:01 I don't care 19:27:13 Ian: don't mind doing this - Bijan or myself? 19:27:18 Bijan: I can do it 19:27:50 Ian: going reasonably well - 19:28:10 q? 19:28:17 ... alan and me will go through the comments and filter those needing further action, talk, and which can be sorted by "polite acknowledgement" 19:28:34 Bijan: this is not something that chairs *must* do, somebody else can do it 19:28:39 bye 19:28:41 -Evan_Wallace 19:28:42 -msmith 19:28:43 ivan has left #owl 19:28:43 -Zhe 19:28:45 -bmotik.a 19:28:45 -bmotik 19:28:46 -bijan 19:28:46 -Achille 19:28:46 Ian: this concludes today's talk then... 19:28:47 -pfps 19:28:48 -baojie 19:28:51 -Sandro 19:28:52 -Ivan 19:28:54 -IanH 19:28:55 bye 19:28:55 zakim, who was here 19:28:56 -christine 19:28:58 I don't understand 'who was here', MartinD 19:29:01 -ratnesh 19:29:08 -schneid 19:29:14 Ivan, I'm sending the rdf comment to where? and on behalf of the group? 19:29:15 bye 19:34:56 http://lists.w3.org/Archives/Public/public-owl-comments/2009Jan/att-0003/128 19:34:58 seems broken 19:39:06 msmith has left #owl 19:51:23 -MartinD 19:51:24 SW_OWL()1:00PM has ended 19:51:26 Attendees were bijan, +0190827aaaa, MartinD, +1.914.421.aabb, +86528aacc, Achille, IanH, Evan_Wallace, pfps, ratnesh, bmotik, baojie, Zhe, Sandro, bcuencag, schneid, Ivan, msmith, 19:51:29 ... christine 19:52:09 RRSAgent, make records public 19:54:49 MartinD has left #OWL 21:54:20 Zakim has left #owl