15:53:02 RRSAgent has joined #rif 15:53:02 logging to http://www.w3.org/2008/11/11-rif-irc 15:53:12 zakim, this will be rif 15:53:12 ok, ChrisW; I see SW_RIF()11:00AM scheduled to start in 7 minutes 15:53:35 Meeting: RIF Telecon 11-Nov-08 15:53:43 Chair: Christian de Sainte-Marie 15:54:22 Agenda: http://lists.w3.org/Archives/Public/public-rif-wg/2008Nov/0029.html 15:54:44 ChrisW has changed the topic to: 11 Nov RIF Telecon Agenda http://lists.w3.org/Archives/Public/public-rif-wg/2008Nov/0029.html 15:54:56 rrsagent, make minutes 15:54:56 I have made the request to generate http://www.w3.org/2008/11/11-rif-minutes.html ChrisW 15:55:23 zakim, clear agenda 15:55:23 agenda cleared 15:55:28 agenda+ Admin 15:55:33 Agenda+ Liason 15:55:39 Agenda+ Public comments 15:55:45 Agenda+ Action review 15:55:52 Agenda+ rdf:text 15:55:57 Agenda+ PRD 15:56:01 Agenda+ UCR 15:56:05 Agenda+ DTB 15:56:11 Agenda+ PICK SCRIBE 15:56:16 Agenda+ AOB 15:57:35 rrsagent, make logs public 15:57:52 Harold has joined #rif 16:00:29 SW_RIF()11:00AM has now started 16:00:31 + +0122427aaaa 16:00:33 SW_RIF()11:00AM has ended 16:00:34 Attendees were +0122427aaaa 16:00:39 DaveReynolds has joined #rif 16:01:36 SW_RIF()11:00AM has now started 16:01:37 +??P44 16:01:41 +Harold 16:01:42 -Harold 16:01:42 +Harold 16:01:48 StuartTaylor has joined #rif 16:02:08 Stella has joined #rif 16:02:25 josb has joined #rif 16:02:35 +josb 16:02:52 + +0122427aaaa 16:03:02 +[IBM] 16:03:07 zakim, ibm is temporarily me 16:03:07 +Stella; got it 16:03:18 zakim, +0122427aaaa is me 16:03:18 +StuartTaylor; got it 16:03:24 +Sandro 16:03:25 +??P55 16:03:26 + +1.914.784.aabb 16:03:31 zakim, aabb is me 16:03:31 +ChrisW; got it 16:04:18 Scribe: Harold 16:04:20 AxelPolleres has joined #rif 16:04:39 http://lists.w3.org/Archives/Public/public-rif-wg/2008Nov/att-0008/2008-11-04-rif-minutes.html 16:04:47 PROPOSED: Approve last weeks minutes 16:04:52 RESOLVED: Approve last weeks minutes 16:05:09 zakim, next item 16:05:09 agendum 1. "Admin" taken up [from ChrisW] 16:05:26 +??P61 16:05:31 action: Chris to change times to standard time in agenda 16:05:31 Created ACTION-643 - Change times to standard time in agenda [on Christopher Welty - due 2008-11-18]. 16:05:46 zakim, who is on the phone? 16:05:46 On the phone I see Harold, DaveReynolds, josb, StuartTaylor, Stella, Sandro, ChrisW, ??P55, ??P61 16:08:34 zakim, ??P55 is AdrianP 16:08:34 +AdrianP; got it 16:09:19 zakim, next item 16:09:19 agendum 2. "Liason" taken up [from ChrisW] 16:10:36 +Gary 16:10:54 Gary_Hallmark has joined #rif 16:11:25 Axel: Mapping rules written in a RIF dialect would be fine for his liaison. 16:11:51 zakim, next item 16:11:51 agendum 3. "Public comments" taken up [from ChrisW] 16:12:36 Sandro: Jos is going to visit OWL-WG to talk about ID/IDREF. 16:13:49 Chris: Three outstanding responses. 16:14:21 ... Just point OK to the changed BLD text. 16:14:27 action: chris to draft comment to ok 16:14:27 Created ACTION-644 - Draft comment to ok [on Christopher Welty - due 2008-11-18]. 16:14:52 action: Chris to send WL response 16:14:52 Created ACTION-645 - Send WL response [on Christopher Welty - due 2008-11-18]. 16:15:44 (I'm having trouble with international dialing. Anyone else have another phone line they can use to call Christian? msg me if you need the number.) 16:16:19 LeoraMorgenstern has joined #rif 16:16:20 http://www.w3.org/2005/rules/wiki/Response_to_RAK 16:16:39 action: Gary to draft response to http://www.w3.org/2005/rules/wiki/Response_to_RAK 16:16:39 Created ACTION-646 - Draft response to http://www.w3.org/2005/rules/wiki/Response_to_RAK [on Gary Hallmark - due 2008-11-18]. 16:16:47 +LeoraMorgenstern 16:16:49 zakim, next item 16:16:49 agendum 4. "Action review" taken up [from ChrisW] 16:18:58 614; I'm just sending out hte email 16:19:47 mkifer has joined #rif 16:20:55 +Michael_Kifer 16:21:48 Michael, should we put changes always into section 2 of specs? _ thought it would always be the last appendix: http://www.w3.org/2005/rules/wiki/BLD#Changes_Since_the_Last_Call_Version_.282008-07-30.29 16:22:24 should manifest be higher priority than that translator? 16:22:34 I mean, shouldn't 16:24:37 zakim, next item 16:24:37 agendum 5. "rdf:text" taken up [from ChrisW] 16:25:44 zakim, who is talking? 16:25:49 Axel: Found agreement with OWL WG on rdf:text. 16:25:54 ChrisW, listening for 10 seconds I heard sound from the following: ChrisW (5%), Sandro (18%), AxelPolleres (4%) 16:26:24 zakim, who is talking? 16:26:35 sandro, listening for 10 seconds I heard sound from the following: ChrisW (74%), Sandro (30%) 16:29:14 action: axel to add editors note regarding status of finite/infinite characters 16:29:14 Created ACTION-647 - Add editors note regarding status of finite/infinite characters [on Axel Polleres - due 2008-11-18]. 16:30:00 PROPOSED: Publish rdf:text as a FPWD, jointly with OWL-WG, given the Editor's Note about infinite character sets gets added. 16:30:12 +1 (W3C) 16:31:27 http://www.w3.org/2007/OWL/wiki/InternationalizedStringSpec 16:31:29 http://www.w3.org/2007/OWL/wiki/InternationalizedStringSpec 16:31:48 PROPOSED: Publish rdf:text as a FPWD, jointly with OWL-WG, given the Editor's Notes about infinite character sets (per Chris) and about compat with XML schema (per Jos) gets added. 16:32:11 action: axel to add editors note on xml schema compatibility 16:32:13 Created ACTION-648 - Add editors note on xml schema compatibility [on Axel Polleres - due 2008-11-18]. 16:33:14 Jos: The infiniteness of the lex and val space, as well as the compatibilty with xml string -- whether the string spart of the lex & val space should be the same as xs:string -- are under discussion. 16:34:00 s/infiniteness of the lex and val space/infiniteness of the character set/ 16:34:11 ... Sandro: Best as two separate Ed 16:34:15 s notes. 16:35:30 Jos/Sandro: One should be fine if both aspects are kept together. 16:35:52 PROPOSED: Publish rdf:text as a FPWD, jointly with OWL-WG, adding an editor's note about infinity (actions Jos, Axel) 16:36:19 -DaveReynolds 16:36:19 +1 16:36:29 +1 (W3C) 16:36:38 +1 (DERI) 16:36:43 +1 (NRC) 16:36:44 +1 (FUB) 16:36:52 RRSAgent, pointer? 16:36:52 See http://www.w3.org/2008/11/11-rif-irc#T16-36-52 16:36:53 +1 16:36:54 +1 (Oracle) 16:37:02 +1 (IBM) 16:37:24 +1 (Aberdeen) 16:37:31 +1 16:37:35 RESOLVED: Publish rdf:text as a FPWD, jointly with OWL-WG, adding an editor's note about infinity (actions Jos, Axel) 16:37:39 zakim, who is on the phone? 16:37:39 On the phone I see Harold, josb, StuartTaylor, Stella, Sandro, ChrisW, AdrianP, AxelPolleres, Gary, LeoraMorgenstern, Michael_Kifer 16:38:17 action: send proposed editors note to rdf:text 16:38:17 Sorry, couldn't find user - send 16:38:26 Jos: Will send editor's note, Axel should track.it. 16:38:28 action: debruij2 send proposed editors note to rdf:text 16:38:28 Sorry, couldn't find user - debruij2 16:38:34 action: jdebruij2 send proposed editors note to rdf:text 16:38:35 Created ACTION-649 - Send proposed editors note to rdf:text [on Jos de Bruijn - due 2008-11-18]. 16:38:52 action: Sandro to publish rdf:text 16:38:52 Created ACTION-650 - Publish rdf:text [on Sandro Hawke - due 2008-11-18]. 16:39:20 zakim, next item 16:39:20 agendum 6. "PRD" taken up [from ChrisW] 16:39:24 AxelPolleres has left #rif 16:39:42 AxelPolleres has joined #rif 16:40:22 Chris: Trying to call Christian's cell... 16:40:53 Gary: Most actions from Orlando were put into the PRD document. 16:41:40 ... E.g., our understanding of conflict resolution strategies is now in the text. 16:41:52 ... People could start draft on wiki and give feedback. 16:41:53 no response from csma's phone 16:42:24 Sandro: Does it look like easily implementable on exist. PR engines? 16:43:02 Gary: Some aspects are not trivial to implement. 16:44:25 ... E.g., tagging Obj. with particular class via Member is not usual in PR engines. 16:45:38 ... Better than removing Member from Core. 16:45:43 *PROPOSED:* In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated using keywords, attached to the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). RIF-PRD 1.0 MAY specify other conflict resolution strategies (and corresponding keywords) for suggested use, but these will not be conformance points. This resolution and t 16:47:19 Sandro: Sent email about two issues with this PROPOSED. 16:47:44 ... 1) The term 'keyword' is not great. 16:48:38 Sandro: I just want it clarified that the strategy could be indicated by being part of the element name 16:48:40 I sent the email to public-rdf-text 16:48:48 ... In XML it seems to imply it would become an attribute, while it may well become a subelement. 16:48:51 Gary: I don't think we're saying anything one way or the other about that. 16:49:08 *PROPOSED:* In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated in some way attached to the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). RIF-PRD 1.0 MAY specify other conflict resolution strategies (and corresponding keywords) for suggested use, but these will not be conformance points. This resolution and the c 16:50:22 PROPOSED: In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated in some way attached to the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). RIF-PRD 1.0 MAY specify other conflict resolution strategies (and corresponding keywords) for suggested use, but these will not be mandatory. This resolution and the complementar 16:50:49 *PROPOSED:* In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated using keywords, attached to the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). RIF-PRD 1.0 MAY specify other conflict resolution strategies (and corresponding keywords) for suggested use, but these will not be conformance points. This resolution and t 16:51:21 *PROPOSED:* In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated using keywords, attached to the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). RIF-PRD 1.0 MAY specify other conflict resolution strategies (and corresponding keywords) for suggested use, but these will not be conformance points. 16:51:32 PROPOSED: In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated using keywords, attached to the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). RIF-PRD 1.0 MAY specify other conflict resolution strategies (and corresponding keywords) for suggested use, but these will not be conformance points. 16:52:33 PROPOSED: In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated in some way, associated with the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). 16:53:28 Sandro: So this means you can't merge rulesets.... but that's the state of the art anyway. 16:53:28 PROPOSED: RIF-PRD 1.0 MAY specify other conflict resolution strategies for suggested use, but these will not be mandatory. 16:53:40 PROPOSED: Close Issue-64 16:53:56 issue-64 16:53:59 issue-64? 16:54:10 ISSUE-64 -- Conflict resolution strategies to be covered by PRD? -- OPEN 16:54:10 http://www.w3.org/2005/rules/wg/track/issues/64 16:54:54 +0 16:54:59 +1 16:55:02 +0 on all three at once 16:55:06 +1 16:55:07 0 16:55:08 +1 16:55:28 RESOLVED: In RIF-PRD, the conflict resolution strategy for a set of rules will be indicated in some way, associated with the top-level group. RIF-PRD 1.0 will specify only one normative conflict resolution strategy, as specified in csma's email [9] (essentially: refraction+priority+recency). 16:55:39 RESOLVED: RIF-PRD 1.0 MAY specify other conflict resolution strategies for suggested use, but these will not be mandatory. 16:55:47 RESOLVED: Close Issue-64 16:55:52 mkifer has joined #rif 16:55:58 action: chris to close issue 64 16:56:01 rrsagent, pointer 16:56:01 See http://www.w3.org/2008/11/11-rif-irc#T16-56-01 16:56:16 zakim, next item 16:56:16 agendum 8. "DTB" taken up [from ChrisW] 16:56:30 Created ACTION-651 - Close issue 64 [on Christopher Welty - due 2008-11-18]. 16:57:16 Axel: Let's go thru the Ed's notes. 17:00:25 Basically Remove: We might introduce additional shortcuts, e.g. for rif:text 17:00:35 StuartTaylor has joined #rif 17:00:39 Remove: rif:text (in particular, its identifying IRI) is an AT RISK feature. 17:01:36 Re: The naming convention for guard predicates, ... 17:02:13 Axel: Would just leave text unchanged and remove Ed's note. 17:03:10 ... When you define your own dialect, should you be encouraged to reuse pred/func prefixes. 17:03:26 ... Who is authorized to reuse such namespace prefixes? 17:03:31 Sandro: W3C. 17:04:30 Axel: Should we say new W3C specs should use these namespace prefixes? 17:04:55 Chris: Give advice. Use word "should" or "should not". 17:05:00 W3C specs MAY reuse, 3rd party dialects MUST NOT reuse the pred and func namespace 17:05:00 ? 17:05:21 SHOULD and SHOULD NOT? 17:06:31 Re: It was noted in discussions of the working group, that except guard ... SPARQL's datatype function ... needed. 17:07:05 Axel: Which value to return? 17:07:22 ... Can not emulate the same behavior. 17:07:28 ... Even with a predicate. 17:07:46 ... SPARQL's datatype functions cannot be emulated. 17:07:49 that's because SPARQL's def is broken 17:09:12 Chris: But what about adding a predicate (not a function), which can bind all these multiple values? 17:09:29 ... Was proposed by Dave Reynolds. 17:11:06 ... Single predicate for checking types instead of one for each. 17:11:47 Re: The naming convention for negative guard predicates ... 17:11:54 Axel: Same thing. 17:12:14 Re: In the following, we adapt several cast functions from [XPath-Functions]. 17:12:28 Axel: Only referring to conversion table. 17:12:37 ... Would need more refined explanation. 17:12:57 ... Will try to resolve and have it reviewed. 17:13:24 Re: We might split this subsection into separate subsections per casting function... 17:13:36 Axel: TBD 17:14:02 Re: The cast from rif:text to xs:string is still under discussion, ... 17:14:24 Chris: This fct stays here. 17:14:28 Axel: OK. 17:14:52 Re: Conversion from rif:iri to xs:string and vice versa is still under discussion ... 17:15:08 Axel: If everyone is fine as is, we can leave it. 17:15:32 ... Strange thing is that can be viewed in both conversion directions. 17:15:44 ... Only one is intended. 17:16:34 ... Use case is creation URI from string. 17:16:49 Sandro: Comes also up in POWDER. 17:17:11 ... They have various such conversion needs. 17:17:32 s/URI/IRI/ 17:17:56 Axel: Only the predicate NAME is a problem. 17:18:10 ... It's fine to use the same predicate. 17:18:28 Sandro: Think has just been called IRI. 17:19:01 ... Gives you IRI of anything. 17:19:27 ... Need a bunch of test cases. 17:19:36 ... Tricky 'corner' of the language. 17:19:53 Axel: Could write some, but Jos is better in this. 17:20:46 ... OK to rename it into iristring? 17:20:56 Jos/Sandro: Yes. 17:21:32 Chris: Potential unexpected results? 17:21:50 Jos: Only some IRIs you dont expect from strings, and vice versa. 17:22:03 ... Will do. 17:22:12 Sandro: Some should use RDF. 17:22:21 Jos/Axel: OK. 17:22:23 action: jos to write some more pathological test cases for potentially confusing uses of iri-string predicate 17:22:23 Sorry, amibiguous username (more than one match) - jos 17:22:23 Try using a different identifier, such as family name or username (eg. jdebruij2, jderoo) 17:22:34 action: jdebruij2 to write some more pathological test cases for potentially confusing uses of iri-string predicate 17:22:44 Created ACTION-652 - Write some more pathological test cases for potentially confusing uses of iri-string predicate [on Jos de Bruijn - due 2008-11-18]. 17:23:00 Re: The following treatment of built-ins which may have multiple arities ... 17:24:43 Axel: Would propose to keep multiple arities. 17:25:26 Harold: We need this for min and max functions (for uncertainty encoding etc.). 17:25:41 StuartTaylor has joined #rif 17:25:59 Chris: Problem: Would you need infinitely many functions, then, semantically? 17:26:03 Axel: No. 17:26:40 Chris: Seems fine as a syntactic convention. 17:27:33 Axel: If we allow variable arities in External, then we are done, too. 17:27:49 action: chris to open issue on polyadic functions per not in DTB 3.5 17:27:51 StuartTaylor has joined #rif 17:27:53 Created ACTION-653 - Open issue on polyadic functions per not in DTB 3.5 [on Christopher Welty - due 2008-11-18]. 17:28:53 action: Chris to put remaining DTB editors notes on agenda 17:29:12 Chris: Remaining four Ed's notes in DTB moved to next telecon. 17:29:15 zakim, next item 17:29:15 agendum 9. "PICK SCRIBE" taken up [from ChrisW] 17:29:22 Axel: Add link to issue. 17:29:39 scribe for next week: leora 17:29:39 Created ACTION-654 - Put remaining DTB editors notes on agenda [on Christopher Welty - due 2008-11-18]. 17:29:50 zakim, next item 17:29:50 agendum 9 was just opened, ChrisW 17:30:10 -Michael_Kifer 17:30:11 -Stella 17:30:12 zakim, list attendees 17:30:12 As of this point the attendees have been Harold, DaveReynolds, josb, Stella, StuartTaylor, Sandro, +1.914.784.aabb, ChrisW, AxelPolleres, AdrianP, Gary, LeoraMorgenstern, 17:30:15 ... Michael_Kifer 17:30:15 -LeoraMorgenstern 17:30:16 -josb 17:30:18 -AdrianP 17:30:23 -StuartTaylor 17:30:28 -Gary 17:31:00 Regrets: Hassan Aït-Kaci Christian de Sainte Marie (at risk) PaulVincent 17:31:05 rrsagent, make minutes 17:31:05 I have made the request to generate http://www.w3.org/2008/11/11-rif-minutes.html ChrisW 17:31:18 -Harold 17:31:24 -AxelPolleres 17:32:02 -Sandro 17:32:05 -ChrisW 17:32:06 SW_RIF()11:00AM has ended 17:32:08 Attendees were Harold, DaveReynolds, josb, Stella, StuartTaylor, Sandro, +1.914.784.aabb, ChrisW, AxelPolleres, AdrianP, Gary, LeoraMorgenstern, Michael_Kifer