17:52:23 RRSAgent has joined #owl 17:52:23 logging to http://www.w3.org/2008/11/19-owl-irc 17:52:30 Zakim, this will be owlwg 17:52:30 ok, pfps; I see SW_OWL()1:00PM scheduled to start in 8 minutes 17:52:40 RRSAgent, make records public 17:55:05 msmith has joined #owl 17:55:09 IanH has joined #owl 17:55:35 zakim, this will be owlwg 17:55:35 ok, msmith; I see SW_OWL()1:00PM scheduled to start in 5 minutes 17:55:45 ScribeNick: msmith 17:55:47 uli has joined #owl 17:55:57 RRSAgent, make records public 17:56:29 SW_OWL()1:00PM has now started 17:56:37 Rinke has joined #owl 17:56:39 +msmith 17:56:49 ewallace has joined #owl 17:56:59 +IanH 17:57:17 zakim, who is here? 17:57:17 On the phone I see msmith, IanH 17:57:18 On IRC I see ewallace, Rinke, uli, IanH, msmith, RRSAgent, Zakim, pfps, baojie, trackbot, sandro 17:57:57 +Evan_Wallace 17:58:01 (I cannot dial in, but will try to follow as much as I can on IRC) 17:58:09 MarkusK_ has joined #owl 17:58:51 +??P10 17:59:01 zakim, ??P10 is me 17:59:01 +uli; got it 17:59:05 zakim, mute me 17:59:05 uli should now be muted 17:59:12 bcuencagrau has joined #owl 17:59:43 bmotik has joined #owl 17:59:48 +Peter_Patel-Schneider 18:00:14 +??P12 18:00:17 zakim, who is here? 18:00:17 On the phone I see msmith, IanH, Evan_Wallace, uli (muted), Peter_Patel-Schneider, ??P12 18:00:20 Zakim, ??P12 is me 18:00:20 On IRC I see bmotik, bcuencagrau, MarkusK_, ewallace, Rinke, uli, IanH, msmith, RRSAgent, Zakim, pfps, baojie, trackbot, sandro 18:00:23 +bcuencagrau; got it 18:01:10 ianh: regrets from Ivan, Alan 18:01:15 zakim, who is here? 18:01:15 On the phone I see msmith, IanH, Evan_Wallace, uli (muted), Peter_Patel-Schneider, bcuencagrau 18:01:17 On IRC I see bmotik, bcuencagrau, MarkusK_, ewallace, Rinke, uli, IanH, msmith, RRSAgent, Zakim, pfps, baojie, trackbot, sandro 18:01:21 +??P13 18:01:24 +Sandro 18:01:30 Zakim, ??P13 is me# 18:01:30 +me#; got it 18:01:30 Topic: Admin 18:01:37 zakim, who is here? 18:01:37 On the phone I see msmith, IanH, Evan_Wallace, uli (muted), Peter_Patel-Schneider, bcuencagrau, me#, Sandro 18:01:37 Zakim, ??P13 is me 18:01:40 On IRC I see bmotik, bcuencagrau, MarkusK_, ewallace, Rinke, uli, IanH, msmith, RRSAgent, Zakim, pfps, baojie, trackbot, sandro 18:01:41 Zakim, mute me 18:01:43 I already had ??P13 as me#, bmotik 18:01:44 sorry, bmotik, I do not know which phone connection belongs to you 18:01:54 Zhe has joined #owl 18:02:00 ianh: no agenda ammendments 18:02:02 last week's minutes look fine 18:02:02 Zakim, me# is bmotik 18:02:02 +bmotik; got it 18:02:03 +Zhe 18:02:07 Zakim, mute me 18:02:07 bmotik should now be muted 18:02:12 last week's minutes look acceptable 18:02:15 Zakim, mute me 18:02:15 bcuencagrau should now be muted 18:02:17 oi! 18:02:24 PROPOSED accept minutes of 2008-11-12 telecon at http://www.w3.org/2007/OWL/meeting/2008-11-12 18:02:25 PROPOSED: Accept Previous Minutes (12 November) 18:02:32 +1 18:02:35 +1 18:02:38 +1 18:02:41 +1 18:02:44 +1 18:02:48 +1 18:02:50 RESOLVED accept minutes of 2008-11-12 telecon at http://www.w3.org/2007/OWL/meeting/2008-11-12 18:03:04 F2F4 day 2 minutes are now OK (after Alan's cleanup) 18:03:10 PROPOSED accept minutes of F2F4 Day 2 at http://www.w3.org/2007/OWL/meeting/2008-10-24 18:03:12 +baojie 18:03:14 +1 18:03:19 +1 18:03:19 +1 18:03:21 +1 18:03:25 +1 18:03:26 +1 18:03:26 RESOLVED accept minutes of F2F4 Day 2 at http://www.w3.org/2007/OWL/meeting/2008-10-24 18:03:51 subtopic: pending review actions 18:03:56 +[IPcaller] 18:04:01 I think that the actions are OK (and some were OK last week) 18:04:07 ACTION-238 closed 18:04:08 ACTION-242 closed 18:04:08 ACTION-244 closed 18:04:08 ACTION-246 closed 18:04:08 ACTION-238 Implement the resolutions from the 4F2F closed 18:04:08 ACTION-242 Will make a proposal regarding naming alignment between the functional syntax and RDF syntax based on the summary from http://lists.w3.org/Archives/Public/public-owl-wg/2008Oct/0150.html closed 18:04:09 ACTION-244 Come up with an analysis of whether OWL 2 should include XMLLiteral closed 18:04:13 ACTION-246 Convert review comments to editors notes (except rinke's) closed 18:04:25 Q? 18:04:29 topic: reviewing and publishing 18:05:06 ianh: dec 1 was tentative deadline for last call publishing. we are now getting close 18:05:10 Q? 18:05:22 ... last call checklist has been completed (excepting items already on agenda) 18:05:22 q+ sotd 18:05:27 ... any questions? 18:05:35 Q? 18:05:43 http://www.w3.org/2007/OWL/wiki/Round_4 18:05:44 ack sandro 18:05:52 ack sotd 18:06:04 sandro: we should start on text describing status of documents 18:06:08 q+ 18:06:17 ... it should include changes from previous publish 18:06:25 ... and some context for new documents 18:06:31 ianh: is this in each document? 18:06:51 q? 18:06:54 sandro: people should use the wiki link (provided above) and it will be put in the doc during publishing 18:07:07 ianh: changes wrt last draft? 18:07:10 ack pfps 18:07:17 sandro: yes, last published working draft 18:07:37 pfps: we have a problem with location of features document 18:07:49 sandro: yes, but it doesn't matter for publication 18:08:10 ianh: yes, and all non-correct locations being redirected (or some other resolution) 18:08:19 zakim, who is on the call? 18:08:19 On the phone I see msmith, IanH, Evan_Wallace, uli (muted), Peter_Patel-Schneider, bcuencagrau (muted), bmotik (muted), Sandro, Zhe, baojie, MarkusK_ 18:08:27 sandro: we need an action for this. we discussed it before and nothing happened 18:08:45 ianh: i can take an action. we also said requirements should occur in the name somewhere 18:09:13 alanr has joined #owl 18:09:16 ... I remember "requirements and new features" 18:09:46 ACTION: ian consult with editors on title and clean up wiki location of requirement document 18:09:46 Created ACTION-248 - Consult with editors on title and clean up wiki location of requirement document [on Ian Horrocks - due 2008-11-26]. 18:09:57 q- 18:10:22 ianh: on Round 4 page, this is an action on each editor to handle their documents? 18:10:27 q? 18:10:29 I'll handle the documents I've been editing, no prolem. 18:10:33 Achille has joined #owl 18:10:41 +[IBM] 18:10:48 Zakim, IBM is me 18:10:48 +Achille; got it 18:10:49 ... should we create actions explicitly? I will do so after the telecon (to avoid the time required now) 18:11:34 action: ian make sure SOTD text on http://www.w3.org/2007/OWL/wiki/Round_4 gets filled in 18:11:34 Created ACTION-249 - Make sure SOTD text on http://www.w3.org/2007/OWL/wiki/Round_4 gets filled in [on Ian Horrocks - due 2008-11-26]. 18:11:53 q? 18:12:11 subtopic: Other considerations 18:12:16 issue-145? 18:12:16 ISSUE-145 -- RESOLVED: Which serializations should have mime types and file extensions (and what should they be) -- CLOSED 18:12:16 http://www.w3.org/2007/OWL/tracker/issues/145 18:12:21 subsubtopic: ISSUE-145 18:12:32 q? 18:12:37 yay! 18:12:39 ianh: I understand this to be resolved. Sandro considers himself the contact to IETF 18:13:03 action: sandro send mime-type registrations in to IETF when we do last-call publications 18:13:03 Created ACTION-250 - Send mime-type registrations in to IETF when we do last-call publications [on Sandro Hawke - due 2008-11-26]. 18:13:31 q? 18:13:43 Zakim, who is on the call? 18:13:43 On the phone I see msmith, IanH, Evan_Wallace, uli (muted), Peter_Patel-Schneider, bcuencagrau (muted), bmotik (muted), Sandro, Zhe, baojie, MarkusK_, Achille 18:13:43 subsubtopic: Check with XML Schema WG on name of dateTime ... 18:13:46 q? 18:13:59 ianh: pfps has been point man with XML Schema WG 18:14:27 pfps: I just sent a message to someone in that WG, asking for pointer to final resolution. 18:14:39 ... I will ask about publication schedule 18:15:02 ianh: assuming no satisfactory answer on publication or datatype name. what's the plan? 18:15:15 ... can we make the name of the datatype "at risk" or something? 18:15:15 q? 18:15:22 sandro: I think we can do that 18:15:32 ianh: "subject to change", etc. 18:15:51 q? 18:15:53 sandro: in general we want at risk to be binary (options are A or B), not be open ended 18:16:02 pfps: we can do that for the datatype name 18:16:07 q? 18:16:17 It already says that 18:16:31 It's not. 18:16:34 highlighted 18:16:36 ianh: someone needs to make sure it is binary in document 18:16:42 sandro: is it marked at risk? 18:16:49 q+ 18:16:53 Zakim, unmute me 18:16:53 bmotik should no longer be muted 18:16:54 q? 18:16:58 ack bmotik 18:16:58 ianh: a couple other things are marked at risk 18:17:19 bmotik: is there a style for at risk? it's marked with an editor's note. is that sufficient 18:17:36 sandro: take a look at the RIF BLD for a template 18:17:52 bmotik: // reading from spec // 18:18:07 sandro: we should more formally call out "at risk" 18:18:25 ... in the status of the document section 18:18:54 I made the change that the fallback is owl:dateTime 18:19:03 ianh: we should explicitly say something about the outcome if the risked scenario comes to pass 18:19:11 q? 18:19:19 ... take this offline 18:19:22 q? 18:19:39 q+ 18:19:41 bmotik: several other editorial notes are present. E.g., bug related to xs:decimal 18:19:43 q? 18:20:12 q? 18:20:13 ianh: I suggest saying something more or less the same. 18:20:16 ack pfps 18:20:23 Zakim, mute me 18:20:23 bmotik should now be muted 18:20:29 pfps: XML Schema WG has fixed this, they haven't published the fix 18:20:45 ... I will ask for a pointer so that we can reuse their wording 18:21:27 sandro: procedural threat - we can't normatively reference less mature specifications 18:21:51 ianh: this is the point of the next item. can we point to XML Schema 1.1 18:22:07 sandro: we can for last call and CR, but not for PR and Rec 18:22:37 q+ 18:22:37 ... this could require a different URI for the property if the XML Schema WG can't move fast enough 18:22:43 q? 18:22:48 ack pfps 18:22:49 ... this is bone-headed and we look for a workaround 18:23:07 pfps: we could squat on xsd:our-datetime if we know what it is 18:23:18 q? 18:23:48 ... for decimal, they will be changing the minimal implementation text. we will copy it. if it changes, its ugly but we don't expect that to happen 18:23:54 q? 18:24:23 subsubtopic: freezing features 18:24:38 q? 18:24:44 ianh: we have to decide that we're not going to introduce or change features at this point 18:24:55 ... or we won't be able to keep our schedule 18:25:00 ... any objections to this? 18:25:08 ... when are we going to freeze the documents? 18:25:09 no objection from me 18:25:14 freeze, yes 18:25:45 sandro: any changes need to have more review. so, hopefully no more review 18:26:24 ... there isn't a formal requirement to freeze for publishing. I make a snapshot (probably in the next few days) 18:26:31 q? 18:26:42 ... I don't have a sense of the state editor's believe the documents to be in 18:26:58 ianh: I was expecting to say something like "by the end of this week" 18:27:17 ... then sandro can snapshot and we have one week for typos, etc. 18:27:30 sandro: ok, any changes after that require chair approval 18:27:37 fine by me 18:27:39 Great! 18:27:39 Yes 18:27:39 ianh: editors, is this ok? 18:27:41 yes 18:27:47 yes 18:28:02 ianh: person that might object is mschnei 18:28:20 ... I will contact him after the telecon to confirm his consent 18:28:38 sandro: the one doc we're not republishing is primer. do we want to say something about that? 18:29:01 ... text that suggests we intend to update and publish it in the future. 18:29:04 that sounds good to me 18:29:15 q? 18:29:23 sandro: Do I understand that correctly? 18:29:45 .. maybe we put such text in the ref card status of document, since the docs are related 18:30:09 topic: Issues 18:30:33 q? 18:30:40 subtopic: ISSUE-87 18:30:58 schneid has joined #owl 18:30:59 q? 18:31:02 confirm 18:31:04 Yep 18:31:11 ianh: I understood from minutes this was handled last week 18:31:27 PROPOSED resolve ISSUE-87 as in terms at http://www.w3.org/2007/OWL/meeting/2008-11-12#Mime_types 18:31:48 wrong section 18:31:52 if you put the colon after "proposed" then it gets nicely formatted. 18:32:04 PROPOSED close ISSUE-87 by adding rational datatype but marking it as at risk, pending implementation experience 18:32:27 +??P1 18:32:33 zakim, ??P1 is me 18:32:33 +schneid; got it 18:32:37 zakim, mute me 18:32:37 schneid should now be muted 18:32:46 PROPOSED: close ISSUE-87 by adding rational datatype but marking it as at risk, pending implementation experience 18:32:52 +1 (NIST) 18:32:57 +1 (ALU) 18:32:59 +1 (FZI) 18:33:00 +1 (Man) 18:33:00 +1 (IBM) 18:33:04 +1 18:33:05 +1 (RPI) 18:33:07 +1 (Oxfrd) 18:33:08 +1 18:33:10 +1 (UvA) 18:33:11 +1 (W3C) 18:33:13 s/Oxfrd/Oxford 18:33:24 RESOLVED: close ISSUE-87 by adding rational datatype but marking it as at risk, pending implementation experience 18:33:31 +1 18:33:57 ianh: mschnei is present now, revert to publishing discussion 18:34:18 zakim, unmute me 18:34:18 schneid should no longer be muted 18:34:23 ... we agreed to freeze docs by end of week, modulo minor errors being fixed. can you live with that? 18:34:45 schneid: I've just started some changes. Sunday? 18:35:09 ianh: we need to freeze fairly soon. Can you accept Sunday? 18:35:34 schneid: yes, since RDF semantics is just second draft 18:35:44 ... I can branch the doc and make larger changes on branch 18:35:49 q? 18:35:59 ianh: reluctant to suggest a branch given problems with rqmts doc 18:36:10 schneid: ok, I will focus on the smaller changes 18:36:24 zakim, mute me 18:36:24 schneid should now be muted 18:36:51 ianh: back to issues 18:36:56 q? 18:37:09 q? 18:37:18 PROPOSED: remove xsd:ENTITY, xsd:ID, and xsd:IDREF datatypes as in http://lists.w3.org/Archives/Public/public-owl-wg/2008Nov/0105.html 18:37:23 +1 (IBM) 18:37:27 +1 (W3C) 18:37:29 +1 (FZI) 18:37:30 +1 (C&P) 18:37:35 +1 (Oxford) 18:37:36 +1 (ALU) 18:37:37 +1 (Man) 18:37:45 +1 (ORACLE) 18:37:45 +1 (NIST) 18:37:55 +1 (Uva) 18:37:58 RESOLVED: remove xsd:ENTITY, xsd:ID, and xsd:IDREF datatypes as in http://lists.w3.org/Archives/Public/public-owl-wg/2008Nov/0105.html 18:37:59 +1 (RPI) 18:38:19 ianh: last issue, proposal to simplify structure of annotations 18:38:41 q? 18:38:46 Zakim, unmute me 18:38:46 bmotik should no longer be muted 18:38:50 q? 18:39:05 bmotik: several aspects to this change 18:39:30 ... first, introduce one class AnnotationValue to avoid AnnotationByIndividual AnnotationByLiteral ... 18:39:40 then unify the syntax 18:40:22 q? 18:40:35 q: wondering about alternatives to "URI" 18:40:35 ... second, currently you can have several annotation values per axiom. this is complex. I propose to require separate axioms for multiple annotations 18:40:51 q? 18:40:56 ianh: this wouldn't change the RDF? 18:40:59 sounds good to me 18:41:10 bmotik: correct, but it would make things more round-trippable 18:41:23 sounds fine to me too 18:41:35 q+ 18:41:41 only on IRC 18:41:48 ack alanr 18:41:49 alan - go ahead 18:41:56 q? 18:42:03 Sent mail re: using "URI" in annotations 18:42:14 I saw this e-mail, but I didn't understand it. 18:42:14 See http://lists.w3.org/Archives/Public/public-owl-wg/2008Nov/0120.html 18:42:17 and mentioned at f2f 18:42:40 Looks like a positive change to me. I'm still uncomfortable with the 18:42:40 URI as name for "entities which we may have different 'views' of". 18:42:41 Perhaps there is some variant of URI (that uses the term "view" in it) 18:42:41 that better expresses that it is something identified that we are 18:42:41 We aren't annotating a URI, which is a syntactic element, we are annotating a resource, but without specifying a view 18:42:41 talking about, rather than the identifier of that thing. i.e. in 18:42:41 productions about properties, we use ObjectProperty := URI, not 18:42:43 ObjectPropertyURI := URI 18:42:45 possibilities: AnyView, AllViews, SomeView, Entity, Resource... 18:42:50 tks 18:42:54 q+ 18:42:57 Zakim, unmute me 18:42:57 bmotik was not muted, bmotik 18:42:59 Resource is most clear 18:43:03 ... but they are ... (wait for it) ... URIs (or at least IRIs) 18:43:11 so is a property, then 18:43:25 bmotik: I didn't understand this question. 18:43:39 oooh, good point 18:43:54 We have several views currently 18:43:54 sandro: I believe he's saying that we're not talking about the URI, we're talking about the thing denoted by the URI 18:44:00 yes 18:44:11 But we don't have a specific view 18:44:19 "view" is the language used by Boris 18:44:31 This annotation is to all the "views" 18:44:32 sandro: I think alanr is saying that using URI in the syntax is likely to mislead and that alternative names for the productions could be helpful 18:44:38 yes 18:44:48 sorry - this is hard over text 18:44:52 bmotik: entity is already used in the structural spec 18:45:04 q? 18:45:10 ack bmotik 18:45:11 the non-terminals could be "Resource" instead of "URI", a la RDF 18:45:16 +1 18:45:50 no just for these things that are on the "URI" 18:45:56 q+ 18:45:58 ianh: we're talking just about the proposal here. 18:46:05 q? 18:46:07 ack pfps 18:46:23 pfps: the only change would be for non-terminals ... are there any ... no 18:46:35 ianh: I don't see any non-terminals with URI in them 18:46:50 Alan: we don't see any productions with URI in them anymore. 18:46:53 pfps: URI annotation is gone, so changing URI annotation to Resource annotation isn't helpful 18:46:58 So we can't understand your point. 18:47:17 Alan? 18:47:17 Will review and get back on email. 18:47:18 tks 18:47:32 But we need to resolve it now. 18:47:42 tks? 18:47:45 thanks 18:47:48 We have agreed to finalise documents by end of this week. 18:48:15 looking now 18:48:24 q+ 18:48:30 q? 18:48:33 ianh: given alan is basically in favor... 18:48:43 q- 18:48:53 sandro: we should make the decision, alan can decide to amend the decision 18:48:58 PROPOSED: simplify structure of annotations as per http://lists.w3.org/Archives/Public/public-owl-wg/2008Nov/0115.html 18:49:00 s/decide/propose/ 18:49:10 +1 18:49:11 e.g. AnnotationPropertyRange := 'PropertyRange' '(' axiomAnnotations AnnotationProperty URI ')' 18:49:17 +1 18:49:34 +1 18:49:36 +1 18:49:39 +1 18:49:40 0 18:49:41 +1 18:49:42 0 18:49:42 0 18:49:42 0 18:49:47 +1 18:49:51 +1 18:50:05 RESOLVED: simplify structure of annotations as per http://lists.w3.org/Archives/Public/public-owl-wg/2008Nov/0115.html 18:50:22 ianh: we will talk to alan offline. to better understand his point 18:50:31 (Alan, if you're not happy with this resolution, we can consider some ammendment.) 18:50:49 ok 18:50:57 subsubtopic: Deprecation 18:51:17 q? 18:51:19 ianh: after investigation, the deprecation problem seems to have gone away 18:51:32 i agree 18:51:33 ... does anyone have something to say? 18:51:41 ... no, ok. we move on. 18:51:42 q? 18:51:50 q+ 18:51:51 yes, I am happy enough with current situation now. 18:51:53 q? 18:51:54 subsubtopic: rdf:XMLLiteral 18:51:58 ack bmotik 18:52:11 bmotik: it is not necessarily difficult conceptually 18:52:32 there is a possible connection with POWDER which refers to XML Literal 18:52:37 ... it contains a design flaw - lexical space requires normalization 18:52:41 yeah, wtf were the RDF Core folks thinking? :-( 18:52:44 q+ 18:52:56 http://www.w3.org/TR/2008/WD-powder-formal-20081114/#regexSemantics 18:53:06 ... it would be more useful if canonical form were for value space 18:53:22 q? 18:53:32 ack msmith 18:54:23 q+ 18:54:31 q? 18:54:50 q+ 18:54:59 q+ 18:55:02 q+ 18:55:03 q? 18:55:17 msmith: I believe OWL 2 should support it. It is useful and can be supported. I think the canonicalization issue is for easy comparison 18:55:29 ianh: what's the current state? it was in OWL 1 but isn't in OWL 2? 18:56:08 bmotik: OWL 1 was contradictory. one spec (RDF?) said it is included. another spec (semantics) said only string & integer 18:56:25 ... we should probably make an estimation if this would make people object. 18:56:32 q? 18:56:38 ack bmotik 18:56:44 ... if there's a non-zero probability of this, then what's one more datatype 18:57:02 q? 18:57:09 ack baojie 18:57:29 * owl:DataRange (alternative rdfs:Datatype) 18:57:29 * owl:distinctMembers (alternative owl:members) 18:57:35 baojie: I believe we have suggested replacing rdfs:Datatype with owl:DataRange 18:57:49 ... this is a different issue 18:58:05 ianh: no, we're now on rdf:XMLLiteral 18:58:08 q? 18:58:17 ... but I didn't understand the point on deprecation 18:58:30 baojie: do we have a list of terms that will be deprecated? 18:58:34 q? 18:58:41 we only deprecate owl:DataRange at the moment 18:58:49 q? 18:58:56 ianh: it was suggested we do a backwards compatibility audit. is that what you mean? 18:58:59 baojie: yes. 18:59:36 pfps: on OWL 1 built-in datatypes. It means if you implement it, you should implement in accordance with the spec 18:59:45 ... it doesn't require implementation 18:59:55 +q 18:59:58 ianh: so, for conformance it wasn't obligatory to support it 19:00:04 ack pfps 19:00:05 pfps: yes. 19:00:13 q? 19:00:15 zakim, unmute me 19:00:15 schneid should no longer be muted 19:00:22 ack schneid 19:00:33 http://www.w3.org/TR/2004/REC-owl-semantics-20040210/syntax.html#owl_built_in_datatypes 19:01:00 schneid: re OWL 1 S&AS, I agree with pfps comments 19:01:31 ... but its unclear if it is MUST or not. 19:01:46 q? 19:01:58 ... but I think it wasn't really in OWL 1, and isn't required in OWL 2 19:02:15 q? 19:02:18 ianh: I think it wasn't required in OWL 1, and isn't required in OWL 2 19:02:30 bmotik: I think this depends on last call 19:02:31 q+ 19:02:35 my email regarding rdf:XMLLiteral: http://lists.w3.org/Archives/Public/public-owl-wg/2008Nov/0112.html 19:02:49 q? 19:02:54 ack bmotik 19:03:13 ... this is an easier datatype to implement. to msmith, why does lexical state assume document is normalized? 19:03:57 one can even create RDFS-inconsistent documents with non-canonicalized literals :) 19:04:00 ianh: I suggest tabling the discussion of sensibility of datatype 19:04:13 zakim, mute me 19:04:13 schneid should now be muted 19:04:15 +1 19:04:23 q? 19:05:15 msmith: can we say if implemented, it should be implemented in accordance with... 19:05:24 +1 to putting this in conformance 19:05:30 ianh: it could be said in the conformance document. 19:05:32 q+ 19:05:38 +1 19:05:39 q? 19:05:44 ack msmith 19:05:48 ack bmotik 19:06:07 bmotik: why don't we add to Syntax 19:06:23 q? 19:06:28 ianh: that would make it mandatory, not optional 19:06:35 bmotik: are there many that use it 19:06:47 i have seen a couple 19:06:50 really? I have never seen it anywhere 19:06:54 I think there are people who use it. IIRC I've seen it in BioPAX files 19:06:58 am looking 19:07:11 q+ 19:07:17 bmotik: I proposed adding 4.7 to syntax, adding rdf:XMLLiteral 19:07:36 ianh: I'd like to make it at risk, because we have little implementation experience 19:07:41 +1 to at risk 19:07:42 q? 19:07:44 zakim, unmute me 19:07:44 schneid should no longer be muted 19:07:49 ack schneid 19:08:05 zakim, mute me 19:08:05 schneid should now be muted 19:08:09 zakim, unmute me 19:08:09 schneid should no longer be muted 19:09:00 schneid: I don't like rdf:XMLLiteral because it is covered in the RDF semantics by several conditions. we would need to avoid conflicting with other specifications 19:09:09 q? 19:09:37 christine has joined #owl 19:09:47 ianh: wasn't this exactly the same problem in OWL 1 19:09:57 q? 19:10:24 schneid: I believe it was only a suggestion in OWL 1, not mandatory 19:10:38 q+ 19:10:45 q? 19:10:46 ianh: but a semantics was specified. if supported, it had a specific semantics. 19:10:48 ack bmotik 19:10:50 +??P0 19:11:02 zakim, mute me 19:11:02 schneid should now be muted 19:11:24 bmotik: rdf mt, section 3.1 suggests this is not a standard datatype. I'm not sure I understand how this impacts things. 19:11:26 +1 to boris 19:11:33 zakim, +??P0 is christine 19:11:33 sorry, christine, I do not recognize a party named '+??P0' 19:11:46 q? 19:11:47 ... and it may change RDF interpretations 19:12:01 zakim, ??P0 is christine 19:12:01 +christine; got it 19:12:11 q+ 19:12:16 q? 19:12:17 bmotik: maybe we shouldn't say anything 19:12:19 ack pfps 19:12:29 Zakim, mute me 19:12:29 bmotik should now be muted 19:12:42 pfps: bad news. at end of WebOnt, XMLLiteral was made mandatory 19:12:51 ... see S&AS C5 19:13:15 we're back at RDF Semantics :) 19:13:25 http://www.w3.org/TR/owl-semantics/#changes-since-PR 19:14:01 sandro: maybe way to procede is to do it at risk and solicit more feedback 19:14:07 ...I will check what kind of "literal" I remember seeing 19:14:56 ianh: I'd like it to be at risk, with default being take it out 19:15:05 sandro: I think we can do that 19:15:19 peter, an RDF compatible datatype map has rdf:XMLLiteral in, anyway, with or without being explicit :) 19:16:03 PROPOSED: XML-Literal datatype is added to OWL 2 datatype map but marked at risk of being removed if there turn out to be implementation or semantic problems. 19:16:09 +1 19:16:12 +1 19:16:17 +1 19:16:18 +1 19:16:20 +1 19:16:21 +1 19:16:22 +1 19:16:22 +1 19:16:24 +1 19:16:24 +1 19:16:26 +1 19:16:27 -0.5 19:16:33 BioPAX doesn't use XML Literal - it uses a string that is documented to be in XML format 19:16:40 0 19:17:06 no, not an objection 19:17:11 q? 19:17:38 like most it was probably arbitrary 19:17:46 RESOLVED: XML-Literal datatype is added to OWL 2 datatype map but marked at risk of being removed if there turn out to be implementation or semantic problems. 19:18:00 yeah, alan, that's the patterns I see in most RDF. 19:18:13 ok 19:18:13 ACTION: bmotik2 to Update the spec to include rdf:XMLLiteral and fix the annotations as proposed 19:18:13 Created ACTION-251 - Update the spec to include rdf:XMLLiteral and fix the annotations as proposed [on Boris Motik - due 2008-11-26]. 19:18:37 q? 19:18:55 q? 19:19:00 q+ 19:19:01 subtopic: alignment of syntaxes 19:19:06 q? 19:19:09 q+ 19:19:16 ZAkim, unmtue me 19:19:16 I don't understand 'unmtue me', bmotik 19:19:17 ianh: it seems that few of the proposed changes had universal agreement 19:19:19 ack bmotik 19:19:20 Zakim, unmute me 19:19:20 bmotik was not muted, bmotik 19:20:04 ack pfps 19:20:15 bmotik: reiterating... I think we are serving two communities with different expectations. conforming one syntax to another is not nice. I think we can unify ExistsSelf and leave it at that 19:20:24 q+ 19:20:25 pfps: I agree with bmotik 19:20:33 Alan? 19:20:40 ianh: alan and ivan aren't present, this is tricky to discuss 19:20:42 I think the sentiment was that it was too hard to agree 19:20:59 whose sentiment? 19:21:01 However I don't agree with the idea that we serve 2 communities therefore things should be different 19:21:08 q+ 19:21:08 OK, so Boris's proposal is only to change ExistsSelf 19:21:08 Ivan, Myself - principal instigators 19:21:18 Does't matter 19:21:19 Would you be OK with this 19:21:29 Alan, I think it's rather we serve 2 communities therefore things may not be unifiable 19:21:38 I will say -1 without objection 19:21:42 (formal) 19:21:45 many of the proposed changes change things from the OWL 1 abstract syntax, which seems to be rather less than optimal 19:21:50 I think our job is to bring together communities 19:22:00 (Let's not get into the philosophy of who we serve.) 19:22:02 Names appeal to small segment 19:22:13 And seem to Boris taste rather to any standard 19:22:16 sure - but we don't want to loose them through this bringing together business 19:22:39 DL standard is logical notation 19:22:47 Add a syntax for that if desired 19:22:56 ? 19:23:02 for what? 19:23:04 q+ 19:23:06 But i (personally) see no reason to differ as we do now 19:23:07 You mean you want *another* syntax? 19:23:22 -q 19:23:26 I don't care. I'm objecting to the argument that the functional syntax is standard to some community 19:23:30 q- 19:23:33 ack alanr 19:23:35 zakim, unmute me 19:23:35 schneid should no longer be muted 19:23:39 ack schneid 19:23:48 q+ 19:23:58 q+ 19:24:00 schneid: if we change existself I favor changing the RDF side 19:24:29 ... so that it is consistent with other Restrictions in rdf 19:24:35 q? 19:24:45 I think SOTD should solicit input and list the disagreement as one we couldn't agree on 19:25:04 ack bmotik 19:25:08 ... something like deprecation [ a owl:Restriction ; owl:onProperty :p ; owl:existSelf "true"^^xsd:boolean ] 19:25:14 q? 19:25:23 bmotik: I wanted to propose something like :hasSelf 19:25:29 zakim, mute me 19:25:29 schneid should now be muted 19:25:47 q? 19:25:56 q? 19:25:56 ack /me 19:25:59 ack uli 19:26:53 q? 19:27:02 uli: disagree with Alan regarding the functional syntax. It is a different syntax because it doesn't have the restrictions of RDF 19:27:08 q? 19:27:21 zakim, unmute me 19:27:21 schneid should no longer be muted 19:27:39 zakim, mute me 19:27:39 uli should now be muted 19:27:54 schneid: hasSelf, existSelf, doesn't matter much. I have more concern about similarity to other restrictions 19:28:09 q? 19:28:16 zakim, mute me 19:28:16 schneid should now be muted 19:28:16 ianh: other opinions on RDF form of existself? 19:28:37 HasSelf is more symmetric 19:28:45 with the rest of the FS 19:28:53 ... I have preference to keeping one of the ones we have rather than pick a new one 19:29:19 will this be the only choice? 19:29:30 zakim, unmute me 19:29:30 uli should no longer be muted 19:29:31 ianh: I understand proposal to be to change both FS and RDFSyntax to be HasSelf. then change nothing else 19:29:58 zakim, mute me 19:29:58 uli should now be muted 19:30:00 uli: in the sense that one could use either current RDF or FS for self restriction 19:30:25 PROPOSED: Use HasSelf for self-restriction in both RDF and functions; don't change anything else. 19:30:32 +1 19:30:37 +1 19:30:38 +1 19:30:40 +1 19:30:43 0 19:30:44 +1 19:30:46 +1 19:30:46 0 19:30:46 -1 (but not formally objecting) 19:30:53 0 19:31:11 0 19:31:16 RESOLVED: Use HasSelf for self-restriction in both RDF and functions; don't change anything else. 19:31:17 ianh: last chance to speak on this... 19:32:00 -Evan_Wallace 19:32:01 -baojie 19:32:02 -Achille 19:32:04 ianh: End of Agenda. We're out of time. No additional business. Thanks. Next week we'll be frozen and ready to roll out docs. 19:32:04 -bmotik 19:32:05 -MarkusK_ 19:32:06 -Peter_Patel-Schneider 19:32:06 -bcuencagrau 19:32:07 -Sandro 19:32:08 -Zhe 19:32:10 -msmith 19:32:13 -IanH 19:32:14 -christine 19:32:16 -schneid 19:32:20 bye 19:32:22 uli has left #owl 19:32:36 -uli 19:32:37 SW_OWL()1:00PM has ended 19:32:38 Attendees were msmith, IanH, Evan_Wallace, uli, Peter_Patel-Schneider, bcuencagrau, Sandro, bmotik, Zhe, baojie, MarkusK_, Achille, schneid, christine