16:59:55 RRSAgent has joined #owl 16:59:55 logging to http://www.w3.org/2008/06/11-owl-irc 16:59:55 bmotik, you need to end that query with '?' 17:00:01 Zakim, who is here? 17:00:01 On the phone I see IanH, bmotik (muted) 17:00:02 On IRC I see RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, trackbot 17:00:06 Thanks! 17:00:16 uli has joined #owl 17:00:32 zakim, dial ivan-voip 17:00:36 ok, ivan; the call is being made 17:00:39 +Ivan 17:00:40 +Evan_Wallace 17:00:44 msmith has joined #owl 17:00:47 +??P4 17:00:54 zakim, who is here? 17:00:54 On the phone I see IanH, bmotik (muted), Ivan, Evan_Wallace, ??P4 17:00:55 On IRC I see msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, trackbot 17:01:10 +??P5 17:01:13 zakim, ??P5 is me 17:01:13 +uli; got it 17:01:20 zakim, mute me 17:01:20 uli should now be muted 17:01:24 +msmith 17:01:36 RRSAgent, pointer? 17:01:36 See http://www.w3.org/2008/06/11-owl-irc#T17-01-36 17:01:41 Peter, are you there and ready to scribe? 17:01:45 bcuencagrau has joined #owl 17:01:46 +Sandro 17:01:47 calvanese has joined #owl 17:01:55 zakim, who is here? 17:01:55 On the phone I see IanH, bmotik (muted), Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro 17:01:57 On IRC I see calvanese, bcuencagrau, msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, trackbot 17:02:04 sandro: what is "pointer" 17:02:29 ewallace, it's the URL for where things are being logged at this point. 17:02:38 cool 17:02:43 RRSAgent, make log public 17:03:07 ok,. I can scribe 17:03:35 ok, fine 17:03:37 +??P13 17:03:43 scribenick MarkusK 17:03:45 scribenick: MarkusK 17:03:47 Zakim, ??P13 is me 17:03:47 +bcuencagrau; got it 17:04:00 scribe: Markus 17:04:05 +calvanese 17:04:14 zakim, who is here? 17:04:14 On the phone I see IanH, bmotik (muted), Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau, calvanese 17:04:16 On IRC I see calvanese, bcuencagrau, msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, trackbot 17:04:25 zakim, mute me 17:04:25 calvanese should now be muted 17:04:29 Who has the machine that goes "ping"? 17:04:34 +Alan_Ruttenberg 17:04:48 no agenda amendments 17:04:54 +[IBM] 17:05:08 Previous minutes 17:05:09 oops, i'm here now 17:05:15 +Peter_Patel-Schneider 17:05:20 Achille has joined #owl 17:05:30 Zakim, IBM is me 17:05:30 +Achille; got it 17:06:02 they aren't pretty 17:06:05 the previous minutes were not acceptable yesterday 17:06:07 Ian: can someone apprve previous minutes 17:06:11 Zhe has joined #owl 17:06:22 msmith has changed the topic to: http://www.w3.org/2007/OWL/wiki/Teleconference.2008.06.11/Agenda 17:06:24 JeffP has joined #owl 17:06:33 Ian: Minutes may need new mechanism to be prepared 17:06:46 Sandro: the old partial minutes have confused people 17:06:54 http://www.w3.org/2007/OWL/wiki/Chatlog_2008-06-04 17:07:02 zakim, mute me 17:07:02 bcuencagrau should now be muted 17:07:05 (link to unformatted minutes) 17:07:31 Sandro: the scribe should edit the IRC log and it should be reformatted later on request 17:07:36 no fixes were performed on the minutes at all - 17:07:59 + +1.603.438.aaaa 17:08:01 what is "the right place"? 17:08:03 Ian: previous minutes cannot be accepted yet since not many people saw the final version 17:08:13 Zakim, +1.603.438.aaaa is me 17:08:13 +Zhe; got it 17:08:18 q? 17:08:55 Ian: registration for F2F3 still should be completed 17:09:06 Topic: Action item review 17:09:07 topic: Pending Review Actions 17:09:14 sorry 17:09:25 you're welcome to assist :-) 17:09:50 q? 17:09:58 Achille: Review of RDF mapping document completed last week 17:10:11 JeffPan has joined #owl 17:10:13 ... found them to be OK, though primer still needs to be updated 17:10:21 Ian - today is 11 June, *not* 4 June! 17:10:28 q+ 17:10:29 ... my only point was in the syntax document 17:10:33 -Alan_Ruttenberg 17:10:37 q? 17:11:34 Ian: the above refered to Action 148, which was still open, though not menitioned in the agenda 17:11:43 +jar 17:11:48 q? 17:11:52 s/menitioned/mentioned/ 17:11:59 ack pfps 17:12:04 Ian: Action 148 completed 17:12:23 ... Boris' Action 131 shall be deferred until later 17:12:24 +??P8 17:12:31 bijan has joined #owl 17:12:39 +qhreul 17:12:41 Ian: Action 42 (Bijan) 17:12:44 alanr has joined #owl 17:12:50 zakim, qhreul is me 17:12:50 +JeffPan; got it 17:13:11 Bijan: Action is ongoing, I hope to have it done by next week 17:13:36 Ian: Action 147 (Michael) 17:13:45 ... a detailed review was provided 17:14:00 zakim, who is here? 17:14:00 On the phone I see IanH, bmotik (muted), Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau (muted), calvanese (muted), Achille, Peter_Patel-Schneider, Zhe, jar, 17:14:03 ... ??P8, JeffPan 17:14:04 On IRC I see alanr, bijan, JeffPan, JeffP, Zhe, Achille, calvanese, bcuencagrau, msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, trackbot 17:14:05 ... Michael is not on the call to comment 17:14:20 Zakim, unmute me 17:14:20 bmotik should no longer be muted 17:14:44 q? 17:14:53 Boris: I did look at Michael's review, though without checking all details 17:14:53 zakim, who is here? 17:14:53 On the phone I see IanH, bmotik, Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau (muted), calvanese (muted), Achille, Peter_Patel-Schneider, Zhe, jar, ??P8, 17:14:56 ... JeffPan 17:14:57 On IRC I see alanr, bijan, JeffPan, JeffP, Zhe, Achille, calvanese, bcuencagrau, msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, trackbot 17:15:29 ... the points appear to be minor suggestions for the most part, and I will try to implement the easy comments first 17:15:45 Zakim, mute me 17:15:45 bmotik should now be muted 17:15:47 ... I wil come back with any non-obvious comments for further discussion 17:15:53 s/wil/will/ 17:16:14 +1 17:16:19 Ian: then let us close Action 147 for the moment 17:16:25 m_schnei has joined #owl 17:16:27 zakim, jar is alanr 17:16:27 +alanr; got it 17:16:41 I htink that's me 17:16:43 zakim, who is here? 17:16:44 On the phone I see IanH, bmotik (muted), Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau (muted), calvanese (muted), Achille, Peter_Patel-Schneider, Zhe, 17:16:47 ... alanr, ??P8, JeffPan 17:16:48 On IRC I see m_schnei, alanr, bijan, JeffPan, JeffP, Zhe, Achille, calvanese, bcuencagrau, msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, 17:16:50 ... trackbot 17:16:52 zakim, ??P8 is me 17:16:52 +bijan; got it 17:16:57 Ian: ??P8 and jar are unidentified participants who must be identified 17:16:57 sorry, today only IRC 17:17:10 zakim, who is here? 17:17:10 On the phone I see IanH, bmotik (muted), Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau (muted), calvanese (muted), Achille, Peter_Patel-Schneider, Zhe, 17:17:13 ... alanr, bijan, JeffPan 17:17:13 Bijan: I fixed it 17:17:14 On IRC I see m_schnei, alanr, bijan, JeffPan, JeffP, Zhe, Achille, calvanese, bcuencagrau, msmith, uli, RRSAgent, MarkusK, ivan, ewallace, IanH, pfps, Zakim, bmotik, sandro, 17:17:16 ... trackbot 17:17:22 zakim, mute me 17:17:22 bijan should now be muted 17:17:34 Ian: Action 150 (Jie Bao) 17:17:43 q? 17:17:48 ... Jie Bao is not here to comment 17:17:56 ... so Action remains open until next week 17:18:11 action 147 is finished 17:18:11 Sorry, couldn't find user - 147 17:18:20 Topic: Issues 17:18:34 i have finished action 147 17:18:38 Zakim, unmute me 17:18:38 bmotik should no longer be muted 17:18:46 Ian: Issue 104 appeared to be a rather obvious fix for the OWL Full semantics 17:19:04 i have just sent a mail regarding 104 17:19:05 q? 17:19:14 Boris: yes, we can change the mapping to address that issue 17:19:22 clu has joined #owl 17:20:00 Ian: so we can propose to resolve Issue 104 17:20:19 104 or 124? 17:20:21 PROPOSED: Resolve Issue 124 as per http://www.w3.org/mid/0EF30CAA69519C4CB91D01481AEA06A096B434@judith.fzi.de 17:20:28 +1 17:20:32 +1 17:20:36 +1 17:20:37 +1 17:20:39 s/104/124/ 17:20:40 +1 17:20:42 0 (sorry, not up to speed on issue) 17:20:46 +1 17:20:47 0 17:20:49 +1 17:20:50 +1 17:20:52 +1 17:20:55 +1 17:20:56 +1 17:21:03 +??P1 17:21:09 zakim, ??p1 is me 17:21:09 +clu; got it 17:21:12 RESOLVED: esolve Issue 124 as per http://www.w3.org/mid/0EF30CAA69519C4CB91D01481AEA06A096B434@judith.fzi.de 17:21:13 zakim, mute me 17:21:13 clu should now be muted 17:21:17 Sorry for being late. 17:21:20 s/esolve/resolve/ 17:21:46 Ian: Issue 104 was discussed in many emails 17:21:54 q? 17:21:59 ... many people raised concerns 17:22:06 q+ 17:22:10 Zakim, unmute me 17:22:10 bmotik was not muted, bmotik 17:22:45 zakim, unmute me 17:22:45 bijan should no longer be muted 17:23:02 Boris: one issue is that reification and collections are the only ones that make sense to take out of the reserved vocabulary 17:23:10 zakim, mute me 17:23:10 bijan should now be muted 17:23:46 ... I send a proposal for having a shadow-vocabulary for OWL, but this met little approval 17:23:52 the proposal was to define our own terminology for the serialization 17:23:58 q+ 17:24:02 ack bmotik 17:24:16 ... the technical problem is that we have no ObjectProperty/DatatypeProperty puning 17:24:21 q? 17:24:44 we need not assign a type in the language - leave it to the modeler 17:24:45 ... hence vocabulary like rdf:first are not easy to define in OWL: one would have to asign a fixed type 17:24:58 s/asign/assign/ 17:25:14 ... rdf:first may then get many types in different applications and I propose to not allow it in OWL DL vocabulary 17:25:15 Or a shadow vocabualry 17:25:19 q? 17:25:43 AlanR: there were various proposals to address this 17:26:02 bijan has joined #owl 17:26:17 ... one was to have an OWL shadow vocabulary, such as owl:first, to resolve possible typing conflicts 17:26:20 in my mail I argue for not treat lists at all in OWL DL, so people may declare it to be either a data or a object property, if they wish 17:26:32 q+ 17:26:33 ... the other proposal was to admit rdf:first and leave typing to modellers 17:26:37 ack alanr 17:26:42 q? 17:26:50 ack bmotik 17:26:52 rdf:first would then be just an URI like any other 17:26:56 ... one would then need to use OWL Full if conflicting types for collection properties would occur 17:27:01 why? 17:27:12 q+ to ask what use case shadow vocab addresses 17:27:34 q? 17:27:37 "messy" is subjective 17:27:41 Boris: I do think that having an explicit type for rdf:first would be no good modelling practice 17:27:51 q+ 17:27:53 then owl full 17:27:59 a shadow vocabulary for lists can be used /always/ by users - no need to say anything about it 17:28:04 ... ontologies should not contain declarations for such properties, and I would rather like to not have it 17:28:14 Subjective considerations aren't invalid (as we've seen :)) 17:28:15 q+ 17:28:20 ack msmith 17:28:20 msmith, you wanted to ask what use case shadow vocab addresses 17:28:37 shadow was for internal use 17:28:38 Interop 17:28:47 q? 17:28:52 MSmith: I do not agree with Boris: I would allow users to define types for rd:type 17:29:01 yes 17:29:02 ... I see no use case for a shadow vocabulary though 17:29:05 yes 17:29:07 q+ 17:29:15 reverse mapping 17:29:18 fixes this 17:29:31 not 17:29:35 ack ivan 17:29:36 The first scribing above is the opposite of what I intended to say. I agree with Boris exactly. 17:29:50 billions and billions 17:29:53 yes 17:29:54 served 17:29:56 Oh, sorry! 17:30:11 Please fix this, I misheard you 17:30:15 By the way, I have just fixed the mapping document regarding owl:datatypeComplementOf. 17:30:19 Ivan: Existing OWL ontologies may already use RDF constructs, so it is not clear that we even have an option for disallowing that now in OWL 2 17:30:22 q+ 17:30:24 q? 17:30:25 q+ 17:30:31 ack alanr 17:30:35 thank you, I will verify the correct version is in the minutes 17:30:52 AlanR: the shadow vocabulary would be for our own serialisation, not for users 17:31:06 q? 17:31:21 ... restricting uses of rdf:first in a certain way may still be better than not allowing it at all 17:32:17 I am now confused about the intended use of the "shadow vocabulary" 17:32:18 q? 17:32:32 msmith: you are not the only one:-) 17:32:58 ack bmotik 17:33:05 idea is that we use owl:first, owl:next owl:nil in our serialization 17:33:29 Boris: switching from RDF lists to something else in serialisation seems to be no good idea 17:33:30 +1 to boris 17:33:34 q? 17:33:41 ... many ontologies are also already using RDF lists 17:33:54 I'd like the backwards compatibility case spelled out clearly, please 17:34:01 ... I think it is not a major backward compatibility issue 17:34:07 I think mike was looking for the utility of the shadow vocabulary 17:34:15 I wonder that so many people can't understand mike :) 17:34:59 q? 17:35:25 Boris: I proposed the shadow vocabulary, so that users are freed of some burdon reinventing vocabulary for standard tasks 17:35:29 can't introduce it to the rdfs users - they are the ones that we want to bring in to the fold 17:35:38 +1 again to Boris 17:35:41 ... but the drawback is that we get into modelling discussions here 17:35:42 q? 17:35:59 ... we cannot really reason about lists logically 17:36:09 q+ to say we are *not* getting in to modeing. We are getting out of the way of modelers. 17:36:13 q? 17:36:23 no no 17:36:29 we are trying to let more rdf be owl 17:36:34 ... the list is just a part of data, not a true semantic construct 17:36:41 they can all be defined as annotation properties if need be 17:36:41 zakim, unmute me 17:36:41 bijan should no longer be muted 17:36:43 q? 17:36:47 ack bijan 17:37:12 Bijan: I second Boris' concern on the lack of utility of the list vocabulary 17:37:29 this is clearly getting in to the modeling business - we think it is bad modeling, so we will forbid it? 17:37:43 ... I often suggest to users to not employ RDF collections or containers in OWL ontologies 17:37:47 q? 17:38:10 do i understand this right? rdf:first as an annotation property? and if a reasoner throws away all annotations? then there are a lot of unconnected nodes around. :) 17:38:11 ... in our practical experience, users were willing to use a custom vocabulary to model lists 17:38:28 Alan, we will prohibit the usage of rdf:List for technical reasons that are not negligible. People can model lists using their own vocabulary if they want. 17:38:41 ... it is usually easy to migrate RDF lists to some custom vocabulary 17:38:44 q? 17:38:47 I don't see the technical reasons as being very much 17:38:51 ack pfps 17:38:57 just not convinced 17:39:06 "seeing" is subjective :) 17:39:15 what about promoting a standard list vocabulary? 17:39:37 Pfps: Where exactly are RDF lists used in OWL ontologies 17:39:41 (owl:ObjectList and owl:DataList, etc.... ) 17:39:43 if it can be done unambiguously then great! 17:39:47 Ivan: mostly in the serialisation of OWL 17:39:48 sandro, without proper list semantics? 17:39:55 no, with. 17:40:00 What is the proper list semantics? 17:40:02 q? 17:40:06 Now we're out of first order logic at least 17:40:07 Lists cannot be modeled semantically! 17:40:08 there are no rdf lists customly used in OWL DL, since this is not allowed :) 17:40:18 Yes, in FOL, T meant. 17:40:19 Since normally lists are well founded and defined with transitive closure 17:40:23 q? 17:40:27 any ontology that uses owl2:first is owl 2 17:40:28 s/T meant/I meant 17:40:45 every ontology that is owl2 is serialized with mention of owl2:first 17:40:51 the times I have seen lists in OWL, the type of items is also restricted, which would require specializing any "standard" shadow vocabulary 17:40:54 :-) 17:41:13 q+ 17:41:19 ack alanr 17:41:19 alanr, you wanted to say we are *not* getting in to modeing. We are getting out of the way of modelers. 17:41:22 q? 17:41:51 Alanr: I do not think that we truly need to use a shadow vocabulary 17:42:21 ... a shadow vocabulary would be closed, hence one can check for occurrences of this vocabulary to decide if a serialisation belongs to OWL 2 17:42:32 http://www.daml.org/services/owl-s/1.1/generic/ObjectList.owl 17:42:40 if you don't use owl2 vocabulary but do use lists in an object sense, are you in owl1 then? 17:42:56 q? 17:43:08 q+ to support Alan 17:43:10 q+ 17:43:15 michael is not here, he supports 17:43:18 markus? 17:43:26 ... OWL should allow lists as data, since people adopt them due to their syntactic shortness in Turtle and SPARQL 17:43:35 q+ 17:43:36 q? 17:44:14 zakim, unmute me 17:44:14 bijan was not muted, bijan 17:44:17 AlanR: Michael may also support my position, but is not on the call 17:44:18 q? 17:44:34 ... I am certainly not convinced by the current arguments against it 17:44:53 I have not voiced any oppinion on this issue, I am scribing 17:45:05 sorry - my mistake 17:45:11 zakim, mute me 17:45:11 bijan should now be muted 17:45:59 http://bibliontology.com/ 17:46:05 +1 to Sandro's suggestion 17:46:10 exactly 17:46:22 Sandro: can we have a straw poll to get some impression here? 17:46:37 alanr, what part of that ontology? 17:46:37 Michael: q? 17:46:42 q? 17:46:43 q? 17:46:43 ... at least to measure general motivation in the group 17:46:50 hunting - discussion was in email 17:46:54 q- 17:46:58 Ian: still some speakers on the queue first 17:47:15 http://bibliontology.com/#term_contributorList 17:47:18 q? 17:47:39 Boris: the technical questions seem to be rather severe 17:47:49 ... changing the vocabulary is not a trivial change 17:47:49 Sandro: proposed strawpoll: It would be nice, if we can find a workable technical solution, to support RDF List in OWL DL. 17:48:26 q? 17:48:33 q- 17:48:34 ack bmotik 17:48:38 zakim, unmute me 17:48:38 bijan should no longer be muted 17:48:42 ack bijan 17:48:46 ... using things like rdf:first in conjunction with OWL constructs like nominals may have unexpected/complex consequences both in OWL DL and OWL Full 17:49:08 Could we get documentation on how Pellet accomodates? 17:49:18 in owl full, there isn't any restriction on the use of rdf:first, anyway 17:49:35 See the code :) 17:49:39 Bijan: I see a user need for expressing lists, but we can leave it to implementors and future work to properly solve that 17:50:02 STRAWPOLL: It would be nice, if we can find a workable technical solution, to support RDF List in OWL DL. 17:50:11 yes, will check code, but if you could give a hint, that would be greatly appreciated ;-) 17:50:13 +1 17:50:15 +1 17:50:16 That's the straw poll? 17:50:22 +1 it would be nice. it doesn't seem feasible 17:50:24 +1 17:50:25 +1 17:50:26 0- 17:50:28 +1, in the same sense that it would be nice to have rules, self-knowledge, etc., etc. 17:50:31 +1 (would be nice, but no shaddow vocab) 17:50:35 +0 17:50:35 +1 would be nice 17:50:37 +1 would be nice... 17:50:37 +1 but not too optimistic 17:50:41 +1 it would be nice, but I strongly doubt we can solve this 17:50:43 +1 to transmutation 17:50:46 0 17:50:49 +0 but I wouldn't mind free puppies either 17:50:49 0 17:51:08 who is going to bell this cat? 17:51:13 Er... if someone wants to , they should do so 17:51:14 Can we get a list of issues to start? 17:51:15 Sandro: maybe a follow-up straw poll on the amount of resources to invest in the issue would be useful 17:51:30 alanr, re: code, I don't know off hand 17:51:43 for me, the question is, whether we can just say /nothing/ about RDF Lists, and it would work 17:51:44 I will volunteer if Michael (S) will 17:52:08 S == Schneider 17:52:11 Ian: are there volunteers for trying to solve the problem? 17:52:13 (sm) 17:52:22 I don't know what to volunteer for, but if it sounds good, I will do it ;-) 17:52:22 I can talk to you about Pellet 17:52:36 please say in irc, alan! 17:52:56 yes 17:52:56 Ian: AlanR and MSchneider to pursue the issue 17:53:15 Alanr: I will start by compiling a list of concerns that were raised so far 17:53:47 action: Alan to work with M_schnei to collect, propose how to address issues in making rdf list vocabulary 17:53:47 Created ACTION-159 - Work with M_schnei to collect, propose how to address issues in making rdf list vocabulary [on Alan Ruttenberg - due 2008-06-18]. 17:53:57 nary! 17:54:14 q? 17:54:16 ok, people, I need to stop for about 15 minutes. my battery is down. sorry! 17:54:18 Ian: discussion on "at risk" features such as EasyKeys 17:54:23 bye for now! 17:54:24 q? 17:54:57 ... especially regarding whether or not such features should appear in the spec with an appropraite disclaimer 17:55:03 q? 17:55:08 q+ 17:55:14 zakim, unmute me 17:55:14 bijan was not muted, bijan 17:55:15 Ian: Any comments? 17:55:25 q? 17:55:29 ack bijan 17:56:12 Bijan: Many discussions are not finished yet at the current state, and we still need to gather more information. 17:56:16 q? 17:56:30 q+ 17:56:44 ... We need to decide on the current status of each feature, and we can add our concerns to the spec to gather feedback. 17:57:05 http://www.w3.org/2007/OWL/wiki/Easy_Keys#Spec_Proposal 17:57:09 +1 Bijan add them now, no need for "At Risk" 17:57:18 q? 17:57:24 ack bmotik 17:57:25 Bijan: "At risk" comments are not problem, I would like the features to be in the spec in general 17:57:46 q+ to mention spec work 17:57:48 Boris: I do not like to add feartures to the spec now that we may remove later on 17:57:50 q? 17:58:06 ack bijan 17:58:06 bijan, you wanted to mention spec work 17:58:15 ... I would prefer to first do some investigations, and then start modifying the spec 17:58:43 Bijan: For EasyKeys, extending the spec should not be hard, since the existing text is almost ready for use in the spec 17:59:08 ... I agree that implementation experiences are good, but adding the features to the spec would still further more feedback. 17:59:13 q? 17:59:23 Ian: do you consider the features to be modular? 17:59:41 Bijan: EasyKeys and Top/Bottom properties both seem to be modular. 17:59:48 Boris: I agree. 17:59:48 yep 17:59:53 Ian: Straw poll 18:00:07 zakim, mute me 18:00:08 bijan should now be muted 18:00:36 STRAWPOLL: easy keys and top and bottom roles should be added to spec with comment that they could be removed later if implementation experience is negative 18:00:37 My main comment is that it is not only the structural spec that changes: most of the documents will need to change. 18:00:45 But I can live with that 18:00:50 +1 18:00:57 +1 18:00:58 +1 18:00:59 +1 18:00:59 Boris, yes, I'm working on bits for rdf mapping and sematncis as well 18:01:00 +1 18:01:00 +1 18:01:00 +1 18:01:00 +1 18:01:01 +1 18:01:05 +1 18:01:05 +1 18:01:06 -0 18:01:09 0- 18:01:10 0 18:01:18 +0 18:01:28 is -0 = 0- ? 18:01:38 Frankly, we don't need a comment. 18:01:39 which can also be read as "is someone looking" 18:01:44 Ian: so it seems that it is OK for the group to add both with some comment 18:01:48 q+ 18:01:55 q? 18:02:07 A joint action? 18:02:08 Boris: Is that a resolution? Shall we have an action? 18:02:12 We'd need a resolution 18:02:17 Ian: I think so. 18:02:19 zakim, unmute me 18:02:19 bijan should no longer be muted 18:02:25 absolutely 18:02:40 q? 18:02:51 Bijan: we first need a resolution. 18:03:34 AlanR: we can also consider that again before the next publication. 18:03:34 RESOLVED: add easy keys and top and bottom roles to the spec; review when we get to next publication round 18:03:42 ACTION: bmotik2 to Add easy keys and Top and Bottom role to the spec 18:03:42 Created ACTION-160 - Add easy keys and Top and Bottom role to the spec [on Boris Motik - due 2008-06-18]. 18:03:49 +1 18:03:54 +1 18:03:55 +1 18:03:58 +1 18:04:00 +1 18:04:02 +1 18:04:05 +1 18:04:06 +1 18:04:09 +1 18:04:13 +1 18:04:21 +! 18:04:24 +1 18:04:28 s/RESOLVED/PROPOSED/ 18:04:29 +1 18:04:33 +0 18:04:34 +1 18:04:36 +1 18:04:42 RESOLVED: add easy keys and top and bottom roles to the spec; review when we get to next publication round 18:05:08 Ian: Issue 109 (XML namespace) 18:05:24 .. are there new technical arguments on that? 18:05:29 q? 18:05:33 pfff 18:05:36 -q 18:05:37 ack boris 18:05:41 ... or shall we just vote? 18:05:45 I do! 18:05:46 I do! 18:05:50 I do! 18:05:56 but I wrote it down 18:05:57 I do more! 18:06:03 I do! I do! (but not as much) 18:06:12 I care, but I do we have new arguments 18:06:26 AlanR: Ivan and Bijan might be able to reach an agreement. 18:06:49 Ivan: Bijan and I tried to compile all pros and cons to support the decision 18:07:16 http://lists.w3.org/Archives/Public/public-owl-wg/2008Jun/0031.html 18:07:42 i did 18:07:44 I did 18:07:44 Ian: The email is rather long, so we should give people the chance of reading the email 18:07:45 me 18:07:45 I did 18:07:49 me 18:07:59 I didn't. :-( 18:08:00 Michael did 18:08:01 I did not 18:08:03 I didn't 18:08:06 am reading it now 18:08:07 I didn't 18:08:16 I just did but didn't finish 18:08:18 Ian: Poll on who read the email and who did not. 18:08:29 action to all who haven't read it? 18:08:29 Sorry, couldn't find user - to 18:08:36 m_schnei has joined #owl 18:09:12 Ian: I will postpone that to next week, and every participant next week should be prepared to vote on that issue, i.e. should have read the email. 18:09:13 is BIJAN one of the options? 18:09:19 +[IPcaller] 18:09:23 Ivan did a good job with the email 18:09:24 bijan:someValuesFrom 18:09:41 zakim, [IPcaller] is me 18:09:41 +m_schnei; got it 18:09:45 zakim, mute me 18:09:45 m_schnei should now be muted 18:09:52 Ian: so the issue will be voted on next week 18:10:10 q? 18:10:32 q? 18:10:39 q? 18:10:45 +1 to resolve these issues 18:10:48 Ian: Issues 21 and 24 18:11:03 ... are we ready to try to resolve those? 18:11:16 q+ 18:11:20 q? 18:11:40 AlanR: I think we should announce it on the agenda for next week 18:12:01 24 reject, no inconsistencies 18:12:17 Pfps: when putting the issues on the agenda, the concrete proposals should be made explicit as well, especially for Issue 24 18:12:41 Ian: Alan and I will prepare a wording for both proposals 18:12:51 Ian: Issue 111 18:12:54 q+ 18:12:55 q+ 18:13:02 ... User intent signaling 18:13:05 q- 18:13:06 q? 18:13:11 zakim, who is on the call? 18:13:11 On the phone I see IanH, bmotik, Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau (muted), calvanese (muted), Achille, Peter_Patel-Schneider, Zhe, alanr, 18:13:14 ... bijan, JeffPan, clu (muted), m_schnei (muted) 18:13:15 ack alanr 18:13:20 q? 18:13:47 +q 18:13:53 q? 18:13:59 AlanR: I thought of the case where someone writes an ontology that needs to be interpreted correctly 18:14:03 PRESENT: IanH, bmotik, Ivan, Evan_Wallace, MarkusK, uli (muted), msmith, Sandro, bcuencagrau (muted), calvanese (muted), Achille, Peter_Patel-Schneider, Zhe, alanr, bijan, JeffPan, clu (muted), m_schnei (muted) 18:14:11 q? 18:14:27 ... the idea of "intents" is not so clear in some cases 18:14:35 zakim, unmute me 18:14:35 bijan was not muted, bijan 18:14:41 q? 18:14:46 ack bijan 18:14:58 ... the main use case I see is really when one requires specific conclusions to be drawn and specifies an intent for that. 18:15:16 Bijan: I raised this issue but would like to withdraw it now 18:15:35 Sandro, were you not concerned about this one too? 18:15:50 absolutely 18:15:59 ... I agree that the use of "intents" is not always clear 18:16:21 ... having intents in ontologies may eventually create more noise 18:16:49 Bijan: you can always do the work-around of including an OWL-full tautology in your DL, if you want to tell people it's OWL-Full. 18:17:09 one question is whether I must use wsdl for message 18:17:22 q? 18:17:30 q+ 18:17:31 Bijan: overall, the issue appears to get more complicated than first expected 18:17:47 zakim, mute me 18:17:47 bijan should now be muted 18:17:48 ... thus I propose to defer that until we may have more experiences 18:18:19 alanr, if not wsdl, some description, perhaps english 18:18:32 q? 18:18:36 ack bmotik 18:18:40 conventions might arise outside the WG, where people use an rdfs:comment on the ontology header which tells the profile 18:18:41 ack sandro 18:18:43 Insane? Moi? 18:18:53 zakim, unmute me 18:18:53 bijan should no longer be muted 18:19:22 q? 18:19:22 what about dl versus r? 18:19:22 q+ 18:19:46 q? 18:19:47 Not at the DL side 18:19:56 Sandro: there are non-entailments for OWL-R that are entailed by other OWL versions 18:20:12 Not at the OWL R DL side: if you're in OWL R DL, then the entailements coincide with OWL 2 DL 18:20:16 q? 18:20:26 OWL R Full is both a /syntactic/ AND a /semantic/ subset of Full 18:20:26 q? 18:20:36 q+ 18:20:37 Bijan: I thought that OWL-R would be a syntactic fragment that entails all consequences that the larger fragments would entail 18:20:48 we discussed this in detail at the last f2f 18:21:00 so patient... 18:21:01 Then I didn't understand it in detail at the last f2f 18:21:02 ... if it is not true for OWL-R Full, I would consider this a bug in OWL-R Full 18:21:06 I can 18:21:06 Are there examples? 18:21:31 q+ on explaining the difference 18:21:41 sounds good to me 18:22:00 q? 18:22:07 q+ on explaining OWL R Full vs. OWL Full 18:22:10 Ian: In OWL-R Full one can state arbitrary DL statements, on account of being "Full", but it would not entail the DL consequences 18:22:11 q+ explaining OWL R Full vs. OWL Full 18:22:12 zakim, unmute me 18:22:13 uli should no longer be muted 18:22:14 q? 18:22:30 Bijan: I would consider OWL-R Full to be broken then 18:22:31 q? 18:22:37 ack uli 18:22:47 Uli: there seems to be a misunderstanding 18:23:11 ... Sandro asked whether OWL Full ontologies should always signal this 18:23:35 what about owl-r full versus owl-full 18:23:39 q? 18:23:43 zakim, unmute me 18:23:43 m_schnei should no longer be muted 18:23:43 ... Bijan referred to the option of signalling OWL Full if this interpretation as OWL Full is considered crucial 18:23:45 zakim, mute me 18:23:45 uli should now be muted 18:23:50 q? 18:23:56 ack m_schnei 18:24:19 Michael: OWL-R Full still lacks some syntactic features of OWL Full 18:24:38 q+ to ask what syntactic features are missing in OWL-R Full 18:24:46 q? 18:24:53 q- 18:24:56 q? 18:25:04 ... I can give an example, but it is probably better to give it by email 18:25:17 Pfps: What is not in OWL-R Full 18:25:21 Obviously we don't have a claer understanding! 18:25:24 Michael: Nominals are not in? 18:25:45 Ian: Syntactically nominals are allowed 18:25:50 zakim, mute me 18:25:50 m_schnei should now be muted 18:25:52 The OWL-R Full specification is telling you what you are allowed to entail 18:26:03 Michael: Indeed 18:26:11 Any other business? 18:26:12 OWL R Full allows *all* RDF graphs, but does not provide any "extra" semantics for several constructs that are in OWL (even in OWL DL). 18:26:33 Eek! 18:26:34 yes, I was a bit confused at the moment :) 18:26:35 -Evan_Wallace 18:26:38 bye 18:26:39 That wasn't my undersatnding 18:26:40 -bmotik 18:26:41 bye, thanks all 18:26:41 -bcuencagrau 18:26:41 Adjourn 18:26:42 -Achille 18:26:43 -msmith 18:26:43 second peter 18:26:43 -JeffPan 18:26:45 bye 18:26:45 -Peter_Patel-Schneider 18:26:46 -IanH 18:26:46 bye 18:26:48 -Sandro 18:26:49 -uli 18:26:51 -calvanese 18:26:53 -Zhe 18:26:55 So the realtionship between owl dl and owl full is very much unlike that between owl-r dl and owl-r full! 18:27:00 So what exactly is the process for publishing minutes now? 18:27:01 Sandro, do we need to do anything for the minutes now. 18:27:04 -m_schnei 18:27:05 zakim, drop me 18:27:05 Ivan is being disconnected 18:27:06 -Ivan 18:27:09 calvanese has left #owl 18:27:10 or does it all happen by magic? 18:27:10 IanH, I'll talk to MarkusK about it. 18:27:12 alanr has left #owl 18:27:14 -clu 18:27:15 msmith has left #owl 18:27:22 OK -- thanks. 18:27:22 MarkusK, hold on a minute.... 18:27:25 ok 18:27:45 -alanr 18:27:50 -bijan 18:30:16 -MarkusK 18:30:17 SW_OWL()12:00PM has ended 18:30:19 Attendees were IanH, bmotik, Ivan, Evan_Wallace, MarkusK, uli, msmith, Sandro, bcuencagrau, calvanese, Alan_Ruttenberg, Peter_Patel-Schneider, Achille, Zhe, JeffPan, alanr, bijan, 18:30:21 ... clu, m_schnei 18:32:43 MarkusK, can I just e-mail you in a bit, when it's ready? 18:32:54 sure 18:33:22 bye 19:54:06 clu has joined #owl 20:35:33 Zakim has left #owl 20:42:15 clu has joined #owl