16:45:50 RRSAgent has joined #owl 16:45:50 logging to http://www.w3.org/2008/09/03-owl-irc 16:46:26 IanH has changed the topic to: http://www.w3.org/2007/OWL/wiki/Teleconference.2008.09.03/Agenda 16:46:50 Zakim, this will be owlwg 16:46:50 ok, IanH; I see SW_OWL()1:00PM scheduled to start in 14 minutes 16:47:03 RRSAgent, make records public 16:55:24 uli has joined #owl 16:56:15 msmith has joined #owl 16:58:07 SW_OWL()1:00PM has now started 16:58:12 +msmith 16:58:15 +Peter_Patel-Schneider 16:58:39 pfps has joined #owl 16:59:24 + +0190827aaaa 16:59:28 zakim, aaaa is me 16:59:28 +MartinD; got it 16:59:32 +??P4 16:59:35 zakim, mute me 16:59:35 MartinD should now be muted 16:59:40 zakim, ??P4 is me 16:59:40 +uli; got it 16:59:44 zakim, mute me 16:59:44 uli should now be muted 16:59:55 scribenick uli 16:59:56 sandro has joined #owl 17:00:04 bcuencagrau has joined #owl 17:00:36 JeffP has joined #owl 17:00:39 scribenick: uli 17:00:44 +IanH 17:00:57 zakim, who is here? 17:00:57 On the phone I see Peter_Patel-Schneider, msmith, MartinD (muted), uli (muted), IanH 17:01:00 On IRC I see JeffP, bcuencagrau, sandro, pfps, msmith, uli, RRSAgent, Zakim, IanH, bmotik, MartinD, ewallace, trackbot 17:01:06 +Sandro 17:01:10 ScribeNick: uli 17:01:15 ivan has joined #owl 17:01:40 +??P13 17:01:44 Zakim, ??P13 is me 17:01:44 +bcuencagrau; got it 17:02:01 zakim, who is here? 17:02:01 On the phone I see Peter_Patel-Schneider, msmith, MartinD (muted), uli (muted), IanH, Sandro, bcuencagrau 17:02:03 On IRC I see ivan, JeffP, bcuencagrau, sandro, pfps, msmith, uli, RRSAgent, Zakim, IanH, bmotik, MartinD, ewallace, trackbot 17:02:05 +StuartTaylor 17:02:16 +??P15 17:02:16 zakim, StuartTaylor is me 17:02:17 +JeffP; got it 17:02:22 Zakim. ??P15 is me 17:02:26 Zakim, ??P15 is me 17:02:26 +bmotik; got it 17:02:32 Zakim, mute me 17:02:32 bmotik should now be muted 17:02:34 zakim, who is here? 17:02:34 On the phone I see Peter_Patel-Schneider, msmith, MartinD (muted), uli (muted), IanH, Sandro, bcuencagrau, JeffP, bmotik (muted) 17:02:36 On IRC I see ivan, JeffP, bcuencagrau, sandro, pfps, msmith, uli, RRSAgent, Zakim, IanH, bmotik, MartinD, ewallace, trackbot 17:02:59 zakim, code? 17:02:59 the conference code is 69594 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), ivan 17:02:59 sure 17:03:04 baojie has joined #owl 17:03:07 Zhe has joined #owl 17:03:29 Topic: Agenda Amendments 17:03:34 none 17:03:44 +Danny 17:03:48 Topic: Previous minutes 17:03:50 zakim, Danny is ivan 17:03:50 +ivan; got it 17:03:51 +baojie 17:03:54 minutes look fine to me 17:04:18 IanH: minutes accepted 17:04:22 +Zhe 17:04:27 zakim, mute me 17:04:27 Zhe should now be muted 17:04:33 Topic: Pending actions 17:04:43 q+ 17:04:55 q? 17:04:59 ack pfps 17:05:35 pfps: action 182 and 183 have emty bodies 17:05:41 q? 17:05:44 s/emty/empty 17:05:58 IanH: something should be done 17:05:59 +q 17:06:11 pfps: or we say now that they are done 17:06:37 IanH: we agree that action 182 and 183 are done, even though their bodies are empty 17:06:48 q? 17:06:58 ack baojie 17:07:09 baojie: there is an incomplete version on the wiki 17:07:35 IanH: asks for a pointer to this version 17:07:42 q? 17:07:42 q+ 17:08:03 I will run down the corridor and remind bijan 17:08:32 A incomplete pdf of Quick Reference Guide: http://www.w3.org/2007/OWL/wiki/Image:Owl2-refcard_2008-08-19.pdf 17:08:40 s/A/An 17:08:47 back! 17:08:57 i think so 17:09:13 IanH: action 150 17:09:22 q? 17:09:28 q- 17:09:34 baojie: we have come to a conclusion, so it should be done 17:09:52 http://lists.w3.org/Archives/Public/public-owl-wg/2008Sep/0019.html 17:10:02 ...we changed the ?? specification 17:10:42 IanH: can you come forward with a proposal re. internationalized string? 17:10:44 q+ 17:10:50 Zakim, unmute me 17:10:50 bmotik should no longer be muted 17:10:58 q? 17:11:07 ack bmotik 17:11:18 bmotik: I think there is a draft with the basics 17:11:24 preliminary spec: http://www.w3.org/2007/OWL/wiki/InternationalizedStringSpec 17:11:45 m_schnei has joined #owl 17:11:56 what is the status of the wiki page, and what should happen to it? 17:12:01 IanH: who take care of looking at this spec and see how we modify ours? 17:12:06 q? 17:12:15 q+ 17:12:17 ACTION: bmotik to modify OWL spec accordingly 17:12:17 Sorry, couldn't find user - bmotik 17:12:25 +??P21 17:12:28 ACTION: bmotik2 to modify OWL spec accordingly 17:12:28 Created ACTION-206 - Modify OWL spec accordingly [on Boris Motik - due 2008-09-10]. 17:12:36 zakim, ??P21 is me 17:12:36 +m_schnei; got it 17:12:40 zakim, mute me 17:12:40 m_schnei should now be muted 17:12:41 q+ 17:12:43 q? 17:12:45 Zakim, mute me 17:12:45 bcuencagrau should now be muted 17:12:53 pfps: it would be odd if, in our spec, we would point to a wiki page 17:13:16 sandro: we could publsih the (content of) wiki as a working draft 17:13:32 IanH: as a RIF or as an OWL publication? 17:13:34 can be a joined 17:13:35 q? 17:13:41 sandro: I think it's OKAY as long we're only making the reference from a WD (pre-LC). Maybe we should make it a WD? 17:13:42 ack bmotik 17:13:43 q+ 17:14:17 q? 17:14:19 ack ivan 17:14:28 bmotik: we make the draft a WD and then reference it 17:14:54 q? 17:15:04 ivan: I had a look at this and it looks as if its publication shouldn't cause any problems. 17:15:18 ivan: we can even have a joint RIF/OWL publication 17:15:44 bparsia has joined #owl 17:16:04 ACTION: sandro to take this publication plan forward 17:16:04 Created ACTION-207 - Take this publication plan forward [on Sandro Hawke - due 2008-09-10]. 17:16:21 (I chose sandro already - he said 'yes' first) 17:16:26 wellcome, ivan 17:16:35 +??P22 17:16:46 zakim, ??p22 is me 17:16:46 +bparsia; got it 17:16:50 zakim, mute me 17:16:50 bparsia should now be muted 17:16:57 q+ 17:17:02 q? 17:17:03 IanH: action 192 re. UNA and OWL QL has been done as seen in an email 17:17:07 ack msmith 17:17:14 msmith: yes, we can close that one 17:17:29 The consensus should result in a discussion / resolution agenda item for next week. 17:17:44 q? 17:17:54 IanH: action 202 must wait for next week, as must 172 17:18:09 IanH: I will chase Achille re. 172 17:18:13 I've had no action joy this week 17:18:32 IanH: action 168 has been on for some time 17:18:37 q? 17:18:41 zakim, unmute me 17:18:41 bparsia should no longer be muted 17:18:59 q+ 17:19:05 q? 17:19:20 zakim, mute me 17:19:20 bparsia should now be muted 17:19:24 q? 17:19:25 zakim, unmute me 17:19:25 uli should no longer be muted 17:19:29 ack uli 17:20:07 works for me! 17:20:23 zakim, unmute me 17:20:23 bparsia should no longer be muted 17:20:27 q? 17:20:38 bparsia: have done some testing, am waiting for Robert 17:21:01 uli: perhaps we should see whether there is some w3c official route and not bother Robert 17:21:23 bparsia: there are some easy problems, e.g., diagrams not alt-ed correctly 17:21:33 q? 17:21:49 sandro: doesn't know of official w3c 'route' 17:22:15 bparsia: we could do a proper accessibility audit 17:22:32 IanH: so action 168 remains on you? 17:22:46 zakim, mute me 17:22:46 bparsia should now be muted 17:22:52 bparsia: couldn't we move it to a general "to-do" list? 17:22:56 IanH: ok, will do 17:22:58 agreed 17:23:01 q? 17:23:14 works for me 17:23:15 IanH: action 170 is mooted by events 17:23:33 q? 17:23:34 IanH: action 174? 17:23:37 zakim, unmute me 17:23:37 bparsia should no longer be muted 17:23:52 zakim, mute me 17:23:52 bparsia should now be muted 17:23:53 bparsia: actually yes, bit also might be mooted shortly 17:23:58 yep 17:24:08 IanH: ok, so we move it by 1 week 17:24:17 Topic: Reviewing 17:24:26 IanH: I saw already some reviews 17:24:32 yes, thanks for the reviews so far! 17:24:37 ...anybody else? 17:24:40 perhaps the review page could be updated as reviews come in? 17:24:47 ...reviews are due on september 8, in 5 days 17:24:52 Zakim, mute me 17:24:52 bmotik should now be muted 17:24:57 q? 17:25:00 I just muted me 17:25:04 zakim, mute me 17:25:04 uli should now be muted 17:25:08 myself 17:25:45 IanH: a slight problem with the profiles document, other docs should be able to be reviewed by september 8 17:25:58 q+ 17:26:11 q? 17:26:16 IanH: the SKOS people have their SKOS reference out for last call 17:26:34 pfps: I have already produced a review for the SKOS semantics document 17:26:48 IanH: and this is different from the reference? 17:26:49 only the SKOS ref is in LC 17:26:58 http://www.w3.org/TR/skos-reference 17:27:02 SKOS Reference 17:27:14 q? 17:27:15 pfps: forget - I meant powder! 17:27:19 ack pfps 17:27:38 q+ 17:27:42 IanH: so, volunteers to review LC draft for SKOS reference? 17:27:42 -1 17:27:43 zakim, unmute me 17:27:43 m_schnei should no longer be muted 17:28:15 zakim, mute me 17:28:15 m_schnei should now be muted 17:28:18 m_schnei: I started to do a personal look-through, but only with OWL full glasses on, and would prefer to keep it that way 17:28:23 I could try 17:28:23 +q 17:28:25 q+ 17:28:26 IanH: anybody else? 17:28:40 ack m_schnei 17:28:43 q- 17:28:51 ack ivan 17:28:56 ivan: the major issue is related to the annotation discussion -- where are we with ours? 17:29:08 q? 17:29:14 but does skos refer to owl 2 at all? 17:29:43 Ivan: all the rest isn't really complicated, but we should check on issues around annotations 17:30:07 IanH: ok, I will send emails around to likely suspects 17:30:15 IanH: F2F4 17:30:18 true, skos:related and skos:broaderTransitive are intended to be disjoint properties 17:30:30 Topic: F2F4 17:30:49 IanH: you need to book early if you want to profit from special rate 17:31:17 i found a hotel for about 70EUR in the neighbourhood :) 17:31:29 sandro: 'special rate' is insane, I suggest to look around in the neighbourhood 17:31:47 IanH: or you can look around on the internet? 17:32:11 sandro: but then you don't contribute to the meeting room rates 17:32:38 http://www.w3.org/2007/OWL/wiki/F2F4_People 17:32:40 IanH: and don't forget to register to TPAC 17:32:49 s/insane/shockling high, esp in US$/ 17:33:06 sandro, we can remove all the above 17:33:32 http://www.w3.org/2002/09/wbs/35125/TPAC2008/ 17:33:33 Perhaps a link to tpac from the f2f4 page? 17:33:35 REGISTER HERE: http://www.w3.org/2002/09/wbs/35125/TPAC2008/ 17:33:39 there is a link on the wiki page, too 17:34:07 Topic: Issues 17:34:54 Ian: Issue 131, 141 and 130 seem to be related, a bit more to discuss on 130. 17:34:56 q? 17:35:10 q+ 17:35:14 zakim, unmute me 17:35:14 m_schnei was not muted, m_schnei 17:35:16 ...but with the drafts we have in the wiki, perhaps we can resolve 131 and 141 17:35:54 m_schnei: I am perfectly happy with proposal for 116 17:36:11 zakim, mute me 17:36:11 m_schnei should now be muted 17:36:24 IanH: any other opinions? 17:36:38 q+ 17:36:42 q? 17:36:44 q- 17:36:45 zakim, unmute me 17:36:45 Zhe should no longer be muted 17:36:52 IanH: I have discussed this earlier with Alan, and he seems ok 17:37:02 i can't hear you, Zhe 17:37:29 q? 17:37:36 ack zhe 17:37:37 I thought we are waiting for RPI's response on unification idea 17:37:48 Zhe: I didn't follow this discussion closely 17:38:00 s/Zhe/Jie/g 17:38:37 +1 to move forward and let people react 17:38:38 IanH: I have discussed these with Jim, and seems to be fine and he will review the document anyway. 17:38:39 reasonable 17:38:53 sorry, Zhe, baojie, I couldn't tell who was talking 17:39:04 np 17:39:14 Uli: was me 17:39:59 from my notes "Alan: Close issue-131 by saying we're happy with the current structure of Profiles. There's one semantics for OWL RL, which the OWL Full semantics...." 17:40:22 PROPOSED: resolve issue 131 and 116 as per Ian's email http://lists.w3.org/Archives/Public/public-owl-wg/2008Aug/0288.html 17:40:35 +1 17:40:40 +1 17:40:41 +1 17:40:46 Sandro: we're still haggling about conformance, which is no longer connected here. 17:40:56 thanks, sandro 17:41:13 +1 (FZI) 17:41:33 +1 (ALU) 17:41:35 +1 17:41:49 we could be more precise saying "under 1 in Ian's email" 17:41:57 +1 (with us being clear that CONFORMANCE is not addressed here) 17:42:01 +1 17:42:04 +1 17:42:06 +1 17:42:16 +1 17:42:16 +1 17:42:22 +1 17:42:28 RESOLVED: resolve issue 131 and 116 as per Ian's email http://lists.w3.org/Archives/Public/public-owl-wg/2008Aug/0288.html 17:42:28 +1 17:43:09 s/and 116/ 17:43:21 q? 17:43:24 IanH: can we have a similar resolution wrt 116? 17:43:53 PROPOSED: resolve issue 116 as per Ian's email http://lists.w3.org/Archives/Public/public-owl-wg/2008Aug/0288.html 17:44:01 +1 17:44:02 +1 17:44:09 +1 17:44:11 :-) 17:44:29 :-) 17:44:35 this just makes the point that we really really resolved it 17:44:53 IanH: rules generating literals in subject position 17:45:06 Q? 17:45:10 q? 17:45:12 IanH: issue 141 17:45:13 q+ 17:45:24 ack zhe 17:45:28 IanH: this is already made clear in the document 17:45:57 not predicate but subject position 17:46:08 Zhe: just to make sure: if this "literal in subject position" happens, what do we do? 17:46:42 IanH: the rule sets works on a generalization of triples 17:46:46 q? 17:47:09 Zhe: what is the best approach to avoid generation of "illegal rfd triples"? 17:47:32 They are triples but not RDF triples 17:47:39 IanH: we already say in the spec that these are "generalized" triples, so this is ok 17:47:53 ...and you won't see these since you can't ask for them 17:48:03 q+ 17:48:05 Zhe: I see - so I guess it's fine 17:48:11 q? 17:48:13 http://www.w3.org/TR/rif-rdf-owl/#End_Notes 17:48:14 ack ivan 17:48:19 ivan: editorial 17:48:28 As far as the basic conformance is concerned, there is no way to tell if the system is generating these generalized triples. 17:48:50 ...the above is a note regarding the same problem which could be added to the document 17:49:08 one implication is that you get with generalized triples every entailment which you got before (without) 17:49:12 q? 17:49:44 PROPOSED: resolve issue 141 as per Peter's email http://lists.w3.org/Archives/Public/public-owl-wg/2008Aug/0203.html 17:49:46 +1, surprise :-) 17:49:46 +1 17:49:48 +1 17:49:48 +1 17:49:49 +1 17:49:50 +1 17:49:52 +1 17:49:54 +1 17:49:54 +1 (FZI) 17:49:58 +1 17:50:03 +1 17:50:06 +1 17:50:34 +1 17:50:38 +1 17:51:03 RESOLVED: resolve issue 141 as per Peter's email http://lists.w3.org/Archives/Public/public-owl-wg/2008Aug/0203.html 17:51:22 q? 17:51:33 q? 17:51:35 IanH: for issue 130, we have a proposal http://www.w3.org/2007/OWL/wiki/Conformance 17:51:39 q? 17:51:49 q+ 17:51:53 q? 17:52:05 IanH: so, can we resolve it like this next week? 17:52:06 Zakim, mute me 17:52:06 bmotik was already muted, bmotik 17:52:52 sandro: I still see the issue that Michael raised, and I would like a simple solution to this 17:52:56 q? 17:52:59 sandro, which problem is this? 17:53:04 q+ 17:53:08 ack sandro 17:53:45 ack sandro 17:54:04 IanH: perhaps sandro has overlooked the precise meaning of this, i.e., that reasoners cannot flip flop between answers 17:54:28 zakim, unmute me 17:54:28 m_schnei should no longer be muted 17:54:29 sandro: perhaps the problem isn't so bad 17:54:32 q? 17:54:38 ack m_schnei 17:54:47 m_schnei: all I wanted with my remark was to explicate this 17:54:51 q? 17:54:54 m_schnei, what? 17:55:12 m_schnei: I just wanted it documented 17:55:32 q? 17:55:37 m_schnei: I want to clarify that I just want to have this conformance behaviour made explicit, I do *not* deny this 17:55:59 IanH: we should say that, all conformant systems should always agree on their answer 17:56:17 sandro: what about negative entailments? 17:56:32 ...do we need another reasoner for this? 17:56:37 q? 17:56:53 q? 17:57:15 q? 17:57:26 you cannot always say from "false" that the converse is true, in particular not under OWA 17:57:36 q? 17:57:39 sandro: oracle wasn't interested in negative/theorem 1 checks 17:57:50 Sandro: Are people going to implement the theorem-1 check? 17:57:53 Zhe: flexibility for user is a good thing 17:58:30 Zhe: it will be difficult to tell which rules are bottleneck, so theorem 1 check could be useful 17:58:51 q? 17:58:57 Zhe: I don't know yet what exactly we will implement, but we may implement it 17:59:28 SHOULD! 17:59:28 IanH: for the test, should we strengthen 'may' to 'should'? 17:59:34 q? 17:59:37 q+ 17:59:58 ack ivan 18:00:18 q? 18:00:27 I'll call at MUST 18:00:33 ivan: I would prefer 'may' since otherwise the implementor load is too high 18:01:04 zakim, unmute me 18:01:04 sorry, bijan, I do not know which phone connection belongs to you 18:01:14 q+ 18:01:16 q+ 18:01:17 sandro: we shouldn't allow reasoners to say 'false' unless it's really false 18:01:19 q? 18:01:36 zakim, unmute me 18:01:36 bparsia should no longer be muted 18:01:39 zhe, even if you only implement a /partial/ /forward/ chainer, then you have an implicit entailment checker: just look in the resulting inference graph and only say "yes", if some entailment is in, and say "no" otherwise 18:01:39 ...call that part 'must' and otherwise, use 'unknown' 18:01:42 +1 to sandro's must proposal 18:02:03 sandro: How about you MUST do theorem-1 checking before returning FALSE, BUT you can return UNKNOWN if you don't want to do that checking. 18:02:27 zakim, mute me 18:02:27 bparsia should now be muted 18:02:38 bparsia: I like sandro's suggestion - having this check available will enhance interoperability, and the 'unknown' option is a good compromise 18:02:57 q? 18:03:03 ack bparsia 18:03:12 ack ivan 18:03:16 IanH: but if we change to "must", then we must explain what implementors could do who wouldn't want to implement the test 18:03:42 sandro: absolutely -- we need text here which makes sense to people without thinking it all through at this level. 18:03:54 q? 18:03:57 q? 18:04:03 ivan: from Zhe's presentation in Manchester, how would the 'must' work with this? 18:04:04 q+ 18:04:35 IanH: tricky since we talk about entailments, but we are also interested in queries 18:04:36 q? 18:04:44 ack zhe 18:04:52 ...so a false is then a 'no, it's really not in the query' 18:04:55 Ian: in real life, people do query answering. so the "false" is kind of like not answering the query. 18:05:22 Zhe: I would prefer 'may' since 'should' or 'must' would be a burden 18:05:41 IanH: but sandro's proposal also allow you to return 'unknown' 18:06:08 ...and this gives us more honesty: 'false' really means false! 18:06:14 q? 18:06:15 q+ 18:06:28 (to answer this) 18:06:32 zakim, unmute me 18:06:32 bparsia was not muted, bparsia 18:06:36 q? 18:06:36 Zhe: but in a forward chaining system, where could be return such an 'unknown'? 18:06:39 ack bparsia 18:06:48 ack bparsia 18:07:14 bparsia: on load time, or in the query 18:07:15 q? 18:07:39 sandro: so, user asks query 'q', and didn't get a certain result 18:08:07 ...does this mean that rules couldn't find this result or that it shouldn't be in answer? 18:08:10 q? 18:08:14 q+ 18:08:26 Zhe: but how would 'unknown' be helpful there? 18:08:27 q? 18:09:07 sandro: on query results, systems should include a flag saying whether complete reasoning was done or not. that's the equivalent of this false/unknown thing in the conformance definition. 18:09:09 bparsia: with SPARQL owl, i looked at racerPro and Sher, and there it is important as well to have a mechanism to indicate to the user how complete you are 18:09:24 zakim, unmute me 18:09:24 m_schnei was not muted, m_schnei 18:09:24 q? 18:09:29 zakim, mute me 18:09:29 bparsia should now be muted 18:09:34 ack m_schnei 18:09:38 q? 18:10:05 m_schnei, I can't understand you 18:10:52 m_schnei: you have to at least implement the full ruleset, and have it not FOL entailed, before you can return FALSE 18:10:55 heavy breathing 18:11:14 (I have a response to m_schnei, but .... maybe I'll save it.) 18:11:45 q? 18:11:51 IanH: using 'unknown' would be a mechanism to indicate to the user that the results to a query may be partial 18:12:06 Zhe: i don't see the additional valie 18:12:10 s/valie/value 18:12:26 q+ 18:12:31 q? 18:12:33 IanH: it prevents implementors from having unsound systems and calling them conformant 18:12:34 m_schnei: you are only allowed to say "False", if the entailment does not exist w.r.t. the /complete/ ruleset. so the NULL reasoner is not allowed. An implementer MAY go beyond the whole ruleset, up to the complete full semantics 18:13:03 zakim, unmute me 18:13:03 bparsia should no longer be muted 18:13:17 sandro: I would like to have a flag that distinguishes complete from incomplete reasoners 18:13:40 sandro: but can any OWL RL rule implementation ever be conformant? 18:13:53 the /ruleset/ is the lower bound of RL conformance 18:13:58 q? 18:14:08 IanH: sure - they are *sound*, we only talk about non-entailments, cases where things are *not* returned 18:14:16 q? 18:14:19 ack bparsia 18:14:25 sandro: and then you could use theorem 1 to find complete cases 18:14:31 btw, if the ruleset entails something, then you can savely say "True", because then OWL Full would produce the same entailment 18:14:49 ian: Theorem 1 gives you the completeness guarantee -- it says that if the ontology looks like this, complete-rule-reasoning is complete-ontology-reasoning. 18:15:08 bparsia: users from bioontology really value complete reasoning, and so we should be able to signal this 18:15:35 q+ 18:15:37 zakim, mute me 18:15:37 bparsia should now be muted 18:15:39 q? 18:15:41 IanH: let's take the discussion on-line, implement the suggested modifications and discuss next week 18:15:57 q+ to ask if query answering should be covered in Conformance 18:16:07 q- ivan 18:16:12 ivan: i would still like to see the consequences for an implementation being written down 18:16:27 q? 18:16:32 ack sandro 18:16:32 sandro, you wanted to ask if query answering should be covered in Conformance 18:16:47 q+ 18:17:01 sandro: let's write it down - but where do we write about query answering? In the conformance document? 18:17:04 ack zhe 18:17:21 I'd be open to flagging it as "depeding on implementor feedback" 18:17:33 I'd rather have the stronger and weaken, then do the weaker and then strengthen 18:18:02 IanH: the tricky bit is the dependency between profiles and conformance 18:18:04 zakim, unmute me 18:18:04 bparsia should no longer be muted 18:18:10 q? 18:18:28 ...we can't review profiles before we fixed conformance 18:18:53 zakim, mute me 18:18:53 bparsia should now be muted 18:19:03 bparsia: why don't we make conformance really strict (so that poking holes in it is easier) and then review them together 18:19:07 q? 18:19:16 sandro: who updates the draft? 18:19:38 ACTION: IanH to update the conformance document with 'unkown' 18:19:38 Sorry, couldn't find user - IanH 18:20:12 q? 18:20:29 zakim, unmute me 18:20:29 bparsia should no longer be muted 18:20:31 I already saw the distinct "ox" namespace in the POWDER semantics ;-) 18:21:07 Topic: Issue 109 18:21:22 q? 18:21:36 bparsia: it would be good to not have to change namespaces 18:22:11 q? 18:22:22 sandro: can we have a pointer to this 18:22:26 zakim, mute me 18:22:26 bparsia should now be muted 18:22:59 q+ 18:23:01 Zakim, unmute me 18:23:01 bmotik should no longer be muted 18:23:03 Topic: issue 138 18:23:06 ack bmotik 18:23:28 q+ 18:23:29 q+ 18:23:29 Zakim, mute me 18:23:30 q? 18:23:30 bmotik: let's use owl:datetime since the datatype is different from the xsd one 18:23:31 bmotik should now be muted 18:23:32 +1 to boris 18:23:58 ivan: [procedural] didn't we want to ask xsd people about that? 18:24:23 IanH: didn't sandro want to edit this message from peter? 18:24:36 Sandro sent a message, but didn't ask for any action. 18:24:53 I'm willing to edit the document, I guess. 18:25:07 ?? 18:25:16 q? 18:25:19 IanH: I observe confusion -- pfps, can you edit the mail and send it? 18:25:25 ...to make it more punchy? 18:25:27 ack ivan 18:25:39 sandro: it should say more clearly what they should do. 18:25:42 q? 18:25:52 q? 18:26:08 q? 18:26:09 IanH: would their answer have any influence of what we do about datetime namespace 18:26:13 ack msmith 18:26:49 msmith: bmotik convinced me that xsd and owl datetime are really different, so perhaps we don't need to waste time by asking them? 18:26:52 +1 18:26:52 q? 18:27:01 It already is owl:dateTime. 18:27:02 q? 18:27:05 +epsilon 18:27:07 IanH: so msmith suggest to just go ahead with owl:datetime? 18:27:17 I used owl:dateTime in anticipation of this discussion. There is an editorial comment about it. 18:27:24 OK by me 18:27:30 ivan: we should keep the issue open, but use owl:datetime 18:27:40 q+ 18:27:43 Zakim, unmute me 18:27:43 bmotik should no longer be muted 18:27:44 q? 18:27:49 ack bmotik 18:27:49 ack bmotik 18:28:04 Zakim, mute me 18:28:04 bmotik should now be muted 18:28:21 +1 18:28:23 bmotik: we already use owl:datetime, so we can't do anything else on this now 18:28:33 IanH; AOB? 18:28:33 q+ 18:28:41 q? 18:28:47 ack Zhe 18:28:54 Zhe: i want to open an issue about base triples? 18:29:16 IanH: you raised it, and it is now open, and we can discuss this next week 18:29:24 IanH: AOB? 18:29:28 thanks, bye 18:29:32 -bmotik 18:29:33 bye 18:29:33 meeting is closed, thanks 18:29:33 -msmith 18:29:35 bye 18:29:36 -JeffP 18:29:37 -Peter_Patel-Schneider 18:29:37 -Zhe 18:29:37 msmith has left #owl 18:29:38 -bparsia 18:29:39 -bcuencagrau 18:29:40 -IanH 18:29:41 -uli 18:29:41 -baojie 18:29:41 thanks, Ian. :-) 18:29:43 -ivan 18:29:49 -m_schnei 18:29:51 -MartinD 18:29:57 MartinD has left #OWL 18:30:04 sandro, ivan, can you please invoke the magic command? 18:30:18 Ian is good at it these days. 18:30:32 Ian, could you please invoke the magic command? 18:31:06 I did it already 18:31:10 at the beginning 18:31:16 ah, thanks! 18:31:35 If you look at the scribe conventions page you will see what you have to do next :-) 18:31:59 Let me know if you need help. 18:32:03 oups - didn't know it moved there 18:32:31 It tells you how to convert the chat log into minutes using Sandro's new software tool 18:33:20 The magic command that I issues was to make the chat log public 18:34:21 Wrong Credential 18:34:21 ...the irc log says: "Sorry, a password is required" 18:34:37 and "Sorry, Insufficient Access Privileges" 18:59:40 ivan has left #owl 18:59:53 -Sandro 18:59:55 SW_OWL()1:00PM has ended 18:59:56 Attendees were msmith, Peter_Patel-Schneider, +0190827aaaa, MartinD, uli, IanH, Sandro, bcuencagrau, JeffP, bmotik, ivan, baojie, Zhe, m_schnei, bparsia 19:00:48 RRSAgent, pointer? 19:00:48 See http://www.w3.org/2008/09/03-owl-irc#T19-00-48 19:01:05 Sorry, Uli. Back now. Still stuck? 19:33:44 I sorted it. 19:34:26 And sent Uli an email. 19:50:20 thanks 20:31:19 Zakim has left #owl 21:00:03 alanr has joined #owl 21:07:39 alanr has left #owl 21:09:17 alanr has joined #owl