17:56:56 RRSAgent has joined #owl 17:56:56 logging to http://www.w3.org/2007/11/21-owl-irc 17:56:58 +??P4 17:57:15 ah, that looks better 17:57:25 ScribeNick: Rinke 17:58:05 rrsagent, make record public 17:58:11 bmotik has joined #owl 17:58:17 zakim, who's here 17:58:17 Rinke, you need to end that query with '?' 17:58:23 zakim, who's here? 17:58:23 On the phone I see bijan (muted), Rinke, MIchaelSmith, MarkusK 17:58:24 On IRC I see bmotik, RRSAgent, Zakim, MichaelSmith, MarkusK, vit, bijan, Rinke, IanH, MartinD, sandro, trackbot-ng 17:58:33 bcuencag has joined #owl 17:58:52 +??P6 17:59:09 uli has joined #owl 17:59:14 Carsten has joined #owl 17:59:17 +MartinD 17:59:20 Zakim, ??P6 is bmotik 17:59:20 +bmotik; got it 17:59:26 jeremy has joined #owl 17:59:27 +IanH 17:59:31 Zakim, mute me 17:59:31 bmotik should now be muted 17:59:33 zakim, mute me 17:59:33 MartinD should now be muted 18:00:05 -bmotik 18:00:23 +??P9 18:00:49 +Alan 18:01:02 +??P12 18:01:03 zakim, ??P9 is me 18:01:03 +uli; got it 18:01:09 +Sandro 18:01:13 Zakim, ??P12 is bmotik 18:01:13 +bmotik; got it 18:01:16 Zakim, mute me 18:01:16 bmotik should now be muted 18:01:17 +??P11 18:01:39 +??P18 18:01:48 Zakim, ??P18 is me 18:01:48 +vit; got it 18:01:58 zakim, who is here? 18:01:58 On the phone I see bijan (muted), Rinke, MIchaelSmith, MarkusK (muted), MartinD (muted), IanH, uli (muted), Alan, bmotik (muted), Sandro, ??P11, vit 18:02:00 On IRC I see jeremy, Carsten, uli, bcuencag, bmotik, RRSAgent, Zakim, MichaelSmith, MarkusK, vit, bijan, Rinke, IanH, MartinD, sandro, trackbot-ng 18:02:03 alanr has joined #owl 18:02:16 ewallace has joined #owl 18:02:27 zakik, who is on the call? 18:02:35 zakim, who is on the call? 18:02:35 On the phone I see bijan (muted), Rinke, MIchaelSmith, MarkusK (muted), MartinD (muted), IanH, uli (muted), Alan, bmotik (muted), Sandro, ??P11, vit 18:02:40 +??P19 18:03:03 calling in on cell phone too, for a few minutes, so I can fetch a coffee... 18:03:23 pfps has joined #owl 18:03:32 zhe has joined #owl 18:03:35 "Zakim, ??19 is me" 18:03:46 +??P20 18:03:50 zakim, ??p20 is me 18:03:50 +pfps; got it 18:03:51 zakim, ??P19 is me 18:03:52 +bcuencag; got it 18:03:54 +Alan_Ruttenberg 18:03:56 zakim, mute me 18:03:56 pfps should now be muted 18:04:00 +??P3 18:04:06 zakim, who is here? 18:04:06 On the phone I see bijan (muted), Rinke, MIchaelSmith, MarkusK (muted), MartinD (muted), IanH, uli (muted), Alan, bmotik (muted), Sandro, ??P11, vit, bcuencag, pfps (muted), 18:04:09 ... Alan_Ruttenberg, ??P3 18:04:11 On IRC I see zhe, pfps, ewallace, alanr, jeremy, Carsten, uli, bcuencag, bmotik, RRSAgent, Zakim, MichaelSmith, MarkusK, vit, bijan, Rinke, IanH, MartinD, sandro, trackbot-ng 18:04:12 zakim, ??p3 is me 18:04:14 +Carsten; got it 18:04:20 zakim, mut me 18:04:20 I don't understand 'mut me', Carsten 18:04:25 zakim, mute me 18:04:25 Carsten should now be muted 18:04:33 zakim, mute me 18:04:33 Rinke should now be muted 18:04:48 +Evan_Wallace 18:06:05 "Zakim, ??P11 is me" 18:06:08 like that. 18:06:17 Zakim, ??P11 is me 18:06:17 +zhe; got it 18:06:26 zakim, who is here? 18:06:26 On the phone I see bijan (muted), Rinke (muted), MIchaelSmith, MarkusK (muted), MartinD (muted), IanH, uli (muted), Alan, bmotik (muted), Sandro, zhe, vit, bcuencag, pfps (muted), 18:06:29 ... Alan_Ruttenberg, Carsten (muted), Evan_Wallace 18:06:30 On IRC I see zhe, pfps, ewallace, alanr, jeremy, Carsten, uli, bcuencag, bmotik, RRSAgent, Zakim, MichaelSmith, MarkusK, vit, bijan, Rinke, IanH, MartinD, sandro, trackbot-ng 18:07:04 IanH: covered Role call 18:07:20 scribenick: Rinke 18:07:25 ok, thanks 18:07:30 RRSAgent, pointer? 18:07:30 See http://www.w3.org/2007/11/21-owl-irc#T18-07-30 18:07:32 IanH: covered Role call 18:07:43 ... any amendments? 18:07:50 ... no amendments 18:07:56 PROPOSED: Accept Previous Previous Minutes 18:08:00 Are we going to cover more issues if we finsih the one's listed 18:08:05 ? 18:08:06 they were rather late 18:08:10 Present: bijan, Rinke, MIchaelSmith, MarkusK, MartinD, IanH, uli, Alan, bmotik, Sandro, zhe, vit, bcuencag, pfps, Alan_Ruttenberg, Carsten, Evan_Wallace 18:08:21 Ian: previous *PREVIOUS* minutes 18:08:30 (ok) 18:08:53 JeffP has joined #owl 18:08:53 7th 18:08:54 http://www.w3.org/2007/OWL/wiki/Teleconference.2007.11.14/Minutes 18:09:00 -Alan_Ruttenberg 18:09:06 http://www.w3.org/2007/OWL/wiki/Teleconference.2007.11.07/Minutes 18:09:12 back 18:09:28 ewallace: previous previous minutes list me as evan wallface 18:10:08 +JeffP 18:10:16 sandro: accept them pending the change 18:10:38 PROPOSED: Accept previous previous minutes module fixing Evan's name 18:11:01 +1 to accept previous previous minutes 18:11:02 sandro: fixed them 18:11:12 ACCEPTED: Accept previous previous minutes module fixing Evan's name 18:11:22 I just updated the attendance list to add Uli 18:11:24 Who was missing 18:11:25 PROPOSED: Accept Previous Minutes 18:11:27 SANDRO - please reply to prtvate message 18:11:31 I approve 18:11:34 sandro: haven't been there long enough to be reviewed 18:11:43 +1 wait 18:11:51 +1 18:11:54 IanH: who has reviewed them? 18:11:58 i haven't 18:11:58 I just did 18:12:07 had a quick look 18:12:12 IanH: leave them to next week 18:12:21 ... action item status? 18:12:28 aren't minutes supposed to be ready in 48 hours or less? 18:12:28 sandro: still mulling it over 18:12:40 IanH: move to next week 18:12:48 alanr: did the syntax document (Action 15) 18:13:00 IanH: action 17 qname approval 18:13:17 MichaelSmith: email has been sent, asking about schema components status 18:13:20 yes, PFPS, that's the normal convention. In this case the fault was mostly mine. :-( 18:13:21 In http://www.w3.org/mid/20071115.054530.235781452.pfps@research.bell-labs.com pfps found text in XML Schema spec http://www.w3.org/TR/xmlschema-2/#built-in-datatypes built-in datatypes and facets are both given URIs 18:13:23 Evan, are you willing to write up the steps to clean up the minutes? (on http://www.w3.org/2007/OWL/wiki/Scribe_Conventions) 18:13:34 ... most of the issue has been addressed because peter found relevant parts 18:13:47 ... action was done 18:13:52 + +078910aaaa 18:13:57 IanH: action 18, brain dump? 18:14:03 continue 18:14:05 alanr: haven't dumped, postponed to next week 18:14:18 Zakim, aaaa is me 18:14:18 +jeremy; got it 18:14:21 IanH: f2f agenda 18:14:43 http://www.w3.org/2007/OWL/wiki/F2F.2007.12-Manchester/Agenda 18:14:44 IanH: have collected a list of items to be discussed at the f2f, please look at the agenda 18:14:55 F2F agenda: http://www.w3.org/2007/OWL/wiki/F2F.2007.12-Manchester/Agenda 18:15:04 ... currently on day 1 an overview of language features, imports 18:15:10 Datatypes? 18:15:11 ... two other topics dl and full alignment 18:15:29 ... if you have comments, topics, then you might want to suggest them 18:15:37 suggest F2F topics how? 18:15:37 ... the schedule is going to be quite tight! 18:15:49 q+ 18:15:54 alanr: where did you put the agenda? 18:15:57 zakim, unmute me 18:15:57 pfps should no longer be muted 18:16:06 q? 18:16:11 IanH: link from meetings page, in the irc as well 18:16:33 ... cannot guarantee that every topic will be added 18:16:49 alanr: if you feel that any knowledge needs to be made clear, we can put it in the tutorial 18:16:56 What's the tutorial? 18:17:00 When is it? 18:17:07 IanH: over the course of the next week we will fix the agenda? 18:17:14 q- 18:17:18 (who's this?) 18:17:21 zakim, unmute me 18:17:21 pfps was not muted, pfps 18:17:43 ewallace: would like to discuss the Declaration 18:17:50 ... just the discussion of it 18:17:52 zakim, unmute me 18:17:52 bijan should no longer be muted 18:17:54 q+ 18:18:12 bijan: what's the tutorial? 18:18:31 alanr: orientation, looking who's coming, having a walkthrough of the specs, and doing a Q&A 18:18:42 ... if you have ideas of what should be covered, let us know 18:18:59 zakim, mute me 18:18:59 bijan should now be muted 18:19:00 bianr: is that the same as Overview of language features? 18:19:03 alanr: yes 18:19:09 IanH: are we done? 18:19:10 chair: Ian 18:19:12 s/bianr/bijan 18:19:29 IanH: alan and I will prepare a more concrete agenda 18:19:36 IanH: 2nd F2F meeting 18:19:37 Perhaps, ian should send an email to solicit agenda topics for f2f? 18:19:43 http://www.w3.org/2007/OWL/wiki/F2F2_proposals 18:19:50 ... quite a few have commented already 18:20:05 Beijing 18:20:10 ... any people on the phone who would like to add their response before we come to a decision? 18:20:16 zakim, mute me 18:20:16 pfps should now be muted 18:20:30 q+ to go back to scribing for a second 18:20:32 ... uli, boris, bernardo... you didn't respond yet? 18:20:40 No preference 18:20:41 oups - i thought i had: preference for washington 18:20:47 beijing or DC 18:20:48 ... any preference Washington, Bejing, Sydney 18:20:59 JeffP: beijing 18:21:00 zakim, unmute me 18:21:00 bijan should no longer be muted 18:21:05 prob. washington for me 18:21:10 I prefer DC, at risk for Beijing, no to sydney 18:21:23 I can probably neither come to Washington nor Beijing, but Sydney may be possible 18:21:46 no preference for me for F2F2 18:21:52 alanr: will put the raw responses on the voting list 18:21:52 zakim, mute me 18:21:52 bijan should now be muted 18:22:11 two 18:22:17 IanH: it is overwhelming for Washington... two people Beijing, one Sydney, everybody else Washington 18:22:35 IanH: it's a no brainer... almost unanimous for Washington 18:22:47 +1 18:22:50 ... peter can go ahead with the OWLED colocation thing? That's my proposal 18:23:03 PROPOSED: F2F2 will be in Washington DC 18:23:07 +1 18:23:09 +1 18:23:10 +1 18:23:11 +1 18:23:13 +1 18:23:15 +1 18:23:16 +1 18:23:17 +1 18:23:31 IanH: lots of agreement, no disagreement 18:23:43 RESOLVED: F2F2 will be in Washington DC 18:23:48 IanH: finished with the admin 18:24:10 q+ have we decided the dates on F2F2? 18:24:12 +1 to DC 18:24:15 ack alanr 18:24:15 alanr, you wanted to go back to scribing for a second 18:24:19 alanr: if Conrad could put his work on the cleanups on the wiki 18:24:23 q- 18:24:23 q? 18:24:32 IanH: task forces stuff 18:24:49 IanH: it would be useful to get some feedback from them 18:25:03 IanH: jeremy to say something about the UFDTF 18:25:05 ?q 18:25:09 q? 18:25:10 Yes he is :) 18:25:27 q+ testing zakim 18:25:28 jeremy: let me think 18:25:31 q? 18:25:34 ack 18:25:34 ... can I go second? 18:25:41 ack testing 18:25:43 ack zakim 18:25:45 IanH: Rich annotations? Bijan? 18:25:53 zakim, unmute me 18:25:53 bijan should no longer be muted 18:26:07 bijan: I wrote up a proposal, some use cases, not finished 18:26:18 ... I ran them by several people, e.g. Alan Rector 18:26:40 ... somebody wanted to use them for patterns (value partitions) 18:26:49 ... that's fine in my proposal, haven't written it up 18:27:01 ... (Jeremy?) using reification for axiom annotations 18:27:07 oooh 18:27:23 ... I guess in that exchange with Boris one option would be to ... the anotations 18:27:30 +1 on importance of axiom annotations 18:27:35 ... would remove a lot of the usefullness of annotations 18:27:43 q? 18:27:48 q+ to mention issue with rich annotations 18:27:52 bijan: proposal is 90% done... 18:28:03 ... would be nice to get some sense of what we're going to do with it 18:28:12 IanH: there is a fairly wellformed proposal on the table 18:28:17 ... please give some comments 18:28:21 the current proposal is http://www.w3.org/2007/OWL/wiki/Annotation_System correct? 18:28:26 Yes 18:28:33 q? 18:28:37 alanr: concerned about the multiple domains of interpretation/ multiple worlds/ multiple models aspect of it 18:28:41 ack alanr 18:28:42 alanr, you wanted to mention issue with rich annotations 18:28:59 ... part of the concern was that it's fairly new, and unexplored... want a warm fuzzy feeling that it's well understood 18:29:10 zakim, mute me 18:29:10 bcuencag should now be muted 18:29:18 ... second issue is that I don't know whether and how it would affect the RDF semantics 18:29:38 ... could you comment on how it affects the OWL Full aspect of it, in the RDF sense 18:29:43 q? 18:29:48 bijan: I have not realised an RDF mapping 18:30:03 ... one could use different extensions: multiple files with pointers analogous to owl:imports 18:30:12 ... minimal mutilation of everything, and easy to understand 18:30:26 ... other than that: is that enough to get you going? 18:30:43 alanr: yes, just to say where I am on it: how much of the proposal is dependent on that 18:31:03 ... is that the central part of the proposal? If it's left out, what will be left? 18:31:20 bijan: it's a major part... another part is the idea to have blobs of annotations instead of nested or chained 18:31:31 ... in the current anotations have to booted in the axiom 18:31:51 ... a lot of people I talked to want to be able toa ssociate fairly elaborate structures to an entity or axiom 18:32:08 q+ to comment 18:32:16 IanH: until more people have had a chance to have a look at that... we might as well leave that 18:32:28 we do have it on f2f 18:32:31 bijan: suggest that it becomes an official agenda item 18:32:40 IanH: action item to go and read it? 18:33:06 q? 18:33:07 bijan: if I know its' going to be on the agenda I could (re)start an email discussion about this 18:33:14 sandro: no need to do an action item 18:33:22 bijan: if its on the agenda, I will start a discussion 18:33:33 zakim, mute me 18:33:33 bijan should now be muted 18:33:41 IanH: why don't you start a discussion, and if there's a significant response to that we can put it on the agenda 18:33:42 q? 18:33:48 alanr: who are the stakeholders on this? 18:33:56 ... and have an action item to review this? 18:34:05 ... for them (that holds for me) 18:34:11 I'm a stakeholder and will review 18:34:13 IanH: anyone else? 18:34:16 I'll stick my hand up 18:34:26 I will read it by next week. Does this cound as a review? 18:34:34 alanr: more strongly, if you think it's important and you might object, you're a stakeholder 18:34:35 q? 18:34:49 ack jeremy 18:34:49 jeremy, you wanted to comment 18:34:52 IanH: why not let jeremy speak, and let people mull over whether they are stakeholders 18:35:11 jeremy: by having the OWL Full semantics in multiple documents is very complicated 18:35:15 JeffP has joined #owl 18:35:17 q? 18:35:18 ... far away from owl 1.0 18:35:28 q+ to see if I understand bijan's idea 18:35:40 could we ask for a decision on this next week 18:35:42 ... out of court. More about 'lets' put some wacky stuff in' instead of a conservative improvement over 1.0 18:35:55 If I've understood things correctly, the idea is not to have one semantics distributed over different documents (Bijan, please correct me if I'm wrong). 18:35:55 IanH: you're talking yourself into being a stakeholder 18:36:04 jeremy, as usual, I can't understand what you are saying -- could you please talk louder? 18:36:15 jeremy: just articulating how a large part of the OWL community would feel about this move away from 1.0 18:36:26 (me neither) 18:36:36 The idea is that you just have different, independent documents. They have nothing to do with each other. You can, however, query them together using, say, SPARQL. 18:36:46 jeremy: this seems a big change from 1.0 in terms of the OWL Full semantics 18:36:53 ... sounds like a non starter (?) 18:36:53 q? 18:36:59 ack alanr 18:36:59 alanr, you wanted to see if I understand bijan's idea 18:37:06 q? 18:37:12 alanr: by putting it into different files, we are just making things independently and unconnected 18:37:22 ... each separately is an OWL Full document 18:37:22 that's fine 18:37:37 That's one reasonable way to go yes 18:37:41 ... that correct bijan? 18:37:51 q? 18:37:52 jeremy: strikes me as a 'big' change (in the eye of the beholder) 18:37:57 ... mouses and elephants 18:38:08 IanH: clearly needs to be discussed in some more detail 18:38:12 But this is really no change: each document is still interpreted as it was interpreted in OWL 1.0. You can use either Full or DL semantics, moreover. 18:38:15 +1 to draft Jeremy as stakeholder :) 18:38:22 ... perhaps jeremy and bijan could exchange some emails on this topic? 18:38:30 ... then the rest of us can eavesdrop 18:38:34 Fine 18:38:36 ... how would that be? 18:38:39 q? 18:38:45 I can be on call too... 18:38:51 if desired 18:38:59 jeremy: not very enthusiastic, at least I get payd for it 18:39:06 IanH: I'll take that as a yes 18:39:13 ... move on to datatypes 18:39:25 There was a telecon! 18:39:32 IanH: a lot of email traffic, no taskforce... 18:39:33 There is! 18:39:42 q? 18:39:45 alanr: summarise where we came to in the first meeting 18:39:48 Cleaned up datatype telecon minutes at http://www.w3.org/2007/OWL/wiki/DataType.Telecon.2007.11.19/Minutes 18:39:48 (who's this?) 18:39:55 Mike smith 18:40:35 MichaelSmith: two types of external datatypes... those that include ID's which can be externally referenced, and those that can't 18:40:53 ... on the first we are waiting on the XML Schema wg 18:40:54 q? 18:41:07 (on the second) 18:41:16 to modify structural specification to require the approach described in http://www.w3.org/TR/swbp-xsch-datatypes/#sec-id-attr when referencing external XML Schema definitions with id attributes 18:41:29 ... moving forward on the approach outlined in the best practices document for the case where we do have IDs 18:41:47 IanH: what kinds of things wouldn't we be able to do without ID's 18:41:48 referencing externalk datatypes defined by someone else 18:41:51 big file of anonymous datatypes 18:41:54 external 18:42:15 MikeSmith: perfectly valid xml schema exists without IDs... if you want to reuse such schema types you have a problem 18:42:17 q? 18:42:22 ... on the semantic web 18:42:27 So one would have to cut and paste that datatype definition into a different file 18:42:39 ... if the author does have the semweb in mind, we have a solution. 18:42:44 ... from the best practices 18:42:52 IanH: we won't lose expressivity, just some rework 18:42:57 literal inclusion of the file within the OWL file 18:43:11 Yes 18:43:13 MikeSmith: yes, about reusing existing XML schema definitions 18:43:17 IanH: unary datatypes? 18:43:31 MikeSmith: yes, the external datatypes only discussed about unary datatypes 18:43:40 ... one other thing, that we discussed 18:43:53 ... don't know if we want to put that in to a proposal first or... 18:44:03 IanH: try us with the other item first 18:44:07 (at the telecon - some e-mail traffic on n-ary) 18:44:20 MikeSmith: inline xml as opposed to what is in the member submission 18:44:21 Issues with XML Schema in thread starting at http://www.w3.org/mid/474203BC.50307@hpl.hp.com and with attempted summary at http://www.w3.org/mid/1195586107.6320.52.camel@msmith-laptop 18:44:28 ... I think it hit some kind of completion point 18:44:34 ... we understand what could be done, 18:44:50 q? 18:44:53 ... if we want to use xml schema types inline, ... 18:45:04 ... we need feedback from people about this 18:45:08 I got negative feedback from OWL API/Protege4 author Matthew Horridge 18:45:10 I'll ask HP implementors 18:45:17 IanH: another case where people need to have a look and get feedback 18:45:19 q+ unary datatype 18:45:21 I would expect negative feedback from TopQuadrent (Holger) 18:45:31 Oh, xml schema syntax inline 18:45:32 IanH: negative with respect to which option? 18:45:36 q? 18:45:45 q? 18:45:54 alanr: I was advocating taking this as our first point strictly from a simplicity point of view 18:46:03 ack unary 18:46:08 ack datatype 18:46:14 q+ to talk about schema syntax 18:46:17 q+ 18:46:22 ... doesn't require any vocabulary, might reduce the load at the expence of annoying but sufferable softare adaptations 18:46:29 well, what about all the corner cases in having inline XML Schema content? 18:46:37 IanH: first bijan, then jeffP 18:46:38 zakim, unmute me 18:46:38 bijan should no longer be muted 18:46:44 ack bijan 18:46:44 bijan, you wanted to talk about schema syntax 18:47:01 bijan: I originally was thinking that using the XML schema syntax would be useful even with its limitations 18:47:17 ... main argument against it: if we use XSD it restricts us in how we... 18:47:24 ... would be apply new datatypes such as rational 18:47:34 ... we could change it, but XSD guys might not like that 18:47:56 ... unary datatypes with definitions, and totally different for n-ary: two different syntaxes 18:48:01 ... if we do it ourselves 18:48:09 how about noting the issue and coming back to it in a few months? 18:48:23 ... some advantages if we do it ourselves, otherwise we have to take the XSD WG into account 18:48:41 q? 18:48:42 ... if we make our home-made one it would probably be more uniform and more under control 18:48:51 zakim, mute me 18:48:51 bijan should now be muted 18:48:53 IanH: sounds like a convincing argument 18:48:55 q+ to ask whether we *at least* need to support XML syntax 18:48:59 ack jeffp 18:49:00 agree with ian no premature decision 18:49:05 JeffP: question for mike... can we see the unions as well? 18:49:15 MikeSmith: there hasn't been a proposal to include unions no 18:49:31 JeffP: if we don't have unions for datatypes. Won't we have too complicated datatypes 18:49:47 With external datatypes they could use union,a faict 18:49:49 ... users might really want to reuse existing datatypes that they have 18:50:07 IanH: if people don't use unions, then ... 18:50:10 q? 18:50:10 (sorry missed that) 18:50:11 but we had counter-examples for this, Jeff! 18:50:28 ack alan 18:50:28 alanr, you wanted to ask whether we *at least* need to support XML syntax 18:50:29 -1 to requiring XML syntax 18:50:30 alanr: might at least support the XML syntax. At least vs. might 18:50:43 uli, could you send a pointer? 18:51:08 Jeff, no - somewhere in the list of emails flying past 18:51:11 IanH: if pople don't use unions, then the kinds of datatypes thay would be defining would be very simple, then not referencing 18:51:16 q? 18:51:26 ... external datatypes using wouldn't be so much of an issue 18:51:35 IanH: Mike was saying something about a proposal 18:51:39 uli, which email in the mailing list? 18:51:43 to modify structural specification to require the approach described in http://www.w3.org/TR/swbp-xsch-datatypes/#sec-id-attr when referencing external XML Schema definitions with id attributes 18:51:52 MikeSmith: proposal for modifying structural specificaiton 18:51:53 +1 to this proposal 18:51:58 +1 18:52:07 (look jeremy and bijan agree!) 18:52:14 :-) 18:52:41 +1 18:52:43 IanH: that must mean everyone else is on board as well 18:52:51 sounds reasonable :-) 18:53:01 ... this would need to be formed into a proposal that we might resolve 18:53:09 zakim, unmute me 18:53:09 bijan should no longer be muted 18:53:16 q+ 18:53:20 q+ to note normativity (lack of) 18:53:21 alanr: is there a section that we could read, a section that says everything about it? 18:53:34 MikeSmith: the alternative would be to insert text into the structural document 18:53:44 I like this 18:53:50 +1 to doing the edit 18:53:51 -1 to this proposal, as OWL 1.1 already has an adequate solution 18:53:52 that, ians suggestion 18:53:53 I prefer inserting text 18:53:58 IanH: add it to the document, and then come back with a proposal to accept the edit in the document 18:54:01 q- 18:54:10 zakim, unmute me 18:54:10 pfps should no longer be muted 18:54:10 q? 18:54:11 alanr: please comment in sandro's format 18:54:14 q- 18:54:31 IanH: peter objects? but I guess that when you come back with the proposal to accept your editing... 18:54:39 pfps: the message stands for itself 18:54:58 ... owl 1.1 already has its own syntax solution which eliminates the need for hacked-up xml schema documents 18:55:09 alanr: there is our own syntax for defining datatypes? 18:55:20 ... a requirement is to be able to reuse other people's documents... 18:55:30 q+ to respond to peter 18:55:30 q? 18:55:33 zakim, unmute me 18:55:33 bijan was not muted, bijan 18:55:36 pfps: there's a vanishingly small number of xsd documents in that form 18:55:40 alanr: bijan? 18:55:46 q? 18:56:02 bijan: not so much about reusing... I would be perfectly reasonable to define my own datatypes in xml schema. 18:56:19 ... I have reasons for doing them inline sometimes, and for doing them outline in some cases 18:56:21 ack jeremy 18:56:21 jeremy, you wanted to respond to peter 18:56:21 zakim, mute me 18:56:23 bijan should now be muted 18:56:24 q? 18:56:35 jeremy: the data may well be useful for an owl or webservice application 18:56:42 XML Schema is a really complex specification, though. 18:56:44 +1 for reuse xml schema datatypes 18:56:56 ... since the rest of the world reads xml datatypes already, we might as well do it ourselves as well 18:57:06 ... yes, it's awful, but that's life 18:57:19 I don't understand quite what exactly is mean with "reusing XML Schema datatypes". 18:57:22 IanH: bijan and jeremy are saying that there isn't actually a huge cost to it? 18:57:38 ... we just need to add id's 18:57:49 and by the user 18:57:50 Boris, I currently can create a set of XML Schema datatypes using XML Schema 18:57:51 alanr: the documents need to be understood by the reasoners that support them 18:57:52 Why not? 18:57:55 Er 18:57:57 Why not use that? 18:58:10 IanH: the added overhead for implementers is that they need to add support for xml datatypes 18:58:20 pfps: you are going to require them to do that 18:58:32 MikeSmith: if you do reference them, you do it in the required way 18:58:33 But are these only the elementary data types (sting etc), or are we including the complex datatypes as well (elements, complexType, etc.)? 18:58:39 there may be an issue with some facets 18:58:57 alanr: add a delimited specific set of datatypes... but implementers could hook into the syntax to support more complex datatypes 18:59:04 bmotik, yes, the imported datatype must be legal in OWL 1.1 18:59:05 simple types only 18:59:05 q? 18:59:12 boris, I think we mean simple types only 18:59:15 MikeSmith: owl 1.0 docs are a little bit inconsistend (integer + string, another doc has a longer list) 18:59:29 ... we are not really clear on what's required for implementors and what's not 18:59:36 But if an implemented handled something more expressive, e.g., union, it seems harmless to let them address it by Id 18:59:36 ... maybe clarifying that is important 18:59:51 Referencing an external .xsd document from OWL parsers might be a pain for implementors. 18:59:55 IanH: a side chat between boris and jeff, trying to clarify whether we are only talking SimpleTypes 19:00:04 q+ 19:00:13 ... I was presuming we're talking about more complex types, not unions, but facets 19:00:34 MikeSmith: when I was responding to Jeff, I was talking about inline... now we're talking about external datatypes 19:00:37 What is "external"? 19:00:47 I.e., defined in an XML Schema file 19:00:56 ... I don't think there was a proposal to restrict what kinds of external xsd datatypes are allowed 19:00:58 q+ to say "no to complex stuff" 19:01:22 +1 to jeremy's point about complex types 19:01:22 What exactly could you write in this external document? Could you do much more than just apply factes? 19:01:24 q? 19:01:28 IanH: reuse the external xsd in your owl file 19:01:29 ack jeremy 19:01:41 jeremy: complextype and simpletype are technical terms 19:01:49 jeremy: a simpletype can be very complicated 19:01:51 I could define a type hierachy 19:01:56 IanH: complicated rather than complex them 19:02:02 I coudl define complex types, but they wouldn't be usable in OWL 19:02:04 ... does this answer boris' questions? 19:02:13 More or less. 19:02:17 ... perhaps Boris could say whether he understands everything now? 19:02:17 What is a type hierachy? 19:02:20 q? 19:02:24 ack bijan 19:02:25 bijan, you wanted to say "no to complex stuff" 19:02:53 bijan: we need to be a little bit careful wrt the types you are about to reference are types that are 'allowed' 19:03:05 ... presumably no current reasoner can do anything with it 19:03:18 ... the type that you reference must be definable in the inline syntax as well 19:03:25 q? 19:03:39 zakim, mute me 19:03:39 bijan should now be muted 19:03:40 ... qnames wouldn't be types you can use and dereference from 19:03:46 IanH: clarified a lot for me 19:03:53 Boris, I can define a string type that is a subclass of xsd:string 19:03:54 ... action on Mike 19:03:56 And subclasses of that 19:03:59 Etc. 19:04:04 ... to make a change that encapsulates his proposal 19:04:23 IanH: skipped over the user facing documents 19:04:27 +Vipul_Kashyap 19:04:28 Wiki question: can we approve changes out-of-order? 19:04:28 q? 19:04:39 jeremy: three telecons so far 19:04:56 For example, if two people make changes in one order, but we want to approve them in different order (or even roll-back one change), is this possible, and if so, how? 19:04:59 ... quite a lot of disagreement, the main point of the telecons was sharing and exchanging views 19:05:01 Re: numerics, I've been working on an explantion document in support of datatypes and n-ary predicates: http://www.w3.org/2007/OWL/wiki/OWL_Numerics 19:05:13 ... agreement on different users prefer docs in terms of their domain and use cases 19:05:15 Vipul has joined #owl 19:05:21 q? 19:05:23 ... risk that we like to produce more docs than we could 19:05:40 ... some members are keen on docs that represent user communities 19:05:53 ... another opinion is that we should produce very little 19:06:08 ... another point of disagreement is to do with what the overview should look like 19:06:12 Well, part of that view (which is mine) is there is other venues which are, perhaps, more appropriate 19:06:19 q? 19:06:22 ... input is owl 1.0: brief summary + list of constructs 19:06:32 ... owl 1.1 summary which is much briefer 19:06:46 ... not anywhere near resolving anytime soon 19:07:04 ... a further issue is that non-wg members have interesting work that they would like to contribute to the group 19:07:24 ... how much can we interact with people not on the wg 19:07:51 q? 19:07:53 IanH: not really a constraint on interaction, but if the cdocuments reflect a lot of their input, then their names could not be on the docs 19:08:05 I thought it was Jeremy that was following up... 19:08:11 Vipul: sent anemail to michel and ... as to what their expectations are 19:08:19 i asked sandro 19:08:37 IanH: fair to say, ongoing, progress is made, but significant issues? 19:08:44 also there are action items for UFDTF 19:08:56 jeremy: for the overall taskforce, yes, I think we're making disappointingly small progress so far 19:09:11 Alan is more optimistic than Jeremy, but that may expose a flaw ... 19:09:14 Vipul: one thing we did agree on is to identify the set of users that would 19:09:22 in Alan's optimism 19:09:23 q? 19:09:28 ... be targeted by these docs 19:09:45 ... CIO's Enterprise Architects, developers: list on an external website 19:09:59 Also started page trying to define who the targets of the documentation are 19:10:09 IanH: we'll be discussing this more on the F2F... hopefully more progress on these issues 19:10:12 ... then 19:10:16 http://www.w3.org/2007/OWL/wiki/Who_Reads_Our_Documents 19:10:42 IanH: issues ... first is Issue 13: quotation and CURIES 19:10:52 sandro: CURIES as in Marie Curie 19:11:23 alanr: peter and I had a breef discussion about our original decision to use SPARQL 19:11:28 Nasty in the RDF/XML yes? 19:11:29 Did sparql not use CURIE because it wasn't reaching REC any time soon? 19:11:35 ... peter thought it was limited, suggested to go for full CURIES instead 19:11:43 q? 19:11:47 ... no problem: a dependency as they're not a standard yet 19:12:11 ... if others think that CURIES are good, then I'm happy too 19:12:19 q? 19:12:20 IanH: are we in a position that we could resolve 19:12:34 sandro: the state of CURIES, we don't know they're ever going to be a rec 19:12:42 q+ to ask where would we use these 19:12:48 q? 19:12:50 pfps: we could pull the stuff out of the CURIE spec 19:13:01 pfps: we could copy/paste CURIE text if they do not reach REVC 19:13:06 alanr: someone from the group suggested we might monitor this 19:13:14 q? 19:13:21 ... and do a fallback when it turns out to not become a rec 19:13:28 I'll Dave tomorrow 19:13:38 ^ask^ 19:13:47 ack bijan 19:13:49 bijan, you wanted to ask where would we use these 19:13:54 q? 19:13:58 sandro: in RIF there was some discussion, in the end decided not to... not relevant...? 19:14:17 q+ 19:14:22 q? 19:14:22 bijan: if CURIES are not legal element names, then how would this effect the RDF serialisation 19:14:34 I see CURIs in RIF BLD at http://www.w3.org/2005/rules/wg/bld/draft-2007-10-30#head-7c71117f168aef019182ae8e8ad8bc542c76868d 19:14:42 zakim, mute me 19:14:42 bijan should now be muted 19:14:43 ... probably would require additional processing 19:14:44 right -- CURIE in AS, or in some of the serializations? 19:15:00 That doesn't always work 19:15:12 alanr: if the local part is not a valid part of a qname then it's expanded to an escaped uri 19:15:17 q? 19:15:19 no that doesn't make sense 19:15:26 ... I don't create extra namespaces, I fully quote them (in angle brackets) 19:15:30 ack jeremy 19:15:45 Yes, i.e., properties 19:15:50 pmid:1234 -> 19:15:51 jeremy: certain uris that might occur as property uris can not be serialised as RDF uris 19:16:05 Metaquestion: do we expect people to use the functional-style syntax directly? If not (i.e., if this syntax is used just in the spec), do we care about abbreviating URIs? 19:16:06 q+ to reply 19:16:10 ... in alan's cases we're talking about subject/object uris, in that case no problem 19:16:17 can always use description/about 19:16:24 +1 19:16:26 ... in predicate position some curies cannot be serialised in RDF/XML 19:16:30 zakim, ack bijan 19:16:30 unmuting bijan 19:16:31 bijan, you wanted to reply 19:16:32 I see no one on the speaker queue 19:16:39 q? 19:16:40 ... this a known limitation in RDF/XML, and we should ignore it 19:16:52 bijan: that's fine jeremy, that's what I wanted to know 19:17:01 ... if that's ok with you, then I'm fine with it 19:17:09 zakim, mute me 19:17:09 bijan should now be muted 19:17:14 jeremy: RDF/XML went to REC with this as a known bug 19:17:37 q+ to repeat the AS vs CS quest 19:17:40 PROPOSED: to base abbreviated URIs on CURIES not QNAMES 19:17:40 alanr: you can already use an arbitrary URI already in OWL 1.1 which cannot be serialised as RDf 19:17:53 jeremy: not an OWL problem, an RDF problem 19:17:53 But curies don't help in RDF/XML *at all* 19:18:01 q? 19:18:07 sandro: is this just about the abstract syntax? 19:18:16 alanr: only effect the functional syntax 19:18:26 I would perhaps change my position after discussion with colleagues (dave and andy) 19:18:38 functional sytax 19:18:42 structural specification 19:18:43 IanH: structural syntax 19:18:48 alanr: functional style syntax 19:18:49 PROPOSED: to base functional style syntax abbreviated URIs on CURIES not QNAMES 19:18:56 "Structural Specification and Functional-Style Syntax" 19:18:59 +1 19:19:06 +1 19:19:19 jeremy: have you seen my notes? I might change my vote tomorrow by email 19:19:34 put it on agenda next week 19:19:39 IanH: what's the best way forward? Resolve this now, backtrack? Push it to next week? 19:20:01 IanH: put it on the agenda for next week. You'll be in a position to give a definitive yay or nay 19:20:13 IanH: we resolved that we will resolve something 19:20:24 IanH: issue 2 is the final thing on the agenda 19:20:41 ... we already resolved that we fix up this problem for alldisjoint wrt the RDF mapping 19:21:19 q? 19:21:30 ... the question arose as to whether we make the language symmetrical and add constructs for things in the structural syntax that use lists 19:21:35 -MartinD 19:21:45 differentindividual 19:21:47 ... boris what are the other ones 19:21:49 sameindividual 19:21:55 pfps: union, intersection 19:22:00 ? 19:22:08 Union and intersection are already OK 19:22:09 Doesn't union and intersection allready nary 19:22:13 +1 to differentindividual 19:22:16 IanH: really correct peter? 19:22:31 ... in RDF they are mapped to multiple pairwise 19:22:32 It is equivalentClasses, equaivalentProperties, disjointClasses, disjointProperties 19:22:44 alanr: alldifferent was already in the first version? 19:23:01 pfps: if you want to go for a same-sized translation, there are only two that are lists 19:23:03 sameIndividaul, differentIndividuals 19:23:10 19:23:12 19:23:14 19:23:14 ifferentIndividuals(iID1 … iIDn) 19:23:14 _:x rdf:type owl:AllDifferent . 19:23:15 04_:x 04owl:distinctMembers04 T(SEQ iID04104 … iID04n04) . 19:23:16 19:23:17 19:23:19 19:23:20 19:23:22 19:23:23 19:23:25 19:23:25 http://www.w3.org/TR/owl-semantics/mapping.html#4.1 19:23:25 It does not enable roundtripping. 19:23:26 so differentindividuals already handled 19:23:27 IanH: not a direct syntax as we have for alldisjoint 19:23:38 pfps: the only rationale for having a direct syntax for some of them is 19:23:57 that the obvious translation is n^2 and the non-obvious translation needs a trick 19:24:09 IanH: boris says that it makes the problem for roundtripping 19:24:24 do we have specification of what roundtripping means? Is it an agreed upon requirement? 19:24:38 q? 19:24:42 how big is this problem? 19:24:43 No 19:24:44 For backwards-compatibility we might translate things as usual only if n =2 19:24:53 If n != 2, we might use the new mapping 19:25:17 zakim, unmute me 19:25:17 bijan should no longer be muted 19:25:22 q? 19:25:32 pfps: we always have a roundtrip from functional to RDF and back, but if we already have a document in RDF then we cannot do roundtripping unless 19:25:41 Sure, but if you have an OWL 1.1 RDF document (with new vocabulary), then things should be round-trippable. 19:25:56 ... we have a direct mapping 19:26:02 q+ 19:26:05 pfps: quantitative vs. qualitative improvement 19:26:10 zakim, unmute me 19:26:10 bmotik should no longer be muted 19:26:14 pfps: reason is bloat 19:26:14 +1 to pfps 19:26:16 zakim, mute me 19:26:16 bijan should now be muted 19:26:20 -Sandro 19:26:21 q? 19:26:25 +1 to pfps too 19:26:32 Arg -- wrong button 19:26:40 q? 19:26:44 q- 19:26:48 sandro left call 19:26:50 sandro hung up 19:27:03 I pressed hangup instead of unmute. 19:27:07 boris: I understand the point regarding the bload 19:27:17 +Sandro 19:27:21 roundtripping not possible given backwards compatibility 19:27:31 ... if we now extend the language with this new construct... new ontology, serialise as RDF then we can do roundtrip 19:27:40 I don't know if it matters 19:27:47 ... if you use owl 1.1 RDF and owl 1.1 AS then things should be round-trippable 19:27:57 IanH: this wasn't the simple discussion I was anticipating 19:28:01 Zakim, mute me 19:28:01 bmotik should now be muted 19:28:13 ... are not going to get through this in the remaining 3 minutes of this telecon 19:28:25 ... aim for email exchange to clarify the matter 19:28:34 IanH: last item.... aob? 19:28:37 ... any of it? 19:28:49 +1 bye 19:28:51 doe and dusted 19:28:52 -Vipul_Kashyap 19:28:56 IanH: declare us finished for this week 19:28:57 bye bye 19:28:57 -Evan_Wallace 19:28:58 -jeremy 19:28:59 bye 19:28:59 -bijan 19:29:00 bye 19:29:02 -Carsten 19:29:03 bye 19:29:03 yep 19:29:03 -MIchaelSmith 19:29:05 -JeffP 19:29:05 -bye 19:29:06 -uli 19:29:06 bye 19:29:07 -vit 19:29:07 -MarkusK 19:29:08 zakim, unmute me 19:29:09 Rinke should no longer be muted 19:29:11 -bcuencag 19:29:22 -bmotik 19:29:31 -pfps 19:30:00 -IanH 19:30:38 -zhe 19:31:06 http://www.w3.org/2007/OWL/wiki/Scribe_Conventions 19:31:16 http://www.w3.org/2007/OWL/wiki/Teleconference.2007.11.21/Minutes 19:31:19 Remove Zakim chit chat such as people entering, leaving, q+, acks, who is here, etc. 19:31:21 Move scribes own comments (as opposed) into irc syntax 19:31:23 Sometimes reorder to make discussions more coherent 19:31:25 Add section headers 19:32:37 Adding {{Action|4}} and {{Issue|23}} 19:35:04 %7B 19:35:37 -Sandro 19:35:39 -Alan 19:35:40 SW_OWL()12:00PM has ended 19:35:41 Attendees were Rinke, bijan, MIchaelSmith, MarkusK, MartinD, bmotik, IanH, Alan, uli, Sandro, vit, pfps, bcuencag, Alan_Ruttenberg, Carsten, Evan_Wallace, zhe, JeffP, +078910aaaa, 19:35:43 ... jeremy, Vipul_Kashyap 19:36:09 jeremy has left #owl 20:02:04 uli has left #owl 21:49:40 Zakim has left #owl 22:30:59 IanH has joined #owl