16:39:10 RRSAgent has joined #owl 16:39:10 logging to http://www.w3.org/2009/04/15-owl-irc 16:53:15 msmith has joined #owl 16:56:38 pfps has joined #owl 16:56:55 SW_OWL()1:00PM has now started 16:57:02 +Peter_Patel-Schneider 16:57:09 Rinke has joined #owl 16:57:11 pfps has changed the topic to: http://www.w3.org/2007/OWL/wiki/Teleconference.2009.04.15/Agenda 16:57:24 zakim, this is owl 16:57:24 pfps, this was already SW_OWL()1:00PM 16:57:26 ok, pfps; that matches SW_OWL()1:00PM 16:57:30 + +1.202.408.aaaa 16:58:06 sebastian has joined #owl 16:58:32 bcuencagrau has joined #owl 16:58:54 alanr has joined #owl 16:59:17 + +86528aabb 16:59:25 IanH has joined #owl 16:59:28 +??P1 16:59:31 zakim, ??p1 is me 16:59:31 +bijan; got it 16:59:39 Zakim, 86528aabb is me 16:59:39 sorry, bcuencagrau, I do not recognize a party named '86528aabb' 16:59:43 + +2 16:59:50 zkaim, aabb is bcuencagrau 16:59:51 + +1.603.897.aadd 16:59:58 zakim even 17:00:04 Zhe has joined #owl 17:00:08 zakim, aabb is bcuencagrau 17:00:08 sorry, bijan, I do not recognize a party named 'aabb' 17:00:09 JeffP has joined #owl 17:00:11 +??P6 17:00:12 christine has joined #owl 17:00:19 zakim, aabb is me 17:00:19 +bcuencagrau; got it 17:00:24 MarkusK_ has joined #owl 17:00:26 Zakim, mute me 17:00:26 +Ian_Horrocks 17:00:26 bcuencagrau should now be muted 17:00:27 - +2 17:00:38 zakim, Ian_Horrocks is IanH 17:00:38 +IanH; got it 17:00:49 yes 17:00:54 zakim, who is here? 17:00:54 On the phone I see Peter_Patel-Schneider, msmith, bcuencagrau (muted), bijan, +1.603.897.aadd, ??P6, IanH 17:00:56 On IRC I see MarkusK_, christine, JeffP, Zhe, IanH, bcuencagrau, sebastian, Rinke, pfps, msmith, RRSAgent, Zakim, bijan, sandro, trackbot 17:00:59 +??P4 17:01:04 +??P8 17:01:05 ivan has joined #owl 17:01:05 zakim, ??P4 is me 17:01:05 +Rinke; got it 17:01:10 zakim, mute me 17:01:10 Rinke should now be muted 17:01:16 scribenick: msmith 17:01:17 zakim, dial ivan-voip 17:01:17 ok, ivan; the call is being made 17:01:18 +Ivan 17:01:22 +Sandro 17:01:22 zakim, ??P8 is me 17:01:26 I already had ??P8 as MarkusK_, christine 17:01:37 zakim, who is here? 17:01:39 On the phone I see Peter_Patel-Schneider, msmith, bcuencagrau (muted), bijan, +1.603.897.aadd, ??P6, IanH, Rinke (muted), MarkusK_, Ivan, Sandro 17:01:39 uli has joined #owl 17:01:48 bmotik has joined #owl 17:01:54 On IRC I see uli, ivan, MarkusK_, christine, JeffP, Zhe, IanH, bcuencagrau, sebastian, Rinke, pfps, msmith, RRSAgent, Zakim, bijan, sandro, trackbot 17:02:00 + +1.518.276.aaee 17:02:04 topic: admin 17:02:04 baojie has joined #owl 17:02:05 -Rinke 17:02:09 zakim, ??P6 is me 17:02:13 +christine; got it 17:02:14 zakim, who is here? 17:02:15 subtopic: roll call 17:02:18 On the phone I see Peter_Patel-Schneider, msmith, bcuencagrau (muted), bijan, +1.603.897.aadd, christine, IanH, MarkusK_, Ivan, Sandro, +1.518.276.aaee 17:02:26 +??P4 17:02:27 Zakim, aaee is baojie 17:02:27 On IRC I see baojie, bmotik, uli, ivan, MarkusK_, christine, JeffP, Zhe, IanH, bcuencagrau, sebastian, Rinke, pfps, msmith, RRSAgent, Zakim, bijan, sandro, trackbot 17:02:28 Zakim, ??P4 is me 17:02:30 ewallace has joined #owl 17:02:33 +bcuencagrau.a 17:02:34 subtopic: agenda amendments 17:02:35 +baojie; got it 17:02:39 +bmotik; got it 17:02:43 Zakim, mute me 17:02:45 bmotik should now be muted 17:02:52 subtopic: previous minutes 17:02:53 +??P16 17:02:57 minutes OK by me 17:03:00 zakim, ??P16 is me 17:03:00 +uli; got it 17:03:03 can you hear me? 17:03:06 + +22427aaff 17:03:10 +Alan_Ruttenberg 17:03:12 zakim, mute me 17:03:12 uli should now be muted 17:03:13 Zakim, ??P4 is someone-else 17:03:14 I already had ??P4 as bmotik, bmotik 17:03:18 Rinke, I couldn't hear you 17:03:18 zakim, ??P4 is me 17:03:18 I already had ??P4 as bmotik, Rinke 17:03:26 ianh: any comments on minutes? 17:03:34 "minutes OK by me" 17:03:37 zakim, aaff is me 17:03:37 +JeffP; got it 17:03:39 +Evan_Wallace 17:03:42 Zakim, bmotik is Rinke 17:03:42 +Rinke; got it 17:03:52 RESOLVED: Accept Previous Minutes (8 April) http://www.w3.org/2007/OWL/meeting/2009-04-08 17:03:54 Zakim, +bcuencagrau.a is me 17:03:55 sorry, bmotik, I do not recognize a party named '+bcuencagrau.a' 17:03:58 q+ 17:04:04 subtopic: pending review action items 17:04:04 q+ 17:04:13 Zakim, bcuencagrau.a is me 17:04:13 +bmotik; got it 17:04:14 ack JeffP 17:04:17 Zakim, mute me 17:04:17 bmotik should now be muted 17:04:40 jeffp: I'd like agenda amendment for negative property assertions 17:04:53 q? 17:04:56 ack pfps 17:05:04 ianh: ok, we'll try to do this in topic "(Technical) Issues Arising" 17:05:13 she said consider it done 17:05:17 pfps: what about Elisa's review action (ACTION-321) 17:05:29 OK to close it by me 17:05:29 q? 17:05:29 ianh: she considers it done for this review round 17:05:51 ianh: consider all pending done (320, 321, 329, 328, 326) 17:06:05 subtopic: Due and overdue Actions 17:06:22 subsubtopic: ACTION-299 17:06:31 Maybe the links from NF&R, but these are intentional 17:06:38 sandro: I don't know what links he was talking about. 17:06:56 ianh: there are references in NF&R that reference documents in the wiki. e.g., there is a reference to punning 17:07:24 sandro: yesterday (or before) I sent an email to the list about links to the wiki 17:07:37 in any case NF&R is not in last call, so we don't need to fix it right now 17:07:41 +q 17:07:46 q+ 17:07:53 ivan_ has joined #owl 17:08:07 RDF Semantics might be a bit more problematic 17:08:08 ianh: links to wiki seem like a bad idea - mutable 17:08:25 sandro: I'm not sure they're so bad, they may be the best we can do 17:08:31 ack christine 17:08:46 sandro: I do agree it's worth some effort to find better citations than links to wiki pages. 17:08:49 christine: what should I do for these links? 17:08:53 -Rinke 17:09:52 ianh: it seems there is a reasonable justification for pointing at the wiki now and this is not time critical yet 17:10:03 ... what we have now is fine for a working draft 17:10:05 ack bijan 17:10:11 q? 17:10:19 +??P4 17:10:24 zakim, ??P4 is me 17:10:24 +Rinke; got it 17:10:27 zakim, mute me 17:10:27 Rinke should now be muted 17:10:32 bijan: I have no problem with wiki mutability, if we can freeze specific pages. 17:10:41 q? 17:10:50 sandro: are you worried about vandalism if left unattended? 17:11:04 q? 17:11:31 +1 to IanH 17:11:37 bijan: not so much vandalism. more just unanticipated changes 17:12:05 ianh: we're considering ACTION-299 done 17:12:14 subsubtopic: ACTION-325 17:12:20 action-299: closed 17:12:20 ACTION-299 Find and fix the to-wiki-links Jeremy complains about notes added 17:12:20 If you meant to close ACTION-299, please use 'close ACTION-299' 17:12:34 close action-299 17:12:34 +??P22 17:12:34 ACTION-299 Find and fix the to-wiki-links Jeremy complains about closed 17:12:43 close action-325 17:12:43 ACTION-325 Send a comment to the CURIE folks about us not using them. closed 17:12:49 zakim, who is talking? 17:12:49 I am sorry, pfps; I don't have the necessary resources to track talkers right now 17:12:56 q? 17:13:18 subtopic: which document should we propose as a citation for OWL 2 as a whole? 17:13:23 q? 17:13:39 OK by me, I guess 17:13:40 yes 17:13:43 ianh: current position seems to be recommend overview 17:13:45 q? 17:13:46 +1 17:13:47 Overview is the main entry point. 17:13:47 I'm reconciled enough to that, with grumpiness 17:14:03 +1 to overview (which is why we made all WG authors) 17:14:13 q? 17:14:23 ianh: that was the intention of overview from last f2f 17:14:44 q? 17:14:53 I'm happy with it. 17:14:57 i'll ship it then... 17:15:02 ... we continue with owverview as main citation point 17:15:08 PROPOSED: WG will send LC comment to POWDER WG as per Ivan's draft 17:15:13 +1 17:15:14 +1 17:15:16 +1 17:15:17 +1 17:15:18 +1 17:15:19 +1 17:15:23 +1 17:15:25 +1 17:15:25 +1 17:15:26 msmith: +1 17:15:27 +1 17:15:27 +1 17:15:29 subtopic: LC comment to POWDER WG 17:15:36 RESOLVED: WG will send LC comment to POWDER WG as per Ivan's draft 17:15:50 ivan's draft: http://lists.w3.org/Archives/Public/public-owl-wg/2009Apr/0120.html 17:16:14 topic: Documents and Reviewing 17:16:29 q? 17:16:32 q? 17:16:35 Primer looks good to me. 17:16:44 no! 17:16:45 (y) 17:16:45 ianh: last week we punted on publishing the Primer. I think it is now ready to pub. Comments? 17:16:47 looks fine to me 17:16:49 yes 17:16:55 q? 17:17:10 No one has to like it in it's current form! 17:17:17 By publishing we don't commit to it 17:17:19 q? 17:17:20 christine: I haven't changed my mind since last week and do not want to see it published 17:17:47 ... I would like a commitment for significant changes before last call 17:18:16 Christine, note that it currently says: "This Working Draft has undergone a complete rewrite since the previous version of 11 April 2008, to improve its readability and utility. Examples are now mostly also available in Turtle syntax. This document will undergo further significant revision before a final version is produced. " 17:18:17 ianh: there is no positive commitment inherent in publishing, so such a commitment to force changes is inappropriate 17:18:20 q? 17:18:21 q? 17:18:23 q+ 17:18:28 +1 to Ian 17:18:41 ack sandro 17:18:47 christine: I don't want to commit to going to LC in the next publication 17:19:07 Standard boilerpalte: 17:19:07 No Endorsement 17:19:08 Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. 17:19:11 I did it. :-) 17:19:15 This is standard for WD 17:19:17 +1 to Sandro stating that further revisions are in scope for us 17:19:36 sandro: I think the text quoted above (authored by pfps) meets your goal 17:19:40 PROPOSED: Primer is ready for publication as OWD 17:19:44 +1 ALU 17:19:47 +1 17:19:49 +1 17:19:49 +1 17:19:51 +1 17:19:52 +1 17:19:52 +1 17:19:53 +1 17:19:55 +1 17:19:57 +1 17:19:59 +1 17:20:01 0- 17:20:02 -Alan_Ruttenberg 17:20:06 0 17:20:08 +0 17:20:09 RESOLVED: Primer is ready for publication as OWD 17:20:11 0 17:20:16 even no reviews! 17:20:39 +Alan_Ruttenberg 17:20:50 alan: +1 17:21:32 Q? 17:21:32 subtopic: procedure for LC comments (in 2nd LC) 17:21:49 zakim, who is talking? 17:21:49 I am sorry, Rinke; I don't have the necessary resources to track talkers right now 17:21:54 ian: Last time, we treated last call comments from WG members like we treated them from outside. I think this was a mistake, overkill, with extra admin burden. 17:22:28 ianh: last time we allowed lc comments from wg members. We should change this b/c: I think this was a mistake b/c it added administrative burden, and interested parties should have already reviewed 17:22:33 Q? 17:22:38 ian: I would expect that folks in the WG have *already* *reviewed* these documents, and given their feedback already. 17:22:48 Ian; I think we should be quicker in dealing with the comments. 17:22:48 schneid has joined #owl 17:22:51 q+ 17:22:54 ... we also need to be quicker responding to lc comments 17:22:58 ack bijan 17:23:37 q? 17:23:41 bijan: are we pretty committed to thinking we have everything fixed (presentation and technical)? if so, then we can dispose of things pretty quickly. 17:23:47 +[IPcaller] 17:24:01 rrsagent, make record public 17:24:23 zakim, [IPcaller] is me 17:24:23 +schneid; got it 17:24:27 zakim, mute me 17:24:27 schneid should now be muted 17:24:27 ianh: last time we took a long time just to allocate resources for response. that consumed a lot of time. chairs might delegate actions more this time around 17:24:31 q? 17:24:35 -Alan_Ruttenberg 17:24:37 bijan: that sounds great. 17:24:58 q? 17:25:04 *I* feel more confident. :-) 17:25:08 ... but if we're not committed enough to push against push back - then we're definitely going to take a long time. are we more confident this time? 17:25:37 q? 17:25:51 ... so, then we should be quick and avoid revisiting the same debates 17:25:55 q? 17:26:06 q? 17:26:21 +Jonathan_Rees 17:26:26 q? 17:26:46 zakim, who is here? 17:26:46 On the phone I see Peter_Patel-Schneider, msmith, bcuencagrau (muted), bijan, +1.603.897.aadd, christine, IanH, MarkusK_, Ivan, Sandro, baojie, bmotik (muted), uli (muted), JeffP, 17:26:48 q+ 17:26:49 ... Evan_Wallace, Rinke (muted), sebastian, schneid (muted), Jonathan_Rees 17:26:52 On IRC I see schneid, ivan_, ewallace, baojie, bmotik, uli, MarkusK_, christine, JeffP, Zhe, IanH, bcuencagrau, sebastian, Rinke, pfps, msmith, RRSAgent, Zakim, bijan, sandro, 17:26:54 ... trackbot 17:27:12 jeffp: what are the deadlines for this lc? 17:27:16 ack JeffP 17:27:19 ianh: 21 days from publish 17:27:34 sandro: apr 21 is expected pub date, so may 12 for end of lc period 17:27:49 alanr has joined #owl 17:27:51 q+ 17:27:52 q? 17:27:56 ack bijan 17:27:59 on irc now... 17:28:02 ianh: last time we got comments well after end of comment period, we tried to deal with those. I'm not sure what happens with those? 17:28:18 bijan: if we set an intended CR date, that will help. 17:28:28 sandro: june 1 was a nominal CR date 17:28:28 q+ 17:28:42 ack alanr 17:29:02 We should respond to comments before end of LC period :) 17:29:02 alanr: we said 3 weeks for comments, 3 weeks for response. so 6 weeks from pub. 17:29:10 sandro: ok, that means june 2 17:29:14 q? 17:29:21 q+ 17:29:23 +1 to alanr 17:29:27 q? 17:29:32 alanr: we should be explicit about schedule dates in LC publish 17:29:34 q- 17:29:44 q+ 17:29:49 sandro: yes, phrased in a friendly way 17:29:52 +1 to being more friendly :) 17:29:53 q+ 17:30:16 sandro: doesn't want to over commit to dates 17:30:20 zakim, unmute me 17:30:20 schneid should no longer be muted 17:30:26 ack schneid 17:30:31 q- 17:30:49 schneid: should we see if everyone is available for a f2f at the end of may 17:30:53 q+ 17:31:09 ianh: we can check, but I think we're hoping to avoid another f2f. 17:31:09 June 1 is only 7 weeks away now, and we need 8 weeks lead time. 17:31:12 ack pfps 17:31:14 q- 17:31:16 ... we can schedule one just in case 17:31:19 +1 to peter 17:31:23 pfps: let's not have another f2f 17:31:33 +1 17:31:33 +1 to peter 17:31:40 ... let's schedule an extended telecon (whole afternoon) instead 17:31:40 "virtual F2F" is the goofy name I've heard for that. 17:31:41 unless the f2f is in Europe :-) 17:31:57 ianh: it would be pretty tough to have another f2f at such short notice 17:32:07 q? 17:32:18 ... doind it by telecon is more economical with everyone's time 17:32:22 q? 17:32:31 q? 17:32:43 topic: (Technical) Issues Arising 17:32:52 zakim, mute me 17:32:52 sorry, alanr, I do not know which phone connection belongs to you 17:33:00 q? 17:33:08 subtopic: negative property assertions (in RL) 17:33:14 zakim, who is here? 17:33:14 On the phone I see Peter_Patel-Schneider, msmith, bcuencagrau (muted), bijan, +1.603.897.aadd, christine, IanH, MarkusK_, Ivan, Sandro, baojie, bmotik (muted), uli (muted), JeffP, 17:33:17 ... Evan_Wallace, Rinke (muted), sebastian, schneid, Jonathan_Rees 17:33:18 On IRC I see alanr, schneid, ivan_, ewallace, baojie, bmotik, uli, MarkusK_, christine, JeffP, Zhe, IanH, bcuencagrau, sebastian, Rinke, pfps, msmith, RRSAgent, Zakim, bijan, 17:33:21 ... sandro, trackbot 17:33:33 q? 17:33:35 zakim, Jonathan_Rees is alanr 17:33:35 +alanr; got it 17:33:38 Ciao, everyone. Back to RIF F2F. 17:33:41 zakim, mute me 17:33:41 alanr should now be muted 17:33:44 yes! 17:33:47 -Sandro 17:33:56 jeffp: last telecon we discussed n.p.a.'s in RL. I did some investigation and I think it boils down to syntactic sugar. 17:34:21 ... jos's comment was about if such syntactic sugar is appropriate 17:34:25 q? 17:34:30 pointer, please 17:34:41 pointer to what? 17:34:42 q+ to answer to Jeff that 'we have learned from OWL lite that leaving out syntactic sugar from a profile is bad' 17:34:46 ... jjc's email laid out why the syntactic sugar is problematic 17:34:49 jeremy fears an idea he calls "negative triples" - whatever this is 17:35:02 q+ 17:35:13 It's harmless, it was requested, add it 17:35:18 zakim, unmute me 17:35:18 uli should no longer be muted 17:35:19 ack uli 17:35:19 uli, you wanted to answer to Jeff that 'we have learned from OWL lite that leaving out syntactic sugar from a profile is bad' 17:35:26 q+ 17:35:41 -bijan 17:35:46 Zakim, unmute me 17:35:46 bmotik should no longer be muted 17:36:02 q+ 17:36:05 ack bmotik 17:36:11 uli: one design principle for all profiles is that if something can be expressed indirectly, it can be expressed directly. i.e., so each profile is maximal in a certain sense. 17:36:38 bmotik: jjc is wrong, there is no problem with the RDF. we either have it in the language or not. 17:36:58 ... in RL it is *not* syntactic sugar, they can't be expressed in other ways 17:37:02 q+ 17:37:05 jjc's message is http://lists.w3.org/Archives/Public/public-owl-comments/2009Jan/att-0051/index.html 17:37:13 +??P1 17:37:16 ack JeffP 17:37:19 zakim, ??p1 is me 17:37:19 +bijan; got it 17:37:58 jeffp: bmotik's point that it is not syntactic sugar in RL is important 17:38:01 q+ 17:38:06 q+ to ask what the problem is 17:38:17 ... folks at HP Bristol confirmed jjc's claim that the RDF will be problematic 17:38:29 ianh: do you have any better information about what the problem is? 17:38:40 clarification: do we talk about negative property or negative class assertions? 17:38:57 q- 17:38:58 This is not correct. 17:39:06 jeffp: if you have negative property assertions, you are negating triples, which is not specified in RDF 17:39:16 Negative property assertions are accompanied by a set of semantic conditions just like any other construct. 17:39:20 There is *no* problem here. 17:39:21 ack bijan 17:39:24 ... we need an agreement with the RDF working group 17:39:59 q? 17:40:09 q+ 17:40:10 q+ 17:40:10 bijan: that argument doesn't make sense because there are alternative encodings. the encoding we're using is intention revealing 17:40:10 q+ to say that functional properties already permits negative triples 17:40:15 q? 17:40:47 ianh: how long should we discuss this given that we're unlikely to change this now? 17:41:03 ianh: we voted for them to be in already. 17:41:04 q+ 17:41:07 no will from me to chuck them out. 17:41:08 Absolutely not! 17:41:27 q? 17:41:34 jeffp: I think we voted that they were in, unless I found problems. This is a problem. 17:41:42 bijan: I disagree, this is not a new problem. 17:41:48 It's not a problem! 17:41:52 q? 17:41:56 Jeff, where exactly/technically is the problem? 17:42:05 zakim, unmute me 17:42:05 alanr should no longer be muted 17:42:06 A problem would be that it wouldn't be implementable on a rules system 17:42:12 let's straw poll on "at risk"! 17:42:14 ianh: I agree with bijan, it would take massive changes to revise current decision 17:42:18 That was explicitly the issue raised last time 17:42:52 Let's work off the queue first. 17:42:56 alanr: we can straw poll specifically for at risk, to solicit comments just for n.p.a. 17:43:05 q? 17:43:07 q- 17:43:08 q- 17:43:13 we heard that the jena team things there is a problem for their implementation - so at risk seems reasonable 17:43:24 q? 17:43:27 (i don't think there is a problem in jena) 17:43:31 But we don't know what the problem is 17:43:36 I'm very skeptical about the report 17:43:44 schneid, "thinks" that there is a problem is different from 'has found a problem'! 17:43:45 +1 to boris 17:43:50 +1 to boris 17:43:54 +1 to boris 17:44:02 -Ivan 17:44:10 q? 17:44:10 note that functional properties have exactly the same effect as negative property assertions 17:44:17 ack bmotik 17:44:20 we lost ivan 17:44:20 bmotik: all of this is fabricated. we are not negating parts of rdf graphs. the statements are positive and accompanied by a set of semantic conditions. I don't see a need to further discussion or vote. 17:44:20 q- 17:44:28 ack ivan_+ 17:44:37 ack ivan_ 17:44:52 +1 to Boris 17:44:59 ivan has joined #owl 17:45:03 Jeff, who asked for this? 17:45:08 ianh: jeffp, are you suggesting removal from OWL 2 or OWL 2 RL? 17:45:12 q+ to ask if jeff is going to lie in the road 17:45:18 q? 17:45:18 But it would still be in full right? 17:45:23 jeffp: just OWL 2 RL, which is considered more RDF friendly 17:45:27 q? 17:45:30 ack bijan 17:45:30 bijan, you wanted to ask if jeff is going to lie in the road 17:45:34 q? 17:45:35 zakim, dial ivan-voip 17:45:35 ok, ivan; the call is being made 17:45:35 +Ivan 17:45:55 q? 17:45:58 bijan: I think jeff would need to file a formal objection at this point. 17:46:25 +1 to Ivan's understanding 17:46:31 q+ 17:46:38 q? 17:46:43 ivan: I think this discussion is not specific to RL. JJC's comment is about n.p.a. in general. 17:47:00 ianh: I agree, jjc was talking about n.p.a in OWL 2 17:47:15 q+ to oppose at risking! 17:47:23 q? 17:47:27 I really don't see a need for an "at risk" label. We should not emasculate the spec because some people have fixations. 17:47:30 ivan: I support making it at risk to get additional feedback. if jjc is the only negative feedback, we can move on 17:47:37 I strongly oppose an "at risk" label. 17:47:41 +1 to bmotik 17:47:54 +1 to bmotik 17:47:55 +1 to boris 17:47:58 q? 17:48:01 msmith: I also oppose "at risk" label 17:48:02 I thought "at Risk" targets to CR ? 17:48:08 ack JeffP 17:48:42 q+ 17:48:42 jeffp: to ivan, jjc's comment is whole spec, but n.p.a is also in RL. I proposed removing it just from RL. 17:48:57 q? 17:49:00 In the RL rules it is simply: NPA(s p o) + s p o = false 17:49:05 ack bijan 17:49:05 bijan, you wanted to oppose at risking! 17:49:12 q? 17:49:22 ianh: ok, it's acceptable to comment on decision from last week. less acceptable to revisit long standing decisions 17:49:35 q? 17:49:37 I *strongly* oppose labeling any part of the spec with "at risk" for exactly the reasons that Bijan mentions now. 17:49:45 bijan: I oppose "at risk" because there is not a technical problem with supporting it. 17:49:50 q? 17:50:00 zakim, mute me 17:50:00 schneid should now be muted 17:50:02 ... I think an "at risk" label would punt a difficult decision that we should make now. 17:50:04 ack ivan 17:50:23 +1000 to Ivan 17:50:33 ivan: I don't understand why focusing on RL would make any difference. I added these rules to my RL implementation this afternoon and they were trivial 17:50:39 we are talking about existing RDF APIs but not just one implementation 17:50:47 ianh: we're going to do some polls 17:51:01 JeffP, there's no change to any api 17:51:04 STRAWPOLL: we mark as "at risk" negative property assertions in general 17:51:08 -1 17:51:09 -1000000 17:51:09 msmith: -1 17:51:10 0 17:51:10 -1 17:51:11 -1 17:51:12 -1 17:51:13 -1 17:51:13 0 17:51:13 +0.5 17:51:16 0 17:51:17 -1 17:51:18 +1 17:51:19 -1 17:51:19 -1 17:51:20 -1 17:51:25 -1 17:51:51 zakim, mute me 17:51:51 alanr should now be muted 17:52:03 ianh: jeffp, this vote is in conflict with your previous comment that you were only concerned with RL 17:52:12 -1 17:52:12 jeffp: I misread the vote, make it -1 17:52:37 ivan: I will not push for "at risk" in general 17:52:37 ivan, but you just implemented them?! 17:52:44 STRAWPOLL: we mark as "at risk" negative property assertions in RL profile 17:52:51 -1 17:52:52 -1 17:52:52 -1E72 (this time shorter) 17:52:55 -1 17:52:56 -1 17:52:56 -1 17:52:57 0 17:52:57 -1 17:52:58 -1 17:52:58 -1 17:52:59 -1 17:53:00 0 17:53:00 0 17:53:01 +1 17:53:01 0 17:53:07 0 17:53:42 ianh: jeffp, are you lying in the road? 17:53:55 q+ 17:53:56 jeffp: I will stick to my opinion 17:53:59 q? 17:54:00 q+ 17:54:00 Jeff should formally object if he wants 17:54:10 q? 17:54:15 ack bijan 17:54:18 ianh: you can formally object I guess? 17:54:38 bijan: I don't think he can object to it being "at risk", he can object to it being in the language 17:54:47 q? 17:54:51 ack alanr 17:55:17 q+ 17:55:20 +q 17:55:33 q? 17:55:45 ack bijan 17:56:00 alanr: I don't see that much down side to saying it is at risk in RL. I don't think many people in the WG are thinking about RL and jeff is, that should be noted. 17:56:15 I didn't hear that. He wants it at risk. 17:56:19 that's what's on the table. 17:56:31 q? 17:56:37 alanr, he said that 17:56:40 ack bmotik 17:56:43 bijan: I don't think jeff is in a privileged position, many of us are thinking about RL. he is not advocating for at risk, he is advocating for removal. 17:57:00 q+ 17:57:08 +1 to bmotik, again! 17:57:09 +1 to Boris, again; there is no problem, it's done, let's keep it 17:57:15 q? 17:57:21 ack JeffP 17:57:23 bmotik: there is no implementation problem. 17:57:27 q+ 17:57:38 q? 17:57:41 if the problem really really is RDF-compatibility, then not including it in RL, but including it in Full is really nonsensical 17:57:55 jeffp: the problem is not implementation, it is with compatibility. we should hear from people building RDF APIs, an area about which we're not experts 17:58:00 JeffP, the problem is _not_ with RL... (in my view) 17:58:01 I've build RDF apis 17:58:06 I've contribtuted to them 17:58:09 q? 17:58:12 q_ 17:58:13 q- 17:58:28 ianh: I don't think we can propose to overturn previous decision. the only think is to decide if we mark at risk. 17:58:33 You can look at the design and see it has no effect on the RDF level 17:58:34 q? 17:58:43 q? 17:59:06 q+ 17:59:09 q? 17:59:15 I'll formally object to removing it! 17:59:18 What a strange belief 17:59:28 q? 17:59:31 q? 17:59:37 ack ivan 17:59:39 jeffp: I would like to remove it from RL altogether, if not mark it "at risk" 17:59:55 zakim, mute me 17:59:55 alanr should now be muted 18:00:05 Yes, you don't have to add a "addNegativeTriple" 18:00:06 q+ 18:00:12 Thus, no change to *any* rdf api 18:00:17 q? 18:00:24 ivan: if there is a problem with n.p.a. , the issue is not specific to RL. this is why I voted to make "at risk" in general 18:00:58 jeffp: if RDF people are going to support OWL 2, then OWL 2 RL will be their initial target. 18:01:02 IT ADDS NO EXPRESSIVE POWER 18:01:02 ivan: I agree. 18:01:13 and also no problem in OWL 2 Full: NPAs are expressible in OWL 1 Full 18:01:29 PROPOSAL: We will mark as "at risk" negative property assertions in OWL RL 18:01:31 -1 (I'll formally object to this decision if this goes through.) 18:01:34 -0.5 ALU 18:01:38 -1 18:01:40 -1 18:01:40 -1 18:01:41 -1 (FZI) 18:01:41 -1 (Manchester) 18:01:41 0 18:01:42 0 18:01:42 0 18:01:43 -1 18:01:43 0 18:01:45 -1 (Amsterdam) 18:01:45 +1 (Aberdeen) 18:01:45 0 18:01:49 0 18:02:26 ok 18:02:39 ianh: jeff, are you satisfied that we've exhausted this issue 18:02:51 indeed - can get comments at lc and cr 18:03:02 +10000 to Ian 18:03:04 Yes, Jeff - please do explain this clearly! 18:03:11 I will try 18:03:14 thanks 18:03:36 q? 18:03:44 ack JeffP 18:03:48 topic: test cases 18:03:58 q+ perhaps discuss syntax translation test criteria? 18:04:13 +1 to default approval of test cases 18:04:16 q+ to perhaps discuss syntax translation test criteria? 18:04:23 ianh: previous approval procedure required action. I think we should switch to defaul approval of test cases 18:04:24 q? 18:04:28 ack alanr 18:04:29 alanr, you wanted to perhaps discuss syntax translation test criteria? 18:04:32 ... or someone could notice a structural problem with a test 18:04:33 q? 18:05:08 q+ 18:05:12 alanr: the only unresolved issue regarding tests was criteria for translation tests. should we discuss this now? 18:05:15 q? 18:05:17 Umm, bi-entailment does not actually check that the models are the same 18:05:27 ... clarification on default. what would be subject to default? 18:05:33 Syntax translation should be in terms of..e.r..syntax, thus structure,yes? 18:05:38 q+ to comment on default approval 18:05:42 ok. pfps - what would the test be? 18:05:42 zakim, unmute me 18:05:42 uli was not muted, uli 18:05:44 ack uli 18:06:20 uli: regarding syntax translation criteria, we can't test model equivalence because you would need to run infinite tests 18:06:29 q? 18:06:32 alanr: so we have statement in RDF mapping that is untestable? 18:06:35 It's demonstratable 18:06:45 uli: yes, but untestable is different from demonstrable 18:06:50 we have lots of untestable stuff in our documents - most of the theorems are "untestable" 18:06:59 But you can't check it in specific cases 18:07:03 Mechanically 18:07:04 q? 18:07:06 uli: if you had such a test, you can test the implementation of a translator 18:07:45 The mappings presented in this document are backwards-compatible with that of OWL 1 DL: every OWL 1 DL ontology encoded as an RDF graph can be mapped into a valid OWL 2 DL ontology using the mapping from Section 3 such that the resulting OWL 2 DL ontology has exactly the same set of models as the original OWL 1 DL ontology 18:07:49 ack msmith 18:07:49 msmith, you wanted to comment on default approval 18:07:50 zakim, mute me 18:07:51 uli should now be muted 18:08:12 sure, let's do this by email 18:08:33 q? 18:08:38 ianh: uli was saying there are properties that exist which we can't necessarily test. 18:08:45 alanr: I will follow-up on email. 18:08:48 sure 18:09:01 zakim, mute me 18:09:01 alanr should now be muted 18:09:02 q? 18:09:47 q+ 18:09:48 q? 18:09:59 ack bmotik 18:10:00 msmith: I think we should have some quick oversight before approval. 18:10:09 bmotik: I don't want default approval. 18:10:21 ... one or two tools should pass test before approval 18:10:22 had to step away from phone - back now 18:10:30 q? 18:10:52 bmotik: suggestion, two tools should pass the test. then default approval. 18:11:03 q+ 18:11:07 ... then the whole test ssuite should be run periodically. 18:11:11 ianh: what is status 18:11:15 q? 18:11:21 q+ 18:11:27 +1 to some intermediate status 18:11:44 ack alanr 18:12:11 alanr: this sounds fine. there should be a mechanism for tests that fail to be approved. 18:12:52 ianh: yes, I was thinking 3 statuses. no state. reasonable. approved. 18:12:56 ack msmith 18:12:59 q+ 18:13:35 q? 18:13:36 submitted, proposed, approved-default, approved-explicit, rejected-explicit 18:14:03 +1 to Mike 18:14:06 ack alanr 18:14:13 +1 to Mike 18:14:22 q+ 18:14:25 msmith: the test framework can support this process. 18:14:45 q+ to say that approved-default is more likely to be correct than approved-explicit 18:14:50 alanr: we need an easy way to see approved default vs. approved by wg action 18:14:56 ack pfps 18:14:56 pfps, you wanted to say that approved-default is more likely to be correct than approved-explicit 18:15:17 q? 18:15:25 alanr: we also need support for submitted tests that are never satisfied by tools. what happens then? 18:15:34 q? 18:15:39 q+ 18:16:01 ack bijan 18:16:48 q? 18:16:52 bijan: tests that are wrong will get resolved by the tools. 18:16:58 q? 18:17:05 +1 on "too-hard" tests according to bijan 18:17:10 +1 to Mike's suggestion 18:17:14 ... perhaps a new category for tests that no one will pass 18:17:36 q? 18:17:51 ianh: we're all pretty much in agreement with "ready for testing" status 18:18:16 q? 18:18:32 yes, I would like primer examples, when primer is stablized to become test cases 18:18:35 q? 18:18:53 q+ 18:18:59 ack msmith 18:20:11 jj 18:20:16 msmith: There was an open issue on how to organize tests that use the same input but produce different outcomes for direct semantics and RDF-based semantics. This is solved now and we can handle this. 18:20:23 msmith: we can clean up test cases on future agendas 18:20:27 ianh: agreed. 18:20:29 bye bye 18:20:29 thanks, bye 18:20:29 -bijan 18:20:29 bye 18:20:30 we can talk about grddl 18:20:30 thanks Ian! 18:20:32 -Evan_Wallace 18:20:33 bye 18:20:33 thanks, bye! 18:20:33 - +1.603.897.aadd 18:20:34 -JeffP 18:20:37 -alanr 18:20:39 -MarkusK_ 18:20:39 -bmotik 18:20:39 sorry 18:20:40 -IanH 18:20:41 -bcuencagrau 18:20:43 bye 18:20:43 -baojie 18:20:45 -sebastian 18:20:46 -uli 18:20:46 -Rinke 18:20:50 -Ivan 18:20:52 ivan has left #owl 18:20:52 -christine 18:20:52 -schneid 18:20:58 RRSAgent, make records public 18:21:14 thanks ian 18:21:16 -Peter_Patel-Schneider 18:21:17 Thanks Mike for scribing! 18:21:18 bye 18:21:22 msmith has left #owl 19:04:31 uli has left #owl 19:35:01 disconnecting the lone participant, msmith, in SW_OWL()1:00PM 19:35:05 SW_OWL()1:00PM has ended 19:35:06 Attendees were Peter_Patel-Schneider, +1.202.408.aaaa, msmith, +86528aabb, bijan, +2, +1.603.897.aadd, bcuencagrau, IanH, Rinke, MarkusK_, Ivan, Sandro, +1.518.276.aaee, christine, 19:35:08 ... baojie, uli, +22427aaff, Alan_Ruttenberg, JeffP, Evan_Wallace, bmotik, sebastian, schneid, alanr 20:37:44 Zakim has left #owl 22:59:01 IanH has joined #owl 23:08:10 IanH_ has joined #owl