17:00:01 RRSAgent has joined #owl 17:00:01 logging to http://www.w3.org/2008/06/25-owl-irc 17:00:12 Zakim, this will be owlwg 17:00:12 ok, pfps; I see SW_OWL()12:00PM scheduled to start 60 minutes ago 17:00:23 RRSagent, make records public 17:00:32 zakim, who is here? 17:00:32 bmotik has joined #owl 17:00:36 SW_OWL()12:00PM has not yet started, pfps 17:00:44 On IRC I see bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:00:47 baojie has joined #owl 17:00:55 zakim, mute me 17:00:56 sorry, Zhe, I don't know what conference this is 17:01:18 IanH has joined #owl 17:01:21 zakim, this will be owlwg 17:01:21 ok, pfps; I see SW_OWL()12:00PM scheduled to start 61 minutes ago 17:01:28 zakim, who is here? 17:01:28 SW_OWL()12:00PM has not yet started, pfps 17:01:29 On IRC I see IanH, baojie, bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:01:54 aha, this explains things 17:02:03 zakim, mute me 17:02:03 sorry, uli, I don't know what conference this is 17:02:09 Zakim, who is on the phone? 17:02:09 SW_OWL()12:00PM has not yet started, bmotik 17:02:10 On IRC I see IanH, baojie, bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:02:11 zakim, this will be owl 17:02:11 ok, sandro, I see SW_OWL()12:00PM already started 17:02:14 ScribeNick: msmith 17:02:15 +??P21 17:02:20 zakim, who is here? 17:02:25 zakim, dial ivan-voip 17:02:29 > Zakim, who is on the phone? 17:02:34 Zakim, who is on the phone? 17:02:39 -??P3 17:02:46 On the phone I see Peter_Patel-Schneider, +1.603.897.aaaa, +1.202.408.aabb, ??P5, ??P8, +0186527aacc, ??P21 17:02:49 ok, ivan; the call is being made 17:02:52 RRSAgent, pointer? 17:02:52 See http://www.w3.org/2008/06/25-owl-irc#T17-02-52 17:02:53 zakim, ??P21 is Ratnesh 17:02:55 +Ivan 17:03:00 RRSAgent, make log public 17:03:01 zakim, +1.603.897.aaaa is me 17:03:10 On the phone I see Peter_Patel-Schneider, +1.603.897.aaaa, +1.202.408.aabb, ??P5, ??P8, +0186527aacc, ??P21, Ivan 17:03:12 zakim, who is here? 17:03:13 zakim, who is here? 17:03:14 On IRC I see IanH, baojie, bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:03:14 it's always slow at the top of the hour. 17:03:17 +Sandro 17:03:25 +Ratnesh; got it 17:03:27 -??P8 17:03:31 +Zhe; got it 17:03:33 Zakim, ??P8 is me 17:03:39 On the phone I see Peter_Patel-Schneider, Zhe, +1.202.408.aabb, ??P5, +0186527aacc, Ratnesh, Ivan, Sandro 17:03:39 Zakim, aaaa is me 17:03:45 On the phone I see Peter_Patel-Schneider, Zhe, +1.202.408.aabb, ??P5, +0186527aacc, Ratnesh, Ivan, Sandro 17:03:49 zakim, mute me 17:03:57 +??P1 17:03:58 Achille has joined #owl 17:04:02 Zakim ??P8 is me 17:04:03 I already had ??P8 as ??P8, bcuencagrau 17:04:05 +??P2 17:04:11 sorry, Zhe, I do not recognize a party named 'aaaa' 17:04:13 On IRC I see IanH, baojie, bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:04:13 Zakim, mute me 17:04:24 Zhe should now be muted 17:04:29 -??P5 17:04:30 JeffP has joined #owl 17:04:34 Zakim, mute me 17:04:36 sorry, bcuencagrau, I do not know which phone connection belongs to you 17:04:38 + +1.518.276.aadd 17:04:42 +??P4 17:04:47 zakim, aadd is me 17:04:47 Zakim, ??P4 17:04:52 sorry, bcuencagrau, I do not know which phone connection belongs to you 17:04:55 Zakim, ??P4 is me 17:04:59 +baojie; got it 17:04:59 zakim, aacc is me 17:05:02 I don't understand '??P4', bmotik 17:05:06 +bmotik; got it 17:05:08 -??P1 17:05:12 +IanH; got it 17:05:12 Zakim, mute me 17:05:14 ack ??P5 17:05:24 bmotik should now be muted 17:05:26 +[IBM] 17:05:26 zakim, ??P2 is me 17:05:29 Zakim, IBM is me 17:05:30 zakim, who is here? 17:05:31 zakim, mute me 17:05:40 +uli; got it 17:05:44 + +0122427aaee 17:05:48 +Achille; got it 17:05:48 ack +0186527aacc 17:05:50 On the phone I see Peter_Patel-Schneider, Zhe (muted), msmith, IanH, Ratnesh, Ivan, Sandro, uli, baojie, bmotik (muted), Achille, +0122427aaee 17:05:55 uli should now be muted 17:05:55 zakim, aaee is me 17:05:57 ack ??P2 17:06:04 On IRC I see JeffP, Achille, IanH, baojie, bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:06:09 Agenda: http://www.w3.org/2007/OWL/wiki/Teleconference.2008.06.25/Agenda 17:06:12 +JeffP; got it 17:06:18 +??P8 17:06:24 Zakim, ??P8 is me 17:06:30 zakim, who is here? 17:06:38 +bcuencagrau; got it 17:06:42 On the phone I see Peter_Patel-Schneider, Zhe (muted), msmith, IanH, Ratnesh, Ivan, Sandro, uli (muted), baojie, bmotik (muted), Achille, JeffP, bcuencagrau 17:06:44 Zakim, mute me 17:06:55 bcuencagrau should now be muted 17:06:58 On IRC I see JeffP, Achille, IanH, baojie, bmotik, RRSAgent, msmith, Zhe, uli, Zakim, ivan, bcuencagrau, Ratnesh, sandro, pfps, trackbot 17:07:02 alanr has joined #owl 17:07:04 +Alan 17:07:33 topic: roll call 17:07:41 topic: agenda amendments? 17:07:51 Rinke has joined #owl 17:07:58 ianh: no agenda amendments 17:08:06 -bmotik 17:08:20 topic: PROPOSED: Accept Previous3 Minutes (04 June) 17:08:26 +??P4 17:08:30 Zakim, ??P4 is me 17:08:30 +bmotik; got it 17:08:32 4 june minutes look acceptable 17:08:36 Zakim, mute me 17:08:36 bmotik should now be muted 17:08:38 calvanese has joined #owl 17:08:54 RESOLVED: Accept Previous3 Minutes (04 June) 17:09:11 topic: Accept Previous2 Minutes (11 June) 17:09:12 11 june minutes look acceptable 17:09:18 +1 17:09:20 PROPOSED: Accept Previous2 Minutes (11 June) 17:09:21 +1 17:09:26 RESOLVED: Accept Previous2 Minutes (11 June) 17:09:38 topic: Accept Previous Minutes (18 June) 17:09:40 18 june minutes are *perfect* :-) 17:09:43 PROPOSED: Accept Previous Minutes (18 June) 17:09:52 +1 17:10:09 RESOLVED: Accept Previous Minutes (18 June) 17:10:31 topic: f2f3 17:10:37 + +39.047.101.aaff 17:10:49 ianh: clarify status on http://www.w3.org/2007/OWL/wiki/F2F3_People 17:11:00 zakim, mute me 17:11:00 sorry, calvanese, I do not know which phone connection belongs to you 17:11:06 topic: pending review actions 17:11:14 zakim, +39.047.101.aaff is me 17:11:14 +calvanese; got it 17:11:20 zakim, mute me 17:11:20 calvanese should now be muted 17:11:22 +??P18 17:11:23 zakim, unmute me 17:11:23 uli should no longer be muted 17:11:30 zakim, ??P18 is me 17:11:34 +Rinke; got it 17:11:35 q? 17:11:41 zakim, mute me 17:11:41 Rinke should now be muted 17:11:48 ianh: on action-160 wasn't there question on top/bottom in profiles? keys in profiles? 17:11:56 q+ 17:12:01 ... there was an action on uli re: top/bottom in profiles 17:12:09 zakim, unmute me 17:12:13 zakim, mute me 17:12:13 uli should now be muted 17:12:32 uli: I sent an email on top/bottom in dl-lite. diego? 17:12:57 zakim, unmute me 17:12:57 uli should no longer be muted 17:13:03 q? 17:13:04 q+ 17:13:13 ack calvanese 17:13:14 calvanese: dl-lite has no top concept... there is no point to having it. we don't believe it would impact properties, but there is not point 17:13:29 ... if it doesn't change computation properties, it is just by chance 17:13:36 ... you don't gain any expressivity 17:13:50 ianh: its already that it doesn't add expressive power to DL 17:13:50 q? 17:14:01 zakim, unmute me 17:14:01 uli was not muted, uli 17:14:06 ack uli 17:14:09 calvanese: yes, b/c you have nominals, that might not apply to profile which is strict subset 17:14:21 q+ 17:14:25 uli: reason to add is not to add expressivity, it is to add useful syntactic sugar 17:14:31 q+ 17:14:46 ... e.g., rooting a property hierarchy from a top property 17:15:11 ianh: with profiles, ruling things out is costly rather than having them 17:15:25 q? 17:15:27 Zakim, unmute me 17:15:27 bmotik should no longer be muted 17:15:27 ... we should only rule things out if e.g., they have adverse impact on properties 17:15:33 msmith: +1 to ianh 17:15:42 ack calvanese 17:16:22 zakim, mute me 17:16:22 uli should now be muted 17:16:28 q? 17:16:34 calvanese: I partially agree. adding construct gives indication it is to be used. this may have bad impact, even if it can be simulated with existing constructs 17:16:43 +1 calvanese 17:16:47 ... similar argument for dl-lite profile 17:16:57 -Ratnesh 17:17:01 q? 17:17:07 ack bmotik 17:17:27 bmotik: only profile now including top/bottom is EL++ 17:17:33 q+ 17:17:46 ... I don't think property must be in profile for editor to hang things off it in UI 17:18:11 q? 17:18:14 1- 17:18:14 ianh: we had discussion about top/bottom being useful and addressed if it *tempts* users in a negative way 17:18:15 q- 17:18:21 +??P15 17:18:26 ... it seems we can have it in dl-lite 17:18:26 q+ 17:18:33 zakim, ??P15 is Ratnesh 17:18:33 +Ratnesh; got it 17:18:37 calvanese: I'd like to check the details on whether we can have it 17:18:59 q- 17:19:15 ianh: revisit this in future telecon 17:19:19 q? 17:19:22 ... top/bottom is in el++ 17:19:30 bmotik: not in owl-r 17:19:43 ianh: should we action someone to investigate easy keys 17:19:45 q? 17:19:58 bmotik: no. its clear no easy keys in dl-lite 17:20:03 q+ 17:20:04 q+ 17:20:11 ... I added it to owl-r 17:20:12 q? 17:20:25 ... unknown for EL++ 17:20:34 jeffp: top/bottom in el++ ? 17:20:43 bmotik: yes, checked with Carsten 17:20:53 jeffp: it doesn't have nominals 17:20:55 q+ 17:20:58 q- 17:21:03 ianh: yes, presumably it doesn't hurt 17:21:13 bmotik: yes, it doesn't hurt 17:21:15 ack JeffP 17:21:18 jefffp: what about el+ 17:21:20 EL++ without nominals 17:21:23 q? 17:21:26 bmotik: what's el+ 17:21:46 jeffp: el+ is supported by CEL 17:21:56 ok 17:22:04 ianh: a bit off topic, we're only cerned with EL++ profile, not other fragments 17:22:14 s/cerned/concerned/ 17:22:28 q? 17:22:51 ... interesting that CEL doesn't support all of EL++ since we'll need to follow-up moving forward the recs 17:23:36 calvanese: follow-up on keys in dl-lite, and boris's comments on it adding recursion. we'd like to see some version of keys, could we consider a restricted version. 17:23:41 ianh: are you willing to take action 17:23:56 action: calvanese to investigate top/bottom roles in dl-lite 17:23:56 Created ACTION-162 - Investigate top/bottom roles in dl-lite [on Diego Calvanese - due 2008-07-02]. 17:24:12  action: calvanese to investigate easy keys in dl-lite 17:24:21 q? 17:24:31 ACCEPT ACTION-160 as completed 17:24:36 topic: due and overdue actions 17:24:46 q? 17:24:55 ack calvanese 17:24:56 q- 17:24:57 ianh: action-155 17:25:12 could we have a pointer to the document from the ACTION-155 page? 17:25:16 q? 17:25:29 ianh: there is a document, we also need implementation 17:25:40 zakim, mute me 17:25:40 calvanese should now be muted 17:25:46 ianh: yes, we should add pointer to doc to action 17:26:01 no 17:26:10 ... bump date forward for action-155 pending arrival of an implementation? 17:26:18 q+ 17:26:22 q- 17:26:26 ianh: ok, that's what we'll do 17:26:28 q? 17:26:40 ianh: action-156, action-157 17:26:47 alanr: push them both a week 17:26:52 ianh: ok 17:27:13 q? 17:27:14 q+ 17:27:15 topic: issue-21 and issue-24 17:27:42 q? 17:27:47 ack alanr 17:27:53 ianh: proposal to resolve says "per pfps email and subsequent discussion", are we really here? it doesn't seem complete 17:28:01 q+ 17:28:05 q? 17:28:07 alanr: we're close, have 1 issue open 17:28:28 ... is inconsistent independent of header? bmotik and I disagreed 17:28:40 q+ 17:28:54 ... it may be case inconsistency is noticed by user, not maintainer, we'd like to state this 17:28:54 q? 17:28:59 ack bmotik 17:29:06 bmotik: one ontology saying something about another is recipe for disaster 17:29:12 q- 17:29:21 ... breaks encapsulation. let's people say anything about anything 17:29:35 how is this different from having axioms on a class in two different ontologies? 17:29:37 q? 17:29:40 Not sure whether this has anything to do with the issues per se? Seems that the issues are being overloaded with side-issues that prevent them from being resolved. 17:29:40 ...detecting these incompatibilities and maintenance could get out of hand 17:29:49 detecting is trivial 17:29:54 q+ 17:29:57 q? 17:30:01 ack alanr 17:30:07 q- 17:30:25 q? 17:30:29 q+ 17:30:30 q+ 17:30:31 alanr: I'm not persuaded 17:30:37 ack bmotik 17:31:03 q? 17:31:04 bmotik: allowing one ont to say something about another seems to me as a conceptual hack 17:31:26 +1 to separate issue! 17:31:29 alanr: you're arguing conceptual integrity vs. use case from personal experience 17:31:40 zakim, unmute me 17:31:40 uli should no longer be muted 17:31:42 ... we can spin this off to another issue and resolve the rest 17:31:56 uli: +1 on separate issue 17:32:14 q+ 17:32:15 ... +1 to bmotik that this will open can of worms and may be difficult to explain behavior 17:32:18 q+ 17:32:33 ack uli 17:32:48 q? 17:32:51 ack bmotik 17:32:55 q? 17:33:02 ianh: I see what you mean, just as you don't have control over another on, you may not have control over statements saying what onts are incompatible 17:33:10 q? 17:33:10 bmotik: already what we have is an improvement 17:33:15 ack alanr 17:33:18 q? 17:33:19 alanr: not sure that's the case for owl 1 17:33:26 bmotik: but there was no semantics 17:33:35 q? 17:33:37 alanr: yes, problem was no teeth to semantics 17:34:06 bmotik: tool is more that welcome to do this. seems to be extrapolating from one use case 17:34:37 ianh: given we have agreement other than this, can we move forward closing ISSUE-21 and ISSUE-24 and open new issue to discuss versioning? 17:34:44 q+ 17:34:48 alanr: incompatible with, not versioning 17:34:50 fine by me 17:34:56 +1 17:35:07 ianh: yes, incompatibleWith 17:35:55 PROPOSED: resolve Issue 21 and Issue 24 Imports and Versioning, per update from Boris, Peter's email and subsequent discussion, modulo opening new issue on incompatibleWith 17:36:34 bmotik: if we move forward splitting, I think we should take everything out 17:36:45 -q 17:36:49 alanr: I disagree unless strong opposition. it would be a step backwards 17:37:09 ianh: if we resolve in favor of your approach, doesn't that mean ripping out what's there now? 17:37:26 q? 17:37:27 alanr: ontology header is better than nothing, if we remove it we may have to readd it later 17:37:40 bmotik: I'd prefer to discuss if we need incompatibleWith at all 17:38:14 q? 17:38:19 alanr: it seems we're now moving backwards 17:38:39 pfps: I suggest going as proposal says, discuss incompatible with as separate issue 17:38:48 bmotik: out of document? 17:39:06 pfps: minimal change to current doc. it is an interim state, even if no one likes it 17:39:12 bmotik: ok 17:39:34 PROPOSED: resolve Issue 21 and Issue 24 Imports and Versioning, per update from Boris, Peter's email and subsequent discussion, but open new issue on status of incompatibleWith 17:39:46 +1 to resolve this way 17:39:49 +1 17:39:51 +1 17:39:53 +1 17:39:53 +1 17:39:56 +1 17:39:58 0 17:39:59 +1 17:40:03 0 17:40:08 +1 17:40:17 +1 17:40:25 RESOLVED: resolve Issue 21 and Issue 24 Imports and Versioning, per update from Boris, Peter's email and subsequent discussion, but open new issue on status of incompatibleWith 17:40:37 +1 17:40:38 happy happy 17:40:42 joy joy 17:40:46 ACTION to bmotik2: Update the strucutral spec according to resolution of ISSUE 21 and ISSUE 24 17:40:46 Sorry, couldn't find user - to 17:41:00 ACTION bmotik2: Update the strucutral spec according to resolution of ISSUE 21 and ISSUE 24 17:41:00 Created ACTION-163 - Update the strucutral spec according to resolution of ISSUE 21 and ISSUE 24 [on Boris Motik - due 2008-07-02]. 17:41:03 Topic: ISSUE-81 17:41:05 Achille has joined #owl 17:41:06 q? 17:41:37 q? 17:41:53 ianh: ISSUE-81 can be resolved using bmotik's proposal to use an alternative vocabulary for reification 17:42:08 ... any reasons not to resolve? 17:42:18 PROPOSED: resolve Issue 81 Reification of Negative Property Assertions, per Boris's email 17:42:21 +1 to proceed apace 17:42:24 +1 17:42:25 +1 17:42:26 +1 17:42:27 +1 17:42:28 +1 17:42:37 +1 17:42:37 +1 17:42:46 +1 17:42:58 RESOLVED: resolve Issue 81 Reification of Negative Property Assertions, per Boris's email (http://lists.w3.org/Archives/Public/public-owl-wg/2008Jun/0156.html) 17:43:06 +1 17:43:09 happy happy 17:43:15 +1 17:43:16 +1 17:43:35 topic: issue discussions 17:43:47 http://lists.w3.org/Archives/Public/public-owl-wg/2008Jun/0171.html 17:43:57 ianh: brief revisit of profile naming (ISSUE-108) 17:44:10 bmotik_ has joined #owl 17:44:28 ...(as in Carsten's email) at least OWL-R and OWL-EL names are ok, DL-Lite needs a name 17:44:48 ... Carsten proposed calling it owl-db, but that's likely to be contentious 17:44:48 Q? 17:44:50 q+ 17:44:51 q+ 17:44:52 :_ 17:44:59 bmotik__ has joined #owl 17:45:01 q? 17:45:29 msmith: why can't we call it dl-lite? 17:45:30 unmute me 17:45:34 ack msmith 17:45:35 ack msmith 17:45:39 unmute me 17:45:40 we want to market to a larger community!! 17:45:48 ianh: owl-lite is deprecated, owl dl-lite seems rather long winded 17:45:51 zakim, unmute me 17:45:51 calvanese should no longer be muted 17:46:04 "OWL2 Lite" ? 17:46:21 OWL-D 17:46:22 q? 17:46:25 q+ 17:46:27 calvanese: we believe name owl-db would be suitable, since owl-r people like owl-r lets use owl-db 17:46:30 zakim, unmute me 17:46:30 Zhe should no longer be muted 17:46:38 ... owl-d doesn't evoke anything related to dl-lite 17:46:50 OWL-I 17:46:51 q? 17:46:51 ... I am not in favor of owl-d 17:46:56 ack Zhe 17:47:06 q? 17:47:07 zhe: is this profile specific for db modeling integration and nothing else? 17:47:16 q? 17:47:21 ... owl-db name implies something 17:47:44 quantify "large"? 17:47:50 zakim, who is speaking 17:47:50 I don't understand 'who is speaking', uli 17:47:50 calvanese: profile was created to connect to large databases. we believe it is specifically suited to databases 17:47:55 millions, 100s of millions? 17:47:56 q? 17:48:03 zakim, who is talking? 17:48:07 10s of billions? 17:48:11 q? 17:48:15 .... also conceptually matches expressivity of databases 17:48:16 JeffP, listening for 11 seconds I heard sound from the following: Sandro (4%), Ratnesh (9%), calvanese (27%), Zhe (82%) 17:48:33 zhe: misleading to me because dl-lite can be provided to other domains 17:48:52 ... plus gives users belief dedicated to storing owl 17:49:00 zakim, mute me 17:49:00 Ratnesh should now be muted 17:49:03 q? 17:49:04 ... gives impression only implementable with db, nothing else 17:49:23 ... dl-lite could apply to sparql endpoint as well 17:49:27 q? 17:49:42 calvanese: one point is that its implemented using database technologies 17:49:55 zhe: is this implementation specific? 17:50:02 calvanese: its how the profile came about 17:50:12 ... its tuned to these features 17:50:26 q+ 17:50:27 q+ 17:50:29 q? 17:50:42 ack bmotik 17:50:44 q? 17:50:45 ianh: useful exchange, and what we suspected. owl-db is controversial. any other less controversial names? 17:50:45 Profile names are easily interpreted as denoting disjoint `features' 17:50:55 bmotik: why not 1,2,3 or A,B,C? 17:51:07 the only reasonable mnemonic is "R" 17:51:20 ianh: we have reasonable names for EL++ and OWL-R which people are comfortable with. isn't 1,2,3 silly? 17:51:28 bmotik: what's wrong with current names? 17:51:28 q? 17:51:38 ianh: owl dl-lite is too much of a mouthful 17:51:38 q+ 17:52:06 alanr: only name with good pneumonic is OWL-R, EL++ is historical and only relevant to small audience 17:52:14 q? 17:52:19 ack alanr 17:52:25 +1 get away from history. 17:52:31 ... I support getting away from historical names and suggest 1 letter (fairly meaningless) names 17:53:07 yes, peter, but for how many others? 17:53:07 q? 17:53:08 "DL" is another bad name. 17:53:10 bmotik: owl dl-lite is too much of a mouthful, what about just dl-lite 17:53:18 I agree, that DL is another bad name 17:53:24 q? 17:53:35 q+ to propose leaving this to marketing 17:53:36 ... el++ has established itself, it doesn't need the owl prefix 17:53:36 ack bmotik 17:53:39 q? 17:53:48 ianh: that may be a step too far 17:53:49 OWL-C for OWL-DL (OWL-Complete) 17:53:56 q+ 17:54:02 OWL-A for (OWL-Anything for OWL-Full) 17:54:04 ack sandro 17:54:04 sandro, you wanted to propose leaving this to marketing 17:54:04 DL-Lite: about assertions, why not OWL-A 17:54:06 q? 17:54:22 sandro: we are worst people to pick names. someone should subject a marketing department to this not us 17:54:36 ... knowledge of history is an impediment 17:55:12 q? 17:55:15 ianh: another side, the marketing people ask you to explain because they know nothing. so, names they create will depend on who explains them 17:55:24 agree with Sandro, one complaint that came up in my little survey was that people didn't know what the names meant 17:55:33 +1 to Rinke 17:55:46 q? 17:55:46 sandro: names should be targeted at people making the purchase decision 17:55:56 calvanese: name is indication, choice will be made on features 17:56:12 I was convinced 17:56:15 ... I made several good arguments for why owl-db is good for dl-lite 17:56:25 q? 17:56:28 ... I didn't hear compelling, non-marketing counterarguments 17:56:31 q+ 17:56:38 ack calvanese 17:56:46 ack Zhe 17:57:14 zhe: why not call owl-r owl-db? oracle is largest database in the world and implements owl-r? 17:57:25 We can call it OWL-Aberdeen 17:57:43 JeffP: I would prefer OWL-Amsterdam! 17:57:48 hehe 17:57:49 me too! 17:57:49 ianh: enough of this discussion. owl-db is just too attractive, so probably no one can have it 17:57:57 +1 to random city names. :-) 17:58:12 rowl, dowl? 17:58:14 zakim, mute me 17:58:14 calvanese should now be muted 17:58:21 howl? 17:58:21 who gets OWL-Bagdad? 17:58:22 topic: issue-67 reification 17:58:47 q? 17:58:49 q+ 17:58:59 ... anyone? 17:59:00 q? 17:59:11 pfps: I don't think anything needs to be done, current status is fine 17:59:14 q+ 17:59:17 q+ 17:59:20 ack pfps 17:59:20 q- 17:59:22 ianh: current status is that we're using rdf reification 17:59:30 alanr: I'm happy with current reification 17:59:32 second alanr 17:59:34 ack alanr 17:59:38 ack bmotik 17:59:42 ... as long as triple being reified is included 17:59:52 bmotik: I don't think we should output triple being reified 17:59:59 q? 18:00:03 q+ 18:00:05 ... this can be handled in the semantics 18:00:09 that's not an argument against. It's an argument that says we can also do it a different way 18:00:09 q? 18:00:30 ack Zhe 18:00:39 q+ 18:00:43 q? 18:00:47 q+ 18:00:49 zhe: conceptually, bmotik is 100% correct. but with tons of annotations this makes implementers life difficult 18:00:55 ack alanr 18:00:57 ... what's the objection to adding the triple 18:01:03 q+ 18:01:23 alanr: yes, what's argument against? this is a divergence from rdf semantics 18:01:39 q? 18:01:48 ack bmotik 18:01:56 I put a proposal for how to solve this on the email 18:02:11 bmotik: impossible to know when mapping rdf to ontology if ontology contained axiom or just annotation of axiom 18:02:17 q+ 18:02:27 q+ 18:02:30 ... I consider sticking with current better solution 18:02:51 +1 to supporting annotation of non-present axioms 18:03:08 There is also rdf/xml support for concise reification when it includes the triple 18:03:16 q- 18:03:34 ack Zhe 18:03:36 pfps: I don't believe argument that additional processing burden is accurate since it introduces an additional triple to parse 18:03:54 zhe: bmotik, I believe you proposed solutions via email to some of these problems. 18:04:09 ... pfps, oracle believes not including triple will make life harder 18:04:12 q? 18:04:23 +q to respont to Zhe 18:04:55 q? 18:04:59 alanr: support for concise reification in RDF/XML, but only in some circumstances 18:05:01 ack alanr 18:05:10 (er, no, you still need to parse the triples even when not using the RDF/XML trick.) 18:05:27 -Rinke 18:05:29 bmotik: are you proposing we use this special syntax 18:06:00 alanr: if triple is in serialization, on can put an id on the predicate to indicate reification 18:06:10 ... there is no shorthand for only the reified part 18:06:17 ianh: closing discussion soon 18:06:21 q? 18:06:38 q? 18:06:43 ack bmotik 18:06:43 bmotik, you wanted to respont to Zhe 18:07:19 no bad ida 18:07:29 better to add a special annotation so they are parallel 18:07:37 q? 18:08:12 q? 18:08:14 I don't understand 18:08:20 me neither 18:08:26 bmotik: one could use following procedure.... if re-ified and non-reified version are present... but this is non-monotonic. question to zhe - if hint that reified triples in RDF/XML should use this shorthand, would that be ok? 18:08:43 I do not think we can do that, Boris 18:09:00 q? 18:09:05 sounds good 18:09:10 ianh: take to email, then revisit discussion 18:09:39 topic: general discussion, schedule 18:09:45 q? 18:10:12 ianh: agenda has short list of things needing attention 18:10:24 ... features: 1) rich annotations, 2) nary datatypes 18:10:26 q? 18:10:27 Bijan isn't here 18:10:32 zakim, where is bijan? 18:10:32 sorry, sandro, I do not understand your question 18:10:47 ... no bijan? :( perhaps uli on nary? 18:10:50 q? 18:10:52 zakim, unmute me 18:10:52 uli was not muted, uli 18:11:18 uli: what are you after? 18:11:36 ianh: I'd like some comments on schedule? 18:12:14 uli: we could be moving really faster. I won't be around for next two weeks, otherwise I'd say proposal in 1 week 18:12:27 ianh: a concrete proposal for what should be added to spec? 18:12:42 ... but not now? 18:12:51 probably depends on what happens next week and the week after too... 18:12:57 uli: depends on this week. 18:12:59 q? 18:13:05 zakim, mute me 18:13:05 uli should now be muted 18:13:07 q? 18:13:07 ianh: this is reasonable guesstimate 18:13:43 alanr: we should get quick check-in on prioritizing things. rich annotations, nary 18:13:53 q+ 18:14:06 ... how are people on nary? priorities, benefits vs cost of delaying? 18:14:22 ... when do we say it's out? 18:14:45 ianh: is my answer some number of weeks? 18:14:54 -q 18:15:10 +q 18:15:11 alanr: I would like to hear from people. I'd like to hear input. 18:15:35 ianh: is it significant delay worthy? 18:15:39 zakim, who is on the call? 18:15:39 On the phone I see Peter_Patel-Schneider, Zhe, msmith, IanH, Ivan, Sandro, uli (muted), baojie, Achille, JeffP, bcuencagrau (muted), Alan, bmotik, calvanese (muted), Ratnesh 18:15:43 ... (muted) 18:15:51 msmith: I think nary are important and would be prepared to wait some 18:15:58 "How horrible would you think failing on n-ary be?" 18:16:04 i'm prepared to wait forever as long as it isn't more than 15 minutes (thanks Oscar Wilde) 18:16:09 q+ 18:16:11 I believe that n-ary datatypes are a high-risk feature 18:16:39 we can leave without nary 18:16:44 I'm concerned about unknowns with n-aries, and known issues, like difficulty in combinations. 18:16:47 q? 18:16:48 bmotik: adding nary adds a huge burden to developers. some algorithmic issues haven't been resolved and I'm skeptical 18:16:57 msmith: notes Carsten also absent 18:17:04 good point 18:17:06 it is not worth delaying the spec for it 18:17:11 zakim, unmute me 18:17:11 uli should no longer be muted 18:17:14 q? 18:17:16 ianh: not time now to get to into the details 18:17:16 ack bmotik 18:17:19 ack bmotik 18:17:22 ack uli 18:17:30 owl3? 18:17:38 uli: not having any nary support would be regretted later as something we missed 18:17:50 ianh: perhaps we should set some implementation bar 18:18:05 q? 18:18:07 ... 2 implementations to get to rec, correct? 18:18:07 q+ 18:18:09 q+ 18:18:18 ack sandro 18:18:20 ack uli 18:18:41 sandro: in general, should only add things for which we think reasonable to there may be two implementations 18:18:48 ACK alanr 18:18:49 +1 to "at risk"iness 18:18:50 ... if we're unsure, that means its at risk 18:19:19 alanr: that doesn't help because there's significant work to get it into the spec 18:19:47 ianh: i agree with that, but the implementation point clarifies just how much expressive power we want to add. 18:19:51 q+ to give one more thought 18:19:59 q? 18:20:07 ack alanr 18:20:07 alanr, you wanted to give one more thought 18:20:10 ... those wanting it very powerful must weight that against cost of implementing it so that it can proceed 18:20:11 q? 18:20:42 +q 18:20:46 q? 18:20:46 alanr: so far focused on one type of concrete domain extension, < > simple arithmetic 18:20:56 alanr, can you explain this? 18:21:05 ... perhaps allen interval relations instead. I'm taking this up with carsten 18:21:07 uli, yes, via email 18:21:22 bmotik: allen interval for time intervals will not solve problems for owl 18:21:44 won't solve all time problems for time. But may solve some some time problems 18:21:45 q? 18:21:46 bmotik: nary datatypes won't help this ... 18:21:54 ack bmotik 18:22:27 ...(scribe interpret) because they only apply to data properties on a single individuals (not comparison between multiple events) 18:22:37 ianh: will ask bijan next week about this 18:23:01 ianh: also discussion about datatypes in general, what should be supported. is this going to derail us? 18:23:03 +q 18:23:04 q? 18:23:12 q? 18:23:17 ack bmotik 18:23:20 bmotik: thinks we can resolve. we have to resolve 18:23:21 I have concerns that this will take time. 18:23:40 q? 18:23:43 ... I don't think solution is difficult 18:23:54 -calvanese 18:24:17 ;) 18:24:23 yes 18:24:26 very 18:24:36 ianh: ISSUE-118 is languishing 18:24:47 q+ 18:24:48 q? 18:24:52 ... any champion for this issue? 18:25:24 alanr: I've suggested unnamed and bnodes as alternative constructs 18:25:47 ianh: documents need to be produced. test, ufds 18:25:48 action: alan to send email re: suggestions (again) for unnamed individuals *in addition* to bnodes 18:25:48 Created ACTION-164 - Send email re: suggestions (again) for unnamed individuals *in addition* to bnodes [on Alan Ruttenberg - due 2008-07-02]. 18:25:57 q? 18:26:25 q? 18:26:30 mike, you know about action=raw ? to get raw mediawiki pages? 18:26:44 q- 18:26:46 alanr, no. thanks 18:27:18 msmith: re tests, I'm targeting f2f3 as a milestone. two parts, the tests, and the documents 18:27:26 q? 18:27:29 ... I'll try to get something to the group before f2f3 on each 18:27:32 mike, see http://svn.neurocommons.org/svn/trunk/product/wiki/get-ncpage-ontology.pl 18:27:49 ianh: none for ufd 18:28:00 pfps: I think bijan is working on primer 18:28:09 topic: additional business 18:28:12 bye 18:28:17 bye 18:28:17 ianh: no additional business, adjourn 18:28:17 thanks 18:28:18 bye bye 18:28:21 -uli 18:28:23 bye 18:28:24 -Ivan 18:28:25 -baojie 18:28:26 -JeffP 18:28:26 -Achille 18:28:28 -bmotik 18:28:28 -Ratnesh 18:28:30 -Zhe 18:28:32 -Sandro 18:28:33 -IanH 18:28:38 -bcuencagrau 18:28:41 msmith, I put some notes about scribing here: http://www.w3.org/2007/OWL/wiki/Scribe_Conventions#After_scribing_.28New_Style_Minutes.29 18:28:45 -msmith 18:28:48 I'm hoping that Turkey wins on penalties :-) 18:29:02 rrsagent, pointer 18:29:02 See http://www.w3.org/2008/06/25-owl-irc#T18-29-02 18:29:14 e.g http://sw.neurocommons.org/cgi-bin/get-ncpage-ontology.pl?page=CommonsPurl:Record/Ncbi_gene§ion=purlRdf 18:29:18 I hope that they have great game 18:29:26 Zakim, list attendees 18:29:26 As of this point the attendees have been Peter_Patel-Schneider, +1.202.408.aabb, +0186527aacc, Ivan, Sandro, Ratnesh, Zhe, msmith, +1.518.276.aadd, baojie, bmotik, IanH, uli, 18:29:30 ... +0122427aaee, Achille, JeffP, bcuencagrau, Alan, calvanese, Rinke 18:29:39 -Alan 18:31:07 zakim, bye 18:31:07 leaving. As of this point the attendees were Peter_Patel-Schneider, +1.202.408.aabb, +0186527aacc, Ivan, Sandro, Ratnesh, Zhe, msmith, +1.518.276.aadd, baojie, bmotik, IanH, uli, 18:31:07 Zakim has left #owl 18:31:10 ... +0122427aaee, Achille, JeffP, bcuencagrau, Alan, calvanese, Rinke 18:31:21 rrsagent, make log public 18:31:32 rrsagent, draft minutes 18:31:32 I have made the request to generate http://www.w3.org/2008/06/25-owl-minutes.html msmith 18:31:39 rrsagent, bye 18:31:39 I see 3 open action items saved in http://www.w3.org/2008/06/25-owl-actions.rdf : 18:31:39 ACTION: calvanese to investigate top/bottom roles in dl-lite [1] 18:31:39 recorded in http://www.w3.org/2008/06/25-owl-irc#T17-23-56 18:31:39 ACTION: bmotik2 to Update the strucutral spec according to resolution of ISSUE 21 and ISSUE 24 [2] 18:31:39 recorded in http://www.w3.org/2008/06/25-owl-irc#T17-41-00 18:31:39 ACTION: alan to send email re: suggestions (again) for unnamed individuals *in addition* to bnodes [3] 18:31:39 recorded in http://www.w3.org/2008/06/25-owl-irc#T18-25-48