13:07:37 RRSAgent has joined #rif 13:07:37 logging to http://www.w3.org/2008/09/26-rif-irc 13:09:19 StellaMitchell has joined #rif 13:09:34 LeoraMorgenstern has joined #rif 13:10:42 csma has joined #rif 13:10:59 DaveReynolds has joined #rif 13:11:43 sandro has joined #rif 13:15:35 Blaz has joined #rif 13:16:03 AxelPolleres has joined #rif 13:16:19 AdrianP has joined #rif 13:16:31 scribe: AxelPolleres 13:16:36 scribenick: AxelPolleres 13:17:11 chris showing the meeting objectives, cf. http://www.w3.org/2005/rules/wiki/F2F11 13:17:45 chris: we must progress on the test cases before going to CR. 13:17:51 RRSAgent, pointer? 13:17:51 See http://www.w3.org/2008/09/26-rif-irc#T13-17-51 13:17:53 ... main issue. 13:18:08 RRSAgent, make record public 13:18:21 ... agenda, cf. http://www.w3.org/2005/rules/wiki/F2F11 13:22:38 sandro: how shall we change morning agenda, since we lost already 1/2 hr. 13:22:49 adrian: we can cut tc to 1/2 hr 13:24:12 RIF test cases 13:24:14 http://www.w3.org/2005/rules/wiki/Category:Test_Case 13:24:18 topic: Test Cases 13:25:22 csma: let's go through them one by one. 13:25:33 subtopic: http://www.w3.org/2005/rules/wiki/Annotation_Entailment 13:25:52 1) http://www.w3.org/2005/rules/wiki/Annotation_Entailment - by jos. 13:26:09 ... found an error. 13:26:23 chris: let's fix simple errors on the fly. 13:27:41 jos: testing whether there is an annotation in the ontology imported. 13:28:07 sandro: how do you know that it is an annotation property. 13:28:32 jos: for all objects of type owl:Ontology, all properties must be annotation properties... 13:28:36 ... will check again. 13:29:17 dave: not sure, whether dc:title should be declared an annotation property. 13:29:42 add dc:title rdf:type owl:AnnotationProperty 13:31:06 axel: I think hijacking dc:title that way is VERY weird. 13:32:24 sandro: right, you can't use dc:title then in an ontology you merge. 13:32:36 axel: you can just create a subproperty of dc:title. 13:32:44 christian: next test case. 13:32:52 subtopic: AnnotationPropertyID rdf:type owl:AnnotationProperty 13:33:02 subtopic: http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment 13:33:08 http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment 13:33:20 jos: that is the simplest form of inconsistency in RIF. 13:33:45 adrian: should we define a separate test category for testing inconsistency? 13:33:52 mdean has joined #rif 13:34:12 agreement on that trst case. 13:34:23 chris: a birt more description would be in order. 13:34:53 resolve this status to "approved"? 13:35:03 rrsagent, pointer 13:35:03 See http://www.w3.org/2008/09/26-rif-irc#T13-35-03 13:35:07 s/resolve/...resolve/ 13:35:20 PROPOSED: Accept http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment 13:35:22 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment 13:35:36 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment with more detailed description 13:35:40 Harold has joined #rif 13:35:46 ACTION: jos add more description to http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment 13:35:46 Sorry, amibiguous username (more than one match) - jos 13:35:46 Try using a different identifier, such as family name or username (eg. jdebruij2, jderoo) 13:35:50 josb has joined #rif 13:35:56 GaryHallmark has joined #rif 13:36:00 ACTION: jdebruij2 add more description to http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment 13:36:02 Created ACTION-580 - Add more description to http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment [on Jos de Bruijn - due 2008-10-03]. 13:36:34 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Arbitrary_Entailment with more detailed description 13:36:39 RRSAgent, pointer 13:36:39 See http://www.w3.org/2008/09/26-rif-irc#T13-36-39 13:36:59 http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-add_1 13:37:04 by Axel 13:40:44 Jos: BLD 2.3 says your can't do this -- no externals in head 13:41:00 Jos: oh... no, that's just atoms 13:42:48 PROPOSED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-add_1 13:43:04 RESOLVED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-add_1 13:43:09 RRSAgent, pointer? 13:43:09 See http://www.w3.org/2008/09/26-rif-irc#T13-43-09 13:46:14 PROPOSED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-add_2 13:46:31 RESOLVED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-add_2 13:46:42 RRSAgent, pointer? 13:46:42 See http://www.w3.org/2008/09/26-rif-irc#T13-46-42 13:50:26 sandro: the description of subtract-variants should reference the addition variants, highlighting the duality between them. 13:53:21 axel: I should add a variation testing for a(11) without the "termination condition" X > 0. 13:53:58 PROPOSED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-subtract_1 13:54:28 ACTION: Axel improve the description of chaining strategies 13:54:28 Created ACTION-581 - Improve the description of chaining strategies [on Axel Polleres - due 2008-10-03]. 13:54:35 PROPOSED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-subtract_1 and 2 13:54:46 RESOLVED: Approve http://www.w3.org/2005/rules/wiki/Chaining_strategy_numeric-subtract_1 and 2 13:55:09 http://www.w3.org/2005/rules/wiki/Class_Membership 13:55:11 by adrian. 13:55:32 jos: this is not correct. 13:55:55 ... membership can't be used as terms. 13:56:28 christian: adrian, please adapt, then we can revisit that test case. 13:56:41 http://www.w3.org/2005/rules/wiki/Classification_non-inheritance 13:56:45 by stella. 13:58:48 dave: This testcase shows that RIF doesn't have something like class properties. 13:59:06 Chris: Instances do not inherit the properties of their classes [ Classification non-inheritance] 13:59:28 Chris: You use formulas, not facts, to give properties of all instances of a class. 14:00:04 Chris: It looks kind of like a default, but BLD doesn't have anything like that. 14:02:02 Dave: if you approach this from an OOP viewpoint, you could expect the conclusion. 14:02:11 Dave: Someone coming at frames from Java might try to do this kind of (disallowed) inheritance 14:02:17 ... that is what that TC shows. 14:02:34 Axel: we could add a rule in a variation that does entail the conclusion. 14:02:46 PROPOSED: Accept http://www.w3.org/2005/rules/wiki/Classification_non-inheritance 14:05:28 csma: instead of using favoritePerson, let's use cardinality->6 billion 14:05:40 christian: the description should be extended to discuss properties of classes and instances. 14:06:14 q? 14:06:37 Leora: Would it be helpful to have a variant as suggested by axel? 14:08:07 ACTION: axel add test case related to http://www.w3.org/2005/rules/wiki/Classification_non-inheritance that makes all class properties apply to instances 14:08:08 Created ACTION-582 - Add test case related to http://www.w3.org/2005/rules/wiki/Classification_non-inheritance that makes all class properties apply to instances [on Axel Polleres - due 2008-10-03]. 14:08:51 ?X[?P -> ?V] :- And ( ?X#?Y ?Y[?P -> ?V] ) 14:12:12 josb has joined #rif 14:12:13 DaveReynolds_ has joined #rif 14:12:18 GaryHallmark has joined #rif 14:12:18 hi back! 14:12:21 :-) 14:12:30 <_mdean> _mdean has joined #rif 14:12:53 Blaz has joined #rif 14:13:43 sandro has joined #rif 14:14:13 variation of http://www.w3.org/2005/rules/wiki/Classification_non-inheritance accepted. 14:14:17 RESOLVED: Accept http://www.w3.org/2005/rules/wiki/Classification_non-inheritance 14:14:21 RRSAgent, pointer? 14:14:21 See http://www.w3.org/2008/09/26-rif-irc#T14-14-21 14:15:03 http://www.w3.org/2005/rules/wiki/Disjunctive_Information 14:15:12 by jos. 14:15:28 jos: that's a nasty one, it needs a constraint solver. 14:17:25 has equality in the head, which is at risk. 14:18:23 Sandro: description should include evil grin of jos :-) 14:19:07 jos: without negative guards we can't have disjunction here. 14:19:14 sandro has joined #rif 14:19:36 chris: as long as we have equality in the head, it makes sense to have that. 14:19:52 sandro: a little bit more description is in order. 14:20:07 RESOLVED: Accept http://www.w3.org/2005/rules/wiki/Disjunctive_Information 14:20:15 Harold has joined #rif 14:20:38 http://www.w3.org/2005/rules/wiki/EntailEverything_1 14:20:39 action: jos To explain better how/why http://www.w3.org/2005/rules/wiki/Disjunctive_Information is so tricky 14:20:39 Sorry, amibiguous username (more than one match) - jos 14:20:39 Try using a different identifier, such as family name or username (eg. jdebruij2, jderoo) 14:20:46 by gary 14:20:51 action: jdebruij2 To explain better how/why http://www.w3.org/2005/rules/wiki/Disjunctive_Information is so tricky 14:20:51 Created ACTION-583 - Explain better how/why http://www.w3.org/2005/rules/wiki/Disjunctive_Information is so tricky [on Jos de Bruijn - due 2008-10-03]. 14:21:03 gary: this is waht PR systems typically can't do. 14:21:52 Gary: http://www.w3.org/2005/rules/wiki/EntailEverything_1 - http://www.w3.org/2005/rules/wiki/EntailEverything_6 are basically all the same. 14:21:52 RRSAgent, pointer? 14:21:52 See http://www.w3.org/2008/09/26-rif-irc#T14-21-52-1 14:24:08 Action: josb remind people that "josb" works for assigning actions to him. 14:24:08 Created ACTION-584 - Remind people that \"josb\" works for assigning actions to him. [on Jos de Bruijn - due 2008-10-03]. 14:24:22 Axel: http://www.w3.org/2005/rules/wiki/EntailEverything_1 doesn't need the p(1 2) fact. 14:24:40 ACTION-584 done 14:24:43 ... similarly for http://www.w3.org/2005/rules/wiki/EntailEverything_2 14:25:30 ACTION-584 closed 14:25:30 ACTION-584 Remind people that "josb" works for assigning actions to him. closed 14:26:15 christian/jos/gary desicuss that we could unify all those into one test case. 14:26:30 ... with a conjunction in the conclusion. 14:28:08 christian: can we make the decision right now? 14:28:38 http://www.w3.org/2005/rules/wiki/Equality_in_conclusion_1 14:28:40 by adrian 14:29:03 adrian: that's an implementation of factorial function 14:29:40 harold: And( .... ) is missing in the body, forall missing, infix-arithmetics not allowed. 14:31:20 subtopic: http://www.w3.org/2005/rules/wiki/Equality 14:32:00 csma: we don't have an unambiguous translation to XML, so we can't consider this yet. 14:33:13 Topic: UCR 14:33:23 christian: which plans and changes? 14:33:59 adrian: many of the use cases need more expressive dialects than the ones we have at the moment. 14:34:31 ... for example 4.3 14:35:31 Harold has joined #rif 14:35:47 ... first rule uses negation, which is not in BLD. 14:36:53 ... there is many different negations, recall: http://www.w3.org/2005/rules/wg/wiki/negation?highlight=(Negation) 14:37:43 christian: not include WRONG language in the document. 14:37:59 I plan to rewrite the relational factorial example (http://www.w3.org/2005/rules/wiki/Equality) to a PS version and complement it with a functional version. 14:38:00 ... remove "non-encodable" code examples 14:39:49 Leora: 4.5 14:40:09 ... modalities not easily expressible. 14:40:20 ... also would need negation. 14:42:04 Adrian: let's discuss 4.6 14:42:07 Bob has joined #rif 14:42:16 Josb: first a question about abridged syntax. 14:43:22 in the examples... what is the type of "holdsAt" "ineffective"? is it a URI, a local constant? 14:43:48 s/in the examples/... in the examples/ 14:44:07 ... that is not abridged syntax, needs to be fixed! 14:44:33 Adrian: needs understanding of event calculus. 14:44:58 Chris: Is the intention of this rule expressible in BLD? I think yes. 14:50:21 BobMoore has joined #rif 14:50:36 Leora: shall we rediscuss encodings of action languages, sit.calc., event calc. in BLD? (was discussed some time ago in RIFRAF) 14:52:09 chris: abridged syntax.... we had agreement that we discuss only on syntaxes which people are willing to implement. 14:52:54 ... for the use cases, it should be the same rationale. abridged syntax only allowed where we have a translator. 14:54:36 jos: 4.6 and other examples need to be reparied to have unambiguous syntax. 14:55:01 <_mdean> _mdean has joined #rif 14:55:06 action: adrian to update examples in UCR to presentation syntax 14:55:06 Sorry, amibiguous username (more than one match) - adrian 14:55:06 Try using a different identifier, such as family name or username (eg. agiurca, apaschke) 14:55:23 action: apaschke to update examples in UCR to presentation syntax 14:55:23 Created ACTION-585 - Update examples in UCR to presentation syntax [on Adrian Paschke - due 2008-10-03]. 14:56:35 christian: What do we do about the syntax? 14:56:42 action: apaschke to add a comment in UC 4.6 explaining that the example can be translated to BLD using some kind of encoding 14:56:42 Created ACTION-586 - Add a comment in UC 4.6 explaining that the example can be translated to BLD using some kind of encoding [on Adrian Paschke - due 2008-10-03]. 14:57:34 action: apaschke to remove examples in 4.3 that we have no dialect for, and add comment to make that clear 14:57:34 Created ACTION-587 - Remove examples in 4.3 that we have no dialect for, and add comment to make that clear [on Adrian Paschke - due 2008-10-03]. 14:58:30 AdrianP has joined #rif 14:58:32 I update the class membership test case 14:58:41 action: leora to remove examples in 4.5 that we have no dialect for, and add comment to make that clear 14:58:41 Created ACTION-588 - Remove examples in 4.5 that we have no dialect for, and add comment to make that clear [on Leora Morgenstern - due 2008-10-03]. 15:00:32 dave: volunteer to correct 4.8 BLD transcription 15:00:36 action: dave to rewrite BLD examples from UC 4.8 15:00:36 Created ACTION-589 - Rewrite BLD examples from UC 4.8 [on Dave Reynolds - due 2008-10-03]. 15:02:41 Gary: internaitonalization hasn't yet been discussed. 15:03:22 axel: does that just mean we should have a UC/TC which uses rdf:text? 15:03:39 Sandro: something that shows off the use of language tags. 15:03:53 action: apaschke to add a requirement that is satisfied by rdf:text 15:03:53 Created ACTION-590 - Add a requirement that is satisfied by rdf:text [on Adrian Paschke - due 2008-10-03]. 15:04:03 COFFEEBREAK! 15:05:09 bmoore3 has joined #rif 15:30:09 <_mdean> scribe: Mike Dean 15:30:22 <_mdean> scribenick _mdean 15:30:58 <_mdean> nick mdean 15:31:12 scribenick: mdean 15:31:36 reviewing actions 15:31:43 NOT CP = NOT CRITICAL PATH 15:31:53 csma has joined #rif 15:31:58 ISSUE-26: roundtripping 15:31:58 ISSUE-26 Replication of original rules after roundtripping to RIF [NOT CP] notes added 15:33:14 Harold: BLD#Conformance_Clauses addresses roundtripping 15:33:54 ChrisW: issue addresses non-semantic things - semantics are required 15:34:26 ChrisW: metadata SHOULD be preserved 15:35:20 ChrisW: ready to close issue? 15:35:39 josb: not sure what it means for metadata to survive roundtripping 15:36:04 josb: e.g. ordering of conjunction clauses 15:36:14 csma: talking about explicit metadata defined in spec 15:36:30 josb: should be made explicit 15:37:26 josb: talking about conjunctions within metadata 15:37:39 csma: metadata about metadata 15:38:04 ChrisW: who would really care? 15:39:45 DaveReynolds_ has joined #rif 15:39:47 GaryHallmark_ has joined #rif 15:40:11 josb_ has joined #rif 15:41:12 sandro has joined #rif 15:46:20 josb_ has joined #rif 15:46:31 GaryHallmark_ has joined #rif 15:46:49 Blaz has joined #rif 15:46:51 DaveReynolds_ has joined #rif 15:47:00 <_mdean> _mdean has joined #rif 15:47:24 csma: WG should not specify such a mechanism 15:47:45 ... should forbid subsets of Core 15:47:58 ... otherwise notion of Core disappears 15:48:24 ChrisW: profiles different than dialects 15:48:39 Sandro: only WG can say what RIF is 15:48:58 ChrisW: profile provides way to describe what subset of a dialect you support 15:49:06 ... issue predates BLD 15:49:21 ... what was Core is now BLD 15:49:49 csma: no mechanism for profiles and don't allow subsets of Core 15:50:06 Sandro: constraints on us vs others 15:50:14 sandro has joined #rif 15:50:48 Gary: forward- vs. backward-chaining example 15:50:56 ... how high is bar for translator implementers 15:51:38 csma: will happen - where WG should legislate is different issue 15:51:58 Harold: cannot predict which other subsets of Core will be relevant (e.g. OWL RL) 15:52:29 DaveReynolds: Core document doesn't currently require all dialects to implement 15:53:02 ... suggest no to profiles - informal seems good enough - add later if demand warrants 15:53:21 csma has joined #rif 15:53:25 ChrisW: no objections to this as proposed resolution 15:53:39 PROPOSED: Close issue-29 saying we will not define a notion of Profiles 15:53:43 AxelPolleres has joined #rif 15:53:47 Harold has joined #rif 15:53:59 PROPOSED: Close issue-29 saying we will not define a notion of Profiles (ie subsets of defined dialects, which are not themselves dialects) 15:54:24 csma: wait until tomorrow for resolutions 15:54:43 ... like waiting until the next telecon 15:55:13 We MAY introduce Best Practices for RIF. Example: Attach annotations only to syntactic parts of rulesets that stay unchanged under semantics-preserving ruleset transformation. Rationale: You don't want to lose "annotation attachment points" under such transformations (cf. Gary's/Jos' tautology example). 15:55:20 PROPOSED: We will not constraint ourselves about whether or not there will ever be a RIF dialect which is a subset of Core 15:55:25 ChrisW: should we constrain the WG? 15:55:46 ChrisW: proposing inverse of that 15:55:53 s/constraint/constrain/ 15:56:17 Harold: should not constraint ourselves 15:56:26 most people feel we should not 15:56:30 No objections, but CSMA wants to think about it more. 15:57:03 ChrisW: these 2 resolutions will close issue 29 15:57:05 Chris: passing those two resolutions tomorrow will close issue-29 15:57:15 Issue 33: specification of data sources in RIF 15:57:27 csma: special session later, also on 37 and 38 15:57:51 Issue 39 and 46 15:58:03 ChrisW: 46 subsumes 39 15:58:25 ChrisW: Michael had more general thing in mind 15:58:43 ChrisW: can we close 39 because we have it in BLD and then move on to more general 15:59:06 csma: discussed w.r.t. Core? May be a problem for PRD 15:59:40 ... semantics of rule set is in conflict resolution strategy - different CRS could be a problem 16:00:12 josb: PRD could preclude loading ruleset with different strategy 16:00:35 josb: maybe change issue 16:00:49 csma: if issue for PRD, then also an issue for Core 16:01:18 ChrisW: keep open for Core and PRD 16:01:32 Issue 46: modules 16:01:38 csma: related to issue 33 16:02:24 Michael: should be in FLD - can't substantiallly change BLD now 16:03:06 josb: add to FLD and write specialization text for BLD 16:03:23 Michael: should leave this open 16:03:49 ChrisW added note that modules apply to FLD 16:04:49 Issue 50: Semantic metadata 16:04:57 GaryHallmark_ has joined #rif 16:05:31 ChrisW: opened for metadata that impacts semantics, e.g. import or PR priority, resolution strategy, negation semantics 16:05:52 Michael: problem for FLD not BLD 16:06:18 ChrisW: closed for BLD 16:06:36 Harold: Peter pointed us to that issue 16:07:03 Michael: metadata is annotations, not import 16:07:37 ... FLD has no provision for metadata affecting semantics 16:08:03 DaveReynolds: in logic language, would make it part of language not metadata 16:08:27 so the question is what is metadata.... annotations.... 16:08:32 Michael: e.g. overrides predicate on identifiers 16:08:53 Michael: depends on where you put stuff 16:09:25 ChrisW: need to decide for FLD, already decided for BLD, what about PRD and Core? 16:09:34 csma: still open 16:09:49 Sandro: would prefer that metadata not be semantic, by definition 16:10:13 csma: point of preserving during round-tripping 16:10:41 ChrisW: how long would this discussion take? 16:12:02 ChrisW: any objections to precluding semantic metadata? 16:12:18 michael: I don't feel comfortable closing this right now, for FLD. 16:12:18 Harold: divide annotations into pragmas and ... 16:13:25 moved to Technical Design product (no conjunctive drop down lists) 16:14:00 Issue 57: Extensibility 16:14:10 ChrisW: XTAN has no official status 16:14:33 csma; relationship to 69 16:14:57 ChrisW: have to close or postpone all issues by Last Call 16:15:15 not in BLD for Last Call 16:15:55 Sandro: can we meet requirements without it? 16:16:04 s/meet/meet our 16:16:13 Sandro: I don't think we can meet our requirements with out. 16:16:33 csma: on tomorrow's agenda? 16:17:14 csma: proposed resolution for profiles 16:19:51 ChrisW: just roundtripping 16:20:26 ... return to issues in last session today 16:24:11 Issues 37 and 38 16:24:28 Christian: references to external classes such as Hen 16:24:34 josb: Jim the Hen Handler 16:25:18 DaveReynolds: schema vs. object model (37 vs. 38) - raised but not written down 16:25:40 s/but/but formal spec/ 16:25:51 ... reuse JAXB mapping 16:26:52 Sandro: write a spec that JAXB happens to implement 16:27:04 Gary: map complex classes to frames 16:27:19 ... JAXB is long and complicated - start with something simpler like Java Bean 16:27:40 ... handle 1-to-1 vs. set cardinality constraints 16:28:15 ... unique properties would probably need equality in the head 16:28:33 ... perhaps end up with mini ontology language 16:29:01 DaveReynolds: XML Schema provides cardinalities 16:29:23 ... need to know URIs to reference complex classes 16:30:44 s/need/just need/ 16:32:04 DaveReynolds: spec'd algorithm vs. annotation mechanism 16:32:23 csma: such schemas already exist 16:32:45 DaveReynolds: focus on algorithm 16:32:55 bmoore3 has joined #rif 16:33:03 Gary: JAXB handles most schemas, but it's a huge spec 16:33:43 csma: useful to any dialects? 16:33:50 Gary: seems orthogonal 16:34:02 csma: who could write strawman document? 16:34:50 Sandro: how many people would use this? is it critical? 16:34:57 Gary: yes 16:35:03 csma: agreed 16:35:11 Adrian: what about black box model? 16:35:27 BobMoore has joined #rif 16:35:36 csma: requires sharing XML Schema + mappin 16:36:32 ChrisW: black box still requires dealing with uniqueness of slots in frame syntax and access to objects 16:37:03 Just to announce I am here - at least for a little while until I have to go down to supper 16:37:40 Is it possible to activate the phone bridge 16:38:02 csma: multiple models mapping on to same XML Schema 16:38:28 csma: navigating schema, attribute of sub-sub-element 16:38:40 AxelPolleres has joined #rif 16:39:05 csma: user-defined builtins for object model methods 16:39:24 ... how do you refer to methods 16:39:41 ... using frame syntax 16:39:48 ... e.g. for Java objects 16:40:28 Hey, BobMoore - one minute. 16:40:41 DaveReynolds: very PRD specific 16:41:01 BobMoore, it looks we're just about to break for lunch. 16:41:15 back in 80 minutes or so. 16:41:19 ChrisW: meet-odds 16:41:35 What timing!! 16:41:41 ChrisW: any other issues or barriers? 16:43:07 csma: use the schema to navigate the data 16:43:09 ACTION: Gary to draft a straw proposal addressing part of ISSUE-37, in the area of navigating the schema/data. 16:43:09 Created ACTION-591 - Draft a straw proposal addressing part of ISSUE-37, in the area of navigating the schema/data. [on Gary Hallmark - due 2008-10-03]. 16:44:41 Gary: not going to do arbitrary XML 16:45:55 csma: use XPath? 16:45:57 Gary: no 16:47:01 ACTION: csma to open issue based on the White Board line: "What about methods -- Ignore" 16:47:01 Created ACTION-592 - Open issue based on the White Board line: \"What about methods -- Ignore\" [on Christian de Sainte Marie - due 2008-10-03]. 16:47:14 break for lunch 16:47:31 cafeteria somewhere in this building 16:47:45 2 or 3 restaurants in Trump Building 16:47:56 appears to have stopped raining 16:48:12 Sony building also has food 16:48:45 reconvene at 2pm 17:32:08 There will be an interruption of Zakim-bot services shortly expected to last less than 15 mins 18:10:45 LeoraMorgenstern has joined #rif 18:17:15 BobMoore has joined #rif 18:28:50 BobMoore has joined #rif 18:31:45 ChrisW has joined #rif 18:33:10 csma has joined #rif 18:34:28 Bob, we restart in 5 minutes, with about 1 hour on Test cases, then reframing the semantics of conditions in PRD to align it with BLD. 18:35:53 Ping us if/when you want to join 18:36:00 okay trust you had a nice lunch - I am assuming the conference code is 74394 18:37:44 sandro has joined #rif 18:38:49 I'm ready to join 18:39:19 ok 18:40:05 Call Zakim (+1.617.761.6200 (US), +33 4 89 06 34 99 (F) or +44.117.370.6152 18:40:05 (GB) 18:40:38 Conference code is as usual: 74394# ('RIFWG') 18:40:55 We are setting up the communication on our side 18:41:28 zakim, what is the code? 18:41:28 the conference code is hidden, csma 18:41:43 zakim, this will be rif 18:41:43 I do not see a conference matching that name scheduled within the next hour, csma 18:41:49 StellaMitchell has joined #rif 18:42:14 Zakim, room for 4 for 300mn? 18:42:14 I don't understand your question, csma. 18:42:30 Zakim, room for 4 for 300 minutes? 18:42:31 ok, csma; conference Team_(rif)18:42Z scheduled with code 26631 (CONF1) for 300 minutes until 2342Z 18:43:13 Bob, the code is 26631, instead 18:43:22 josb_ has joined #rif 18:43:55 Team_(rif)18:42Z has now started 18:43:55 Scribe: stella Mitchell 18:44:02 + +0777841aaaa 18:44:06 scribenick: StellaMitchell 18:44:21 DaveReynolds_ has joined #rif 18:44:35 BobMoore, we're trying to figure out how to get the phone working. 18:44:37 DaveReynolds has joined #rif 18:44:49 Bob, are you +0777841aaaa? 18:44:59 Zakim, aaaa is me 18:44:59 +BobMoore; got it 18:45:30 yes I am - Zakim says I am the first participant and I need to wait for others to join 18:46:11 +??P1 18:46:20 zakim, ??P1 is Meeting_Room 18:46:20 +Meeting_Room; got it 18:46:39 Blaz has joined #rif 18:47:20 topic: Test Cases, including FPWD plan 18:47:37 csma: start with FPWD plan 18:47:51 AdriaP has joined #rif 18:48:12 csma: what do we need to publish? 18:48:27 mdean has joined #rif 18:48:46 csma: document does not currently include the test cases. Should it? 18:49:00 http://www.w3.org/2005/rules/wiki/Test 18:49:00 http://www.w3.org/2005/rules/wiki/Test 18:49:02 GaryHallmark has joined #rif 18:49:16 Sandro: there are 3 options: 18:49:35 ... 1. owl pulbished the tests, but not the format 18:50:04 ... 2.currently for RIF we have the format, and other information, but not the tests themselves 18:50:12 ...3 some groups do neither 18:50:22 AxelPolleres has joined #rif 18:50:25 ...I can't see reasons to go one way or the other 18:50:56 csma: do we need to publish anything? or can we just maintain the wiki page? 18:51:02 jos: need versions 18:51:17 Harold has joined #rif 18:51:54 who is on the phone? 18:51:58 sandro: can't run test cases from wiki, I am writing software to extract the cases from that 18:52:00 zakim, who is on the phone? 18:52:00 On the phone I see BobMoore, Meeting_Room 18:52:25 adrian: I think it's good to have a separate document also 18:52:41 csma: but does it need to be on rec track? 18:53:08 jos: I don't think it needs to be rec track 18:53:29 csma: needs to be accessible, but rec track is a different quesiton 18:53:41 leora: what do other groups do? 18:54:24 sandro: owl did, but they were different because they included the tests and conformance clauses 18:54:26 zakim, meeting_room contains AxelPolleres, SandroHawke, JosDeBruijn, MikeDean, StellaMitchell, LeoraMorgenstern, BlazNovak, MichealKifer, DaveReynolds, AdrianPaschke, HaroldBoley, GaryHallmark, ChrisWelty, ChristianDeSainteMarie 18:54:26 +AxelPolleres, SandroHawke, JosDeBruijn, MikeDean, StellaMitchell, LeoraMorgenstern, BlazNovak, MichealKifer, DaveReynolds, AdrianPaschke, HaroldBoley, GaryHallmark, ChrisWelty, 18:54:29 ... ChristianDeSainteMarie; got it 18:54:57 rrsagent, make minutes 18:54:57 I have made the request to generate http://www.w3.org/2008/09/26-rif-minutes.html ChrisW 18:55:07 rrsagent, make logs public 18:55:18 csma: if we do not publish the test cases, then this can be on the same web page 18:55:49 sandro: I don't think it needs to be rec track 18:56:28 sandro: people may notice it more if there is a document 18:56:58 csma: question of whether there is a document is separate from the question of whether it is rec track 18:57:38 sandro: I like that the tests are normative, so you know if someone fails a test case then they have a non-conforning implementation 18:57:52 jos: there could be errors in the test cases 18:58:41 harold: there could be errors in the test cases, but it would be good if they are normative - and we should try to make sure they are all correct 18:58:51 mdean has joined #rif 18:59:23 csma: if we make them normative, then that doesn't add much work to what we have to do anyway 18:59:50 csma: but other things, such as running the test cases, are a distraction that is not high priority 19:00:38 csma: how far are we from being able to publish a document if we put all the tests in an appendix? 19:00:47 adrian: I think it is almost ready 19:01:17 csma: how much of the document has been discussed and agreed upon? 19:02:17 harold: we need to bring it to a high quality anyway - so that they can be used 19:02:43 csma: how hard would it be to agree on properties? 19:02:52 sandro: it's not done yet 19:04:06 sandro: should extend rdf and owl 19:04:12 sandro: I think 19:04:28 sandro: if the definitions are the same as RDF/OWL used 19:06:37 chrisw: is everyone ok with doc being published as WD, and including actual test cases? 19:07:06 dave: nervous about including test cases in the document 19:08:28 sandro: the doc could end up being too large 19:08:55 http://www.w3.org/TR/owl-test/ 19:09:00 sandro: a recommendation can be multple web pages 19:10:51 adrian: show/hide buttons 19:11:25 sandro: is it ok to use RDF for the manifest file format? 19:11:56 In response to Sandro, if the document is too long to be printed, it should carry a label warning about this ("Please don't print this long document ..."). 19:12:07 sandro: question to Gary, is this ok for you? will you have tools to parse RDF? 19:14:04 Sandro wants tests to be maintained on the wiki 19:14:31 not in a repository like the current document specifies 19:15:41 Gary: I don't think it's a problem - re: manifest file format 19:16:06 sounds like it's okay to be RDF-centric in test-case management for now. 19:18:42 SPARQL test cases --- looks like a WD, but it's not.... http://www.w3.org/2001/sw/DataAccess/tests/r2 19:19:36 chris: prefer to have text of test cases in WD --- 8 19:19:48 chris: prefer not to have it in --- 3 19:20:14 chris: what other things do people expect to see in the WD that is not here 19:20:34 ...none were identified 19:20:58 chris: so, we need to work out properties and include text of test cases 19:21:24 Dave, we could have an "In doubt leave it out" policy for the set of approved WD test cases. 19:23:07 chris: test cases task force will meet monday 11:00 est 19:23:33 chris: have estimate by tues of how long it would take to get this ready to be reviewed as a WD 19:24:05 action: csma to put Test Cases working draft schedule on agenda for next telecon 19:24:05 Created ACTION-593 - Put Test Cases working draft schedule on agenda for next telecon [on Christian de Sainte Marie - due 2008-10-03]. 19:24:26 toplic: reviewing test cases 19:24:47 subtopic: http://www.w3.org/2005/rules/wiki/Equality_in_conclusion_1 19:25:46 csma: any problems with this 19:26:05 chris: could use more in the description 19:26:19 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Equality_in_conclusion_1 19:26:29 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Equality_in_conclusion_1 19:26:35 RRSAgent, pointer? 19:26:35 See http://www.w3.org/2008/09/26-rif-irc#T19-26-35 19:27:19 action: Stella to add more to the description of use case equality in conclusion1 19:27:19 Created ACTION-594 - Add more to the description of use case equality in conclusion1 [on Stella Mitchell - due 2008-10-03]. 19:27:39 csma: equality_in_conculsion2 19:27:45 csma: any objections? 19:28:58 Chris: It would be nice to have some real-world example for this. 19:29:20 chris: for description - say why you would write a rule like this 19:29:32 chris: test cases are examples too 19:29:33 Chris: put in a concrete example.... 19:30:04 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Equality_in_conclusion_2 19:30:12 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Equality_in_conclusion_2 19:30:16 action: Stella to add more to the description of use case equality in conclusion2 19:30:16 Created ACTION-595 - Add more to the description of use case equality in conclusion2 [on Stella Mitchell - due 2008-10-03]. 19:30:19 RRSAgent, pointer? 19:30:19 See http://www.w3.org/2008/09/26-rif-irc#T19-30-19 19:30:40 csma: equality_in_condition 19:31:58 csma: in this test case, the conclusion is exhaustive 19:32:02 jos: no, it's not 19:32:58 sandro: would be nice to see what isn't entailed, as well as what is entailed - n the same test case 19:34:19 various: in this case, the conclusion is not a proper document 19:34:39 dave: updated to be a document 19:35:07 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Equality_in_condition 19:35:13 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Equality_in_condition 19:35:20 RRSAgent, show pointer 19:35:20 I'm logging. I don't understand 'show pointer', sandro. Try /msg RRSAgent help 19:35:23 RRSAgent, show pointer? 19:35:23 I'm logging. Sorry, nothing found for 'show pointer' 19:35:28 RRSAgent, pointer? 19:35:28 See http://www.w3.org/2008/09/26-rif-irc#T19-35-28 19:35:54 what about testcases like modeling equalities from OWL - e.g. by inverseFunctionalProperties... - for head equality? do we want that? I have one here: http://axel.deri.ie/~axepol/presentations/20080922KeynoteXinnovationsPhDworkshopBerlin.pdf, slide 31, with the test data from slide 22, basically. 19:36:49 stella, let me know, if that looks worthwhile, I can shape it in the right format. 19:37:48 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Guards_and_subtypes 19:37:54 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Guards_and_subtypes 19:37:59 rrsagent, show pointer 19:37:59 I'm logging. I don't understand 'show pointer', ChrisW. Try /msg RRSAgent help 19:38:02 rrsagent, show pointer? 19:38:02 I'm logging. Sorry, nothing found for 'show pointer' 19:38:09 axel, yes that would be good 19:38:11 rrsagent, pointer? 19:38:11 See http://www.w3.org/2008/09/26-rif-irc#T19-38-11 19:38:22 rrsagent, anything 19:38:22 I'm logging. I don't understand 'anything', ChrisW. Try /msg RRSAgent help 19:39:25 action: josb to update description of Inconsistent entailment 19:39:25 Created ACTION-596 - Update description of Inconsistent entailment [on Jos de Bruijn - due 2008-10-03]. 19:39:49 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Inconsistent_Entailment 19:39:59 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Inconsistent_Entailment 19:40:05 rrsagent, pointer? 19:40:05 See http://www.w3.org/2008/09/26-rif-irc#T19-40-05 19:40:57 test case individual data separation inconsistency 19:41:09 chris: is this still true? 19:41:44 jos: a is a class, and then we say everything is of type a 19:41:51 chris: is this still true in OWL2? 19:41:58 jos: yes, I think it does 19:42:11 chris: in owl1.1 you could use same iri as both a class and an instance 19:42:31 jos: oops, I was talking about a different test case 19:43:06 jos: in owl-dl there is a separation between individual domains and data value domains 19:44:40 csma: any objections to this test case? 19:45:00 RRSAgent, pointer? 19:45:00 See http://www.w3.org/2008/09/26-rif-irc#T19-45-00 19:45:03 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Individual-Data_Separation_Inconsistency 19:45:08 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Individual-Data_Separation_Inconsistency 19:45:15 rrsagent, pointer? 19:45:15 See http://www.w3.org/2008/09/26-rif-irc#T19-45-15 19:45:23 csma: test case "local constant" 19:45:47 jos: in BLD LC WD, this was true , entailment relation doesn't preserve names of local constants 19:46:20 mk: in the current BLD, this is no longer true 19:46:33 mk, jos: this test isn't valid wrt to the current BLD 19:47:18 csma: test case: named_argument_uniterms/frames1 19:48:06 daver: tihs case, together with the other named_argument uniterm/frame give the idea 19:48:16 daver: can cross link between the 2 tests 19:51:17 jos: for 2nd one, the conclusion is not a valid question 19:52:05 jos: ...because a predicate can only occur in one context 19:52:15 someone should produce a Negative Syntax Test from this: ex:p(ex:a->1 ex:b->2) and ex:p(ex:a->1) 19:52:25 jos: even if it is in a separate document 19:53:00 csma: repeat the arg names 19:53:05 mk, dave: no, not allowed 19:54:41 csma: if rhis cannot be expressed in RIF, why do we need named arguement uniterms? 19:55:01 daver: I kind of agree 19:55:31 mk: can we go back and remove restrictoins such as no polymorphic symbols 19:56:25 chris: would be nice to capture named-argument uniterms as a negative syntax test 19:56:29 dave: will do it now 19:56:55 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Named_Argument_Uniterms/Frames_1 19:57:12 sandro: and change the names of the tests 19:58:44 PROPOSED: Approve http://www.w3.org/2005/rules/wiki/No_polymorphic_symbols 19:58:53 csma: test case: no polymorphic symbols 19:59:07 csma: syntax error - rejected by consumer 19:59:29 sandro: description should highligh that buy has 3 parms in one place, and 4 in another 19:59:55 action: Stella to update description in http://www.w3.org/2005/rules/wiki/No_polymorphic_symbols 19:59:55 Created ACTION-597 - Update description in http://www.w3.org/2005/rules/wiki/No_polymorphic_symbols [on Stella Mitchell - due 2008-10-03]. 20:00:01 PROPOSED: accept http://www.w3.org/2005/rules/wiki/No_polymorphic_symbols 20:00:10 RESOLVED: accept http://www.w3.org/2005/rules/wiki/No_polymorphic_symbols 20:00:14 PROPOSED: Approve http://www.w3.org/2005/rules/wiki/No_polymorphic_symbols 20:00:20 rrsagent, pointer? 20:00:20 See http://www.w3.org/2008/09/26-rif-irc#T20-00-20 20:00:49 csma: test case: non-annotation entailment 20:00:57 jos: this is the complement of annotation entailment test case 20:01:45 jos: in the earlier test case we were talking about owl-dl annotation entialment and this is plain owl-dl enatailment, so annotation properties are not considered in the entailment 20:02:04 chris: why do we need to prevent entailment of annotation properties? 20:02:32 jos: just following what is in owl 20:03:09 action: josb to update description of http://www.w3.org/2005/rules/wiki/Non-Annotation_Entailment 20:03:09 Created ACTION-598 - Update description of http://www.w3.org/2005/rules/wiki/Non-Annotation_Entailment [on Jos de Bruijn - due 2008-10-03]. 20:03:20 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Non-Annotation_Entailment 20:03:26 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Non-Annotation_Entailment 20:03:32 rrsagent, pointer? 20:03:32 See http://www.w3.org/2008/09/26-rif-irc#T20-03-32 20:03:33 csma: test case: owl combination vocabulary separation inconsistency1 20:04:05 jos: again, mixing of individual and concrete domains 20:07:10 axel: this would not be syntactially correct in owl-dl 20:07:14 various: but this is RIF 20:07:20 ...combination with OWL-DL 20:08:11 csma: axel, do you object? 20:08:12 PROPOSED: accept http://www.w3.org/2005/rules/wiki/OWL_Combination_Vocabulary_Separation_Inconsistency_1 20:08:16 axel: no 20:08:51 RESOLVED: accept http://www.w3.org/2005/rules/wiki/OWL_Combination_Vocabulary_Separation_Inconsistency_1 20:08:57 rrsagent, pointer? 20:08:57 See http://www.w3.org/2008/09/26-rif-irc#T20-08-57 20:09:05 my concern/ confusion basically was along the following lines: 20:09:30 sandro: will these (the ones applicable to core) turn into core tests? 20:09:55 test case; owl combination vocabulary separation inconsistency2 20:09:56 e.g. the pD* entailment rules from ter Horst 2005 would have no problems with http://www.w3.org/2005/rules/wiki/OWL_Combination_Vocabulary_Separation_Inconsistency_1 if written in RIF. 20:10:20 chris: is this still in owl2, object properties, datatype properties...? 20:10:22 jos: yes 20:10:46 jos: but in owl2 you have punning, but you can always determine from the context 20:11:06 dave: I thought that was dropped for object properties 20:11:08 ... it is just that I was astonished - hadn't realizzed that - when something is not in OWL DL syntactically we infer inconsistency... but if that is the agreement - and I don't have a better suggestion - then that's fine. 20:12:02 recent change in OWL2: "The major change to this document since the version of 11 April 2008 reflects the major revamping of the functional syntax to disallow punning between classes and datatypes and between object, data, and annotation properties. Some minor changes were made to reflect changes in the Functional Syntax." 20:12:36 axel: punning is not trivially combinable with our rules 20:13:12 PROPOSED: accept http://www.w3.org/2005/rules/wiki/OWL_Combination_Vocabulary_Separation_Inconsistency_2 20:13:22 RESOLVED: accept http://www.w3.org/2005/rules/wiki/OWL_Combination_Vocabulary_Separation_Inconsistency_2 20:13:29 rrsagent, pointer? 20:13:29 See http://www.w3.org/2008/09/26-rif-irc#T20-13-29 20:13:58 test case: frame slots are independent 20:14:24 ...renamed from named/arg untierms... 20:14:44 csma: any objection to accepting this? 20:14:45 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Frame_slots_are_independent 20:15:14 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Frame_slots_are_independent 20:15:18 rrsagent, pointer? 20:15:18 See http://www.w3.org/2008/09/26-rif-irc#T20-15-18 20:15:42 PROPOSED: accept http://www.w3.org/2005/rules/wiki/Named_Argument_Uniterms_non-polymorphic 20:16:11 RESOLVED: accept http://www.w3.org/2005/rules/wiki/Named_Argument_Uniterms_non-polymorphic 20:16:22 rrsagent, pointer? 20:16:22 See http://www.w3.org/2008/09/26-rif-irc#T20-16-22 20:17:53 csma: who read the description of semantics of conditions in PRD? 20:17:58 ...a few 20:19:19 csma: in 1st WD, the semantics was described operationally 20:19:32 ...question was rasied of how we relate this to DTB? 20:19:54 ...suggestion was to describe semantics of conditions in PRD in the same was as in BLD 20:20:38 chris: I don't understand the link, between need to link to DTB and how to specify conditions 20:21:31 chris: question about what is being done here, with actions vs. conditions 20:22:06 gary: prd: start with rules and facts, then ask which rules you want to fire 20:22:21 ...conditions tell you which to fire (might only pick some of them) 20:22:36 ...the rules that fire cause actions to be executed 20:22:52 ...actions change state of things 20:22:55 ...then repeat 20:23:49 csma: semantics of facts in actions is the same as semantics of facts in conditions 20:24:48 csma: adrian proposed a definition that is as similar to BLD as possible 20:25:03 gary: it is possible to just point to BLD from here? 20:26:44 csma: Definition of Satisfaction is the important point 20:28:39 gary: why do we need extra substitution step mapping variables to ? 20:29:13 csma: we wanted to mention this in the plenary so that semantisists can comment 20:29:36 jos: why don't use you a semantic structure? 20:29:39 csma: we do 20:30:07 csma: but we also have operational semantics for the action part 20:30:27 jos: the set of facts is equivalent to a semantic structure, and go directly from w to w1 20:30:37 s/w1/w'/ 20:31:54 csma: I'd like to see it written as a draft, and then we have to relate it to the working memory 20:32:01 ...and take into consideration the target audience 20:32:41 gary: "w" is very syntactic 20:32:52 ,,,2 different things in syntax map to same thing in the domain 20:33:35 adrian: and it needs to be restructured 20:34:02 csma: no, I moved it into the "instantiate rules" part 20:34:25 csma:...but I agree that the document needs to be reorganized 20:35:37 jos: you need the substitution because of assert and .. in head 20:35:56 chris: not if you define it as transitions 20:35:58 jos: ok 20:38:08 csma: we can in one of several ways, but currently it is incorrect 20:38:56 ... (definition of pattern matching) 20:39:03 ...get rid of sigma 20:41:03 .chris: target audience may not understand what the variable mapping means 20:41:24 csma: we need to add a paragraph to explain variable binding 20:42:05 csma: in signature, adrian introduced a function "type" 20:42:14 adrian: that is to introduce a multi-sorted type system 20:42:35 csma: I'm not sure this is required for PRD 20:43:06 gary: you can do type referencing with guards 20:43:33 csma: and a few other things that could be removed from the signatures 20:43:44 daver: and another mistake: frames don't have an arity 20:44:15 gary: this is supposed to be mirroring BLD in the syntax area 20:44:30 csma: but syntax is what we will define semantics of 20:44:54 csma: and other simpler things 20:45:22 taking a break 20:45:33 csma: the main point was about the semantics of pattern matching 20:48:42 ACTION: AdrianP to reformulate PRD condition semantics without substitution 20:48:42 Sorry, couldn't find user - AdrianP 20:49:14 ACTION: AdrianPaschke to reformulate PRD condition semantics without 20:49:14 Sorry, couldn't find user - AdrianPaschke 20:49:30 ACTION: AdriaP to reformulate PRD condition semantics without 20:49:30 Sorry, couldn't find user - AdriaP 20:49:59 ACTION: APaschke to reformulate PRD condition semantics without 20:49:59 Created ACTION-599 - Reformulate PRD condition semantics without [on Adrian Paschke - due 2008-10-03]. 21:04:29 AxelPolleres has joined #rif 21:06:44 Guys & gals I'm falling asleep - it's been a very long day. I'll try and be a more active participant tomorrow. Enjoy dinner 21:07:01 Enjoy, BobMoore 21:07:01 scribenick Blaz 21:07:12 scribenick: Blaz 21:07:21 -BobMoore 21:07:38 chrisw: open issues in BLD: roundtripping; at risk: external frames (because there was confusion about exactly what they were), equality in the conclusion, scrictness requirement @ conformance 21:07:41 ScribeNick: Blaz 21:09:36 chrisw: at the last f2f we discussed the idea of 'consumer' that implements extensions; we added the clause there may be a strictness mode that will reject everything that is not in BLD 21:10:48 csma: the point is it is not a requirement 21:11:24 chrisw: there is no harm in leaving "at risk" in for now 21:12:17 -Meeting_Room 21:12:18 Team_(rif)18:42Z has ended 21:12:20 Attendees were +0777841aaaa, BobMoore, AxelPolleres, SandroHawke, JosDeBruijn, MikeDean, StellaMitchell, LeoraMorgenstern, BlazNovak, MichealKifer, DaveReynolds, AdrianPaschke, 21:12:22 ... HaroldBoley, GaryHallmark, ChrisWelty, ChristianDeSainteMarie 21:12:29 csma: equality in the conclusion remains 'at risk', because some of the implementers might want not to implement it 21:13:58 jos: it might be possible to introduce an inconsistency even without this 21:15:18 mk: nobody will implement this anyway 21:15:29 mk: we should do something about conformance, then 21:15:50 csma: we can not remove it now 21:16:22 also with RDF and RDFS combinations we can have inconsistencies, because there can be inconsistencies in these languages 21:17:46 what is the terminology - head/body? condition/conclusion? 21:18:00 chrisw: the language should be made consistent 21:18:19 mk: 'premise' is used a lot, 'body' is used in a couple of places 21:18:28 mk: 'body'/'head' is used in the translation to XML too 21:18:47 mk: conclusion and premise? 21:19:25 voting on "premise" and "condition" 21:19:38 condition wins 21:20:09 ignoring Axel and Sandro saying "if-part" 21:20:19 not really a WG decision. 21:20:32 Chris: At very least, get rid of Body and Head. 21:20:58 chrisw: leaving equality at risk 21:21:28 chrisw: what is external about external frames 21:21:42 mk: it's just like external predicates... it's just the same thing, but different syntax 21:22:20 csma: P(a,b) .. if P has a fixed interpretation, then this is an external: Ext[P(a,b)] 21:23:13 mk: you are asking an external source, and it tells you yes or no 21:23:22 ... you are making a query to an external source 21:24:17 csma: [to mk] is it a way to address 'external methods' ? 21:25:15 Ext[P(a,b)] vs. Ext(a[P->b]) -- is using the same device for differrent purposes 21:25:31 csma: my understanding of the current def. of 'external' is that it is a function 21:25:51 mk: originally, the idea was just to do builtins, then we discussed that people might want to access external datasources 21:25:58 csma: but this is completely different 21:26:00 mk: no 21:26:12 dave: the builtin location is part of a step 21:26:25 mk: you can not really draw a boundary between external sources and builtins 21:26:30 csma: I think it is wrong 21:26:56 mk: it really means a query to some source 21:27:06 mk: we are just asking a query 21:27:23 csma: I agree they are the same 21:27:52 csma: if a and P are both IRIs .. which one is external? 21:28:03 mk: if a is an IRI, it means 'query me this way' 21:28:25 mk: if it's not an IRI, but some other constant .. you would do some other thing .. the object tells you how to query it 21:28:49 mk: it's a matter of modelling. you can model something as a predicate, relation, class, 21:29:22 csma: in Ext[P(a,b)] there is no ambiguity. what is external is 'P'. if both are equivalent... 21:29:47 mk: I'm saying I can think of situations where you have an object that is sitting externally and that object can be asked various things 21:29:59 mk: and that object http://www.ibm.com/ and P would be 'president' .. 21:30:29 csma: when I receive a document where there is an external frame and I have to deserialize it .. how do I know which is extenral? I know when I'm executing it, but how do I know when I'm deserializing it ? 21:30:46 csma: this is an interchange format; when I see an XML document I want do deserialize it into my own lanugage 21:30:59 mk: how do you perform calls to external sources? 21:31:23 csma: I'm not saying we do not need it 21:32:03 csma: I have to know wether 'a' is stored in an object database at the address given by 'a' or if 'P' is ____. I need to know it syntactically 21:32:20 chrisw: I don't understand the role of externals 21:32:55 mk: if you're getting a document with an ext. and unless you know how to call the external, you can not use it .. 21:33:42 csma: then, what you're saying, it is indeed related to the question about user defined data models and functions. this is what I hear 21:33:47 dave nods no 21:34:04 mk: for the predicate you have to know how many arguments it has. then you also have to know the model of the predicate. 21:34:19 chrisw: the moment you use it, you find out its model. why do you need external? 21:34:27 mk: otherwise you'll have to try to match it to your own predicates 21:34:37 csma: external tells you its interpretation is fixed outside the ruleset 21:34:47 csma: fixed interpretation is a nice way to say it. 21:34:56 gary: it's fixed but you might not know what it is 21:35:05 csma: it's interpretaiton is external to the ruleset 21:35:44 csma: to me it is clear if I find an ext. predicate I know there is a specification of that predicate somewhere and I have to know it if I want do do something and it might be an extension if it is a call to a database or an intention of ... 21:35:57 csma: I can not get what an external frame means 21:37:17 chrisw: the question is: what is external: in Ext[P(a b)] it's P. how about in Ext(a(P->b]) ? 21:37:26 mk: the meaning of this is not a part of your ruleset 21:37:39 jos: could you view this as an external ternary predicate [the second one] 21:37:44 jos: that has a fixed interpretation 21:38:03 mk: you also know there should be some protocol to say 'send me this stuff..' 21:38:16 "This section introduces the notion of external schemas, which serve as templates for externally defined terms. These schemas determine which externally defined terms are acceptable in a RIF dialect." from FLD, section 2.5 21:38:38 THis means the externally definined schemas are hard-wired with a dialect. 21:39:16 MoZ has joined #rif 21:39:19 csma: in the second case, even if you have an IRI, where do I send my query? 21:39:49 csma: I did not say you have to send it there; but if you have that address, then being able to identify P tells you exactly what to do 21:40:24 csma: I'm not thinking about anything magical 21:40:54 mk: you have an address and there is some XML. if you want to talk to this address, you have to know what message to send. wether there are 2 or 5 arguments. what this message is to be 21:41:20 csma: I perfectly understand this. my question is: 21:41:39 csma: my understanding was: P unambigously identifies this address 21:41:41 mk: no 21:41:48 csma: how do I know this address? 21:42:11 chrisw interrupts the discussion 21:42:31 chrisw: who understands external frames? 21:42:37 chrisw: jos you try to explain it 21:42:55 csma: give me an example 21:42:59 jos: I have no idea what they are good for 21:43:12 axel: I think they are completely redundant 21:43:45 axel: which external things are allowed in External? it is defined in RIF DTB in coherent set of schemata. it is fixed for a dialect. 21:43:54 axel: the dialect has to define what the fixed semantics of this is 21:44:26 csma: the point is, your dialect has to specifiy a consistent schema and define what it means 21:44:47 csma: BLD does not specify any consistent schema for external frames 21:44:57 csma: if you want to have them, you have to provide a schema 21:45:21 chrisw: the claim that 4 people just agreed to is that external frames are useless 21:45:34 chrisw: this only has use if you're extending BLD with your datatypes 21:45:59 csma: I did not think of that you have to provide a consistent schema 21:46:24 chrisw: so maybe extending a definition of external frames .. just a little note: "meant for extending datatypes for use with BLD" 21:47:40 chrisw: don't ever question understanding ... 21:48:00 chrisw: does it make sense to pull the 'at risk' statement? 21:49:41 chrisw: would you object to removing external frames? 21:50:58 mk: you have one KB somewhere and this tells you how to represent things 21:51:46 axel: if that is a datasource that allows you to query frames, then you'd need to give the address anyway; so you couldn't pack it in an external schema 21:51:57 mk: we are going to a different level 21:52:14 mk: we can express everything with predicates and do not need frames at all ... 21:52:37 axel: but frames are convenient 21:53:06 mk: the question is 'do we need frames at all or not' -- it's the same discussion 21:53:20 chrisw: anyway. let's stop. 21:53:35 chrisw: so we got to the point of 'there would be objections to removing external frames' 21:53:45 chrisw: anyone against removing 'at risk' ? 21:53:48 noone against 21:54:00 chrisw: let's add this to the list of resolutions to be passed tomorow 21:54:14 : remove at-risk for external. 21:54:21 chrisw: roundtriping 21:54:43 mk: did we decide on at-risk on equality? 21:54:52 chrisw: we're keeping it 21:54:59 Why then not allow any "parametrizable string template" for external schemata? by that, we could e.g. for free get external calls to SPARQL endpoints or SQL databases, etc. etc. 21:55:34 csma: did we decide to keep at risk for 'strictness conformance'? 21:55:34 ... That would generalize the external schemas in a very beneficial way! 21:55:40 chrisw: no 21:57:19 ... e.g. External( ?X ?Y "SELECT ?X FROM WHERE { ... ?Y ... }" ) would be a possible schema. 21:57:19 csma: we kept it because we'll wait for implementations 21:58:11 ... whereas we currently enforce "RIF term syntax" for the external calls, which is unnecessarily restrictive. 21:58:12 chrisw: the only place we talked about roundtripping is in conformance section 21:58:49 chrisw: jos complained that 'what does it mean to maintain the semantic meaning' is not specific enough 21:59:33 jos: this whole paragraph can be removed; it doesn't say much 21:59:52 chrisw: it's trying to say that conformance does not mean things need to look the same 22:00:02 jos: this paragraph does not say anything about conformance 22:00:30 csma: [reads] "a nonconformant implementation might not preserve the semantics in the roundtrip" 22:00:55 jos: does anyone want to have some paragraph about roundtripping? 22:01:23 csma: the question was should we say something about survivability of metadata? this is the important point 22:01:56 chrisw: we could add metadata survivability here [a couple paragraphs earlier] 22:02:46 csma: in some test cases there is a notion of 'the same ruleset' if you send me the ruleset back 22:03:10 jos: the only notion we have now is 'semantics preserving mapping' 22:03:53 csma: if we have that notion of keeping the identity of a document, they can keep the metadata as XML and send it back when they return the document 22:04:00 csma: wedo not have the notion of the identity of document here 22:04:07 csma: this is probably why it does not make sense 22:04:27 csma: our processing model is just producer/consumer. it does not define roundtripping of documents 22:04:38 csma: so the notion of surviving metadata is not defined as well 22:04:41 mk: it could be a recommendation 22:05:11 csma: we have test cases where the notion of passing metadata along makes sense .. but perhaps not in BLD .. maybe in PRD 22:05:22 harold: it could be just conformant, or annotation conformant 22:05:32 harold: it is a stronger level of 'conformant' 22:06:11 csma: you have metadata about something that is identified uniquely -- if you use the same identifier for something, you can use the same metadata 22:06:15 jos: it is attached to structural elements 22:06:45 chrisw: here is the proposal: I proposed we remove this paragraph because it does not say anything 22:07:08 chrisw: and add here the intention of 'metadata survivability' to [first bulletpoint in RIF-BLD specific clauses] 22:08:07 chrisw: "conformant producers and consumers ... should ... preserve annotations ... where possible" 22:08:31 chrisw: anyone opposed? 22:08:34 noone. 22:08:46 chrisw: for tomorow, we will vote on this resolution 22:09:20 Annotations ''should'' survive BLD round-tripping whenever possible. 22:09:40 Annotations ''should'' survive BLD transformations whenever possible. 22:10:28 action: chrisw to draft revised metadata conformance wording for BLD 22:10:28 Sorry, couldn't find user - chrisw 22:10:37 action: chris to draft revised metadata conformance wording for BLD 22:10:37 Created ACTION-600 - Draft revised metadata conformance wording for BLD [on Christopher Welty - due 2008-10-03]. 22:13:59 logout 22:14:03 rrsagent, make logs public 22:14:08 zakim, list attendees 22:14:08 sorry, ChrisW, I don't know what conference this is 22:14:17 rrsagent, make minutes 22:14:17 I have made the request to generate http://www.w3.org/2008/09/26-rif-minutes.html ChrisW