15:41:23 RRSAgent has joined #rif 15:41:23 logging to http://www.w3.org/2007/11/27-rif-irc 15:44:27 Topic: 27 November RIF telecon agenda: http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0080.html 15:44:49 Agenda: http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0080.html 15:45:01 Scribe: Leora Morgenstern 15:45:13 csma has left #rif 15:45:19 csma has joined #rif 15:46:01 csma has changed the topic to: 27 November RIF telecon qgendq: http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0080.html 15:46:21 Zakim, list agenda 15:46:21 I see 1 item remaining on the agenda: 15:46:22 8. Issue 40 [from csma] 15:46:32 zakim, close agenda 15:46:32 I don't understand 'close agenda', csma 15:46:39 zakim, reset agenda 15:46:39 I don't understand 'reset agenda', csma 15:46:53 zakim, delete agenda 15:46:53 I don't understand 'delete agenda', csma 15:48:39 zakim, clear agenda 15:48:39 agenda cleared 15:49:12 agenda+ Admin 15:49:35 agenda+ Liaisons 15:49:48 agenda+ F2F9 15:50:18 agenda+ OWL compatibility 15:51:03 agenda+ Issue 41 (membership) 15:51:28 agenda+ Issue 43 (classification) 15:51:56 agenda+ Issue 44 (named arguments uniterm) 15:52:17 bijan has joined #rif 15:52:22 agenda+ Issue 45 (lists) 15:52:54 agenda+ AOB (pick scribe for next time!) 15:54:02 SW_RIF()11:00AM has now started 15:54:03 +??P7 15:54:12 zakim, ??p7 is me 15:54:12 +bijan; got it 15:54:18 zakim, mute me 15:54:18 sorry, bijan, muting is not permitted when only one person is present 15:54:31 You mean I have to listen to myself talk? 15:54:33 Fooey 15:54:54 PaulaP has joined #rif 15:57:24 LeoraMorgenstern has joined #rif 15:57:57 Harold has joined #rif 15:59:14 Darko_A has joined #rif 15:59:14 +[NRCC] 15:59:15 -[NRCC] 15:59:17 +[NRCC] 15:59:29 +Leora_Morgenstern 15:59:31 Paula, did n't you post regrets? I changed the agenda because of that! 15:59:39 zakim, NRCC is me 15:59:40 +Harold; got it 15:59:51 IgorMozetic has joined #rif 15:59:52 Hi ... is anyone on the phone? 15:59:58 josb has joined #rif 16:00:02 I am 16:00:09 But last I checked I was all alone 16:00:12 zakim, mute me 16:00:12 bijan should now be muted 16:00:20 I'm online for the first part of the telecon...but on the call 16:00:30 +Sandro 16:00:35 +??P36 16:00:41 but NOT on the call...sorry 16:00:52 DaveReynolds has joined #rif 16:01:05 zakim, ??P36 is me 16:01:05 +csma; got it 16:01:15 zakim, who is the phone? 16:01:15 I don't understand your question, csma. 16:01:17 +??P42 16:01:25 zakim, ??P42 is me 16:01:25 +IgorMozetic; got it 16:01:32 zakim, who is on the phone? 16:01:32 On the phone I see bijan (muted), Harold, Leora_Morgenstern, Sandro, csma, IgorMozetic 16:01:34 +josb 16:01:44 zakim, mute me 16:01:44 IgorMozetic should now be muted 16:01:53 zakim, agenda? 16:01:53 I see 9 items remaining on the agenda: 16:01:57 1. Admin [from csma] 16:02:05 2. Liaisons [from csma] 16:02:12 3. F2F9 [from csma] 16:02:12 scribenick: Leora_Morgenstern 16:02:21 I didn't know that the wireless connection will be ok here, we are on a small island for our annual project meeting 16:02:22 4. OWL compatibility [from csma] 16:02:26 5. Issue 41 (membership) [from csma] 16:02:32 6. Issue 43 (classification) [from csma] 16:02:38 7. Issue 44 (named arguments uniterm) [from csma] 16:02:42 8. Issue 45 (lists) [from csma] 16:02:50 9. AOB (pick scribe for next time!) [from csma] 16:02:56 +[IBM] 16:03:01 ChrisW has joined #rif 16:03:04 + +1.919.541.aaaa 16:03:04 zakim, next item 16:03:10 +Dave_Reynolds (was Guest P46 74394) 16:03:16 +Dave_Reynolds 16:03:26 agendum 1. "Admin" taken up [from csma] 16:03:49 Hassan has joined #rif 16:03:52 Action review: 16:04:22 +Hassan_Ait-Kaci 16:04:55 LeoraMorgenstern has joined #rif 16:05:00 action-383 done 16:05:39 PROPOSED: Accept minutes of telecon of 11-20-07 16:05:51 RESOLVED: Accept minutes of telecon of 11-20-07 16:06:10 PROPOSED: Accept minutes of F2F8 16:06:35 Actually, that should be in 3 parts (first day, second day, breakout sessions) 16:06:47 RESOLVED: Accept minutes of F2F8 16:06:47 I can't access the WG web pages - "Forbidden due to abuse" 16:07:08 Christian: Discussing responses to public comments 16:07:37 http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0073.html 16:07:55 csma: There was one question about negation and disjunction on public comment list 16:08:05 http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0065.html 16:08:06 +Gary_Hallmark 16:08:11 JeffP has joined #rif 16:08:30 cmsa: Axel proposed a reply; if there's no objection, I propose we send Axel's reply. 16:09:53 +JeffP 16:09:53 csma: Can Axel send the reply? 16:10:09 csma: Sandro: yes, as long as others have read it and are comfortable with it 16:10:24 s/csma:Sandro/Sandro/ 16:10:37 csma: I have read it, and I'm comfortable 16:10:52 +1 for Axel's reply 16:11:28 csma: Also, Peter Palel-Schneider had some comments regarding BLD on the public list 16:11:53 csma: Three actions on Michael relative to this comment 16:11:55 http://www.w3.org/2005/rules/wg/wiki/Response_to_PPS1 16:12:04 josb: Michael not here; we need to defer the discussion 16:12:09 zakim, next item 16:12:09 agendum 2. "Liaisons" taken up [from csma] 16:12:25 No news on liaisons 16:12:29 zakim, next item 16:12:29 agendum 2 was just opened, LeoraMorgenstern 16:12:41 zakim, next item 16:12:41 agendum 2 was just opened, LeoraMorgenstern 16:12:48 zakim, close agendum 2 16:12:48 agendum 2, Liaisons, closed 16:12:49 I see 6 items remaining on the agenda; the next one is 16:12:51 3. F2F9 [from csma] 16:12:54 http://www.w3.org/2002/09/wbs/38457/f2f9dates/results 16:13:05 zakim, unmute me 16:13:05 IgorMozetic should no longer be muted 16:13:16 csma: Very few people have responded to Sandro's questionnaire. 16:13:24 csma: Action 380, on me, has been done 16:13:43 csma: Actions on Igor and Axel with regard to posting date preferences for F2F9 16:13:58 csma: Action 379 on Igor has been done too. 16:14:32 csma: Problem with dates: can only be in the last 2 weeks in February; moreover, Harold can only make the last week in February. 16:14:38 http://www.w3.org/2002/09/wbs/38457/f2f9dates/results 16:15:02 http://www.doodle.ch/participation.html?pollId=s25uzg9n378hney6 16:16:21 csma: Michael can't make the 26th; Chris can't make the 28th; Dave and Harold can't make the previous week. 16:17:17 csma: Perhaps we need to move F2F9 to March or January? 16:17:25 chris: Seems so. 16:17:48 Sandro: Too late for January. We can try for March; it may turn out to be worse. 16:18:02 csma: And March is very late relative to the end of the WG 16:19:19 harold: I could do February 20-22 16:19:26 igor: I can't make it those days. 16:20:15 dave: I can't make it those days either. 16:21:25 dave: But I could attend by phone. 16:21:57 +1 16:22:06 csma: There seems to be a consensus to have F2F9 on February 21-22, either in Galway or Paris. 16:22:25 +1 for Paris :) 16:22:43 -Gary_Hallmark 16:22:55 +1 for Paris (sorry Axel :) ) 16:23:05 +Gary_Hallmark 16:23:28 zakim, mute me 16:23:28 IgorMozetic should now be muted 16:23:29 csma: Let's have the meeting in Paris. 16:23:33 zakim, next item 16:23:33 agendum 3. "F2F9" taken up [from csma] 16:23:55 zakim, close item 3 16:23:55 agendum 3, F2F9, closed 16:23:56 I see 5 items remaining on the agenda; the next one is 16:23:58 4. OWL compatibility [from csma] 16:24:00 zakim, next item 16:24:00 agendum 4. "OWL compatibility" taken up [from csma] 16:24:30 Back to liaison: 16:25:21 sandro: There's supposed to be a formal announcement from W3C on the extension of the Working Group. 16:25:44 sandro: Which would one hope, bodes well, but we don't know, and we have to wait. 16:25:56 Back to OWL compatibility: 16:26:06 markproctor has joined #rif 16:26:16 csma: Checking for actions ... no actions 16:26:22 http://www.w3.org/2005/rules/wg/wiki/SWC/OWL-Compatibility 16:26:28 markproctor has joined #rif 16:27:02 josb: I've drafted several issues. There are several decisions that have to be made to enforce compatibility with OWL. 16:27:21 josb: Similar issues as arose with ensuring compatibility with RDF. 16:27:25 +Mark_Proctor 16:28:02 josb: First issue : the different versions of OWL. 16:28:39 josb: If we specify compatibility wiht OWL-DL, we automatically have compatibility with OWL-Lite, but not with OWL-Full, which has a different semantics. 16:29:00 josb: So we have to specify which version we're compatible with. 16:29:30 josb: If we just decide to go with OWL-DL, we can just ignore all the issues that arise from OWL-Full 16:29:56 josb: Syntax of OWL-Full and RDf are exactly the same. 16:30:19 josb: In case of OWL-DL, syntax is not the same. Abstract syntax specification is quite different from RDF. 16:30:20 GaryHallmark has joined #rif 16:31:18 josb: But there is an RDF representation of abstracft syntax of OWL-DL. 16:31:41 +Sandro.a 16:31:48 -Sandro 16:32:07 I wonder how the fact of a new version of owl affects this deliverable 16:32:15 josb: 16:32:16 Zakim, who is on the call? 16:32:18 I'll note that OWL DL is a fairly significant fragment of OWL Full, so workign with OWL DL gets *some* Full joy 16:32:19 On the phone I see bijan (muted), Harold, Leora_Morgenstern, csma, IgorMozetic (muted), +39.047.1.aaaa, +1.919.541.aaaa, [IBM], Dave_Reynolds, Hassan_Ait-Kaci (muted), +012242aabb, 16:32:24 ... Gary_Hallmark, Mark_Proctor, Sandro 16:33:54 josb: that's as far as syntactic compatibility. 16:34:14 josb: Semantic compability is a thornier issue. 16:34:19 Both semantics are normative 16:34:29 Maybe the OWL Full species is not a main issue for RIF compatibility with a new version of OWL (based on OWL 1.1): http://www.webont.org/owl/1.1/tractable.html#8 16:34:45 josb: Various issues have to be faced, whether we go for compatibility with OWL-Full or Owl-DL. 16:34:45 -Sandro 16:34:54 q+ 16:35:21 +Sandro 16:35:27 josb: Decision has to be made to go for straightforward correspondence of models 16:36:00 q? 16:36:02 josb: or as results obtained from questioning an external oracle. 16:36:08 zakim, unmute me 16:36:08 IgorMozetic should no longer be muted 16:36:52 ack chrisw 16:37:02 csma: If we go with the second option (external oracle), do we get a pass on the syntactic compatibility issues? 16:37:11 josb: No -- still must deal with them 16:37:31 chris: several people on the irc have brought up the point that there will be a new version of OWL. 16:37:52 zakim, unmute me 16:37:52 bijan should no longer be muted 16:37:58 q+ to talk about owl 1.1 16:38:03 chris: Perhaps we should have some liaison with the OWL group to come up with compatiblity with new standard. 16:38:20 ack bijan 16:38:20 bijan, you wanted to talk about owl 1.1 16:38:27 chris: better than just picking one of the old versions and ensuring compatibility with that old version. 16:39:06 bijan: Current status quo of OWL-DL 1.1 very advanced, but this is not ture of OWL-Full. 16:39:19 s/not ture/not true/ 16:39:33 zakim, mute me 16:39:34 csma should now be muted 16:39:39 q+ 16:39:46 zakim, unmute me 16:39:46 csma should no longer be muted 16:39:52 bijan: There's a possiblitiy that eventually there will just be one OWL --- some of OWL-Full will be dropped. 16:40:44 bijan: In terms of implementations: various implementations of OWL-DL, but implementations of OWL-Full seem to rely on a patchwork of various things, SWRL, RDF, etc. 16:40:48 ack josb 16:40:53 zakim, mute me 16:40:53 bijan should now be muted 16:41:26 I wouldn't mind transfering the owl compatibility to the OWLWG 16:41:43 josb: Regarding OWL 1.1 --- Scenario Chris sketched of collaboration between OWL and RIF won't work, because if we're lucky enough to get an extension, it will only be for 6 months. 16:42:17 josb: We shouldn't build anything into the language that make compatibility with further extensions impossible. 16:42:25 josb: But that may be as far as we should go. 16:42:26 +1 to a lightest possible compatibility document! 16:42:50 There is also an OWLED TF on rule integration 16:42:51 josb: That is, we should aim for the lightest possible compatibility document. 16:43:11 q? 16:43:35 q+ 16:43:39 josb: We can make it very light by saying we extend RDF compatibility to OWL-DL and OWL-Full. 16:44:11 josb: But that's not the lightest possible for the reader, who is more used to reading about a direct model-theoretic compatibility. 16:44:44 (Reminds me of what Shaw said: If it's easy to write, it's usually hard to read, and vice versa.) 16:44:47 zakim, unmute me 16:44:47 bijan should no longer be muted 16:44:49 ack bijan 16:45:40 bijan: I would imagine that such a document wouldn't be picked up a whole lot by the OWL reasoner community. So, realize it would probably be ignored by the OWL implementors' community. 16:46:04 bijan: If I just saw an extension of the RDF semantics, I would probably just ignore it. 16:46:15 csma: And after all, we're doing this document for the OWL community. 16:46:25 bijan: But I'm speaking for myself, not for the OWL community. 16:46:44 ack sandro 16:46:45 bijan: What I'm looking for from the RIF is an interoperable syntax. 16:46:55 zakim, mute me 16:46:55 bijan should now be muted 16:46:56 bijan: But if it came with a lot of baggage, I might ignore it. 16:47:29 q+ 16:47:38 ackm josb 16:47:40 sandro: Primary purpose of deliverable: There are users who want to use OWL and want to use rules, and they want to know how to use both together. E.g., Christine Golbreich. We need an answer for such people. 16:47:44 Perhaps we should interpret 'lightest' in the sense of the OWL species -- starting with OWL Lite and moving up to OWL DL (as used in SWRL), but postponing OWL Full to Phase 2? 16:47:46 ack josb 16:47:55 sandro: May mean paying more attention to SWRL than we have recently. 16:47:55 There are several editors that generate SWRL syntax 16:48:06 csma: Like making sure that SWRL is covered by BLD, 16:48:20 sandro: I think SWRL can be covered by a small extension to Core. 16:48:32 OWL Full more relevant to us than OWL DL in that our OWL work tends to be of the RDFS++ style that Bijan outlined 16:48:43 All reasoning implemetnations I know of interpret it as DL safe...with a few translation approaches in the offing (i.e., a prototype translation to FOL, and some translation to OWL 1.1 TBox axioms) 16:49:33 josb: I agree with both Bijan and Sandro. Our goal shouldn't be to make the lightest possible document, but to make this easy for people ---those who want to use OWL and rules --- to use. 16:49:41 (All, nigh compelte OWL DL + SWRL rules implementations, i.e., Racer, KAON2, and Pellet.) 16:49:55 josb: maybe have 2 documents, one for OWL-DL, and one for OWL-full 16:51:12 csma: And for OWL-Full, just extend RDF compatibility? 16:51:12 josb: Yes. 16:51:26 sandro: If BLD doesn't depend on OWL compatibility, then we have more time to work on OWL compatibility, and therefore we may hae the time to hook up with the OWL community. 16:51:50 sandro has joined #rif 16:52:08 I'm biased to something that supports existing and likely near-term implementations. It helps scope the problem; it provides immediate support to users; it's more or less testable 16:52:15 -Sandro 16:52:28 sandro: If it's the case that we have to ensure these different types of compatibility 16:52:29 q+ 16:52:40 ack josb 16:52:41 sandro: 16:52:57 For example, I'm interested in supporting hex predicates in Pellet, but that's several years off. 16:52:58 +Sandro 16:52:59 csma: Should we talk to the OWL WG? 16:53:42 The OWLWG will *know* in the next 6-9 months :) 16:53:53 sandro: Maybe we can ask the OWL WG to ask us whether we should do the two types of compatibiltity separately or work on some sort of merged version 16:54:12 chris: Yes, can't ignore the fact that OWL is changing. 16:54:18 chris: We have an opportunity to do a nice job with integration with these two different things. 16:54:43 csma: Especially, since although BLD will be final(ized) in May, there will be more time until the final recommendation. 16:54:49 q+ 16:54:58 zakim, unmute me 16:54:58 bijan should no longer be muted 16:55:01 ack bijan 16:55:07 s/the final recommendation/ it is a recommendation 16:55:22 s/final(ized)/last call/ 16:55:35 bijan: OWL task force just got a surge of interest; possible we might be interested in getting people to work, review, support this effort. 16:56:00 bijan: Peter is coming to Manchester before , Boris ??? is coming; can get lots of stuff going. 16:56:21 zakim, mute me 16:56:21 bijan should now be muted 16:56:35 zakim, unmute me 16:56:35 bijan should no longer be muted 16:56:36 q+ 16:57:01 josb: It seems like we'd have to wait for the recommendation for OWL 1.1 16:57:20 chris: No, I'm talking about jointly making a recommendation for OWL and BLD. 16:57:23 q+ 16:57:35 chris: Having a joint task force could influence the evolvement of these two. 16:58:25 chris: I specifically don't want to be in the situation where subgroup of OWL tells us what to do, or vice versa. 16:58:30 ack bijan 16:58:46 chris: who will be on this task force from RIF? 16:59:31 bijan: Lot of start-up overhead at the moment. No significan push possible until after the holidays/first f2f for owl 1.1. 17:00:12 ack hassan 17:00:14 My survey: http://spreadsheets.google.com/pub?key=pTmcCXR-dV6TdDo24Tse-fQ 17:00:23 bijan: had 94 people at last owl get together (get exact name), but based on polling, many fewer people willing to actually work on this, because what they have works well enough. 17:00:27 zakim, mute me 17:00:27 bijan should now be muted 17:00:28 q? 17:01:14 hassan: I agree with what most of what's been said, but there's a bit of a chicken-and-egg argument here. OWL 1.1 isn't going to be that different fromcurrent OWL, so we can start looking at likely interesection between current OWL and OWL 1.1 17:01:17 s/owl get together (get exact name)/owled/ 17:01:28 me 17:01:32 me 17:01:36 me 17:02:08 I've seen task forces with members disjointly from each wg 17:02:09 csma: how does it work? Does a member of such a task force have to be a member of both WGs? 17:02:12 I'd like visibility at least since my concerns are different from the DL rule cluster 17:02:14 That's the norm 17:02:24 zakim, unmute me 17:02:24 bijan should no longer be muted 17:02:25 sandro: I'd assume it's enough to be a member of one WG. 17:03:15 zakim, mute me 17:03:15 bijan should now be muted 17:03:46 at most 4 people? 2 from each WG? 17:03:53 17:04:23 Chris: Shouldn't be too big. 17:04:29 Is the goal to produce a document? 17:05:11 ACTION on Chris to talk to OWL Working Group Chairs, Alan and Ian 17:05:14 I'd say, yes 17:05:27 I suppose so Bijan (re: producing a document) - how else can it be? 17:05:28 Chris: will report next week 17:05:29 q? 17:05:55 q+ 17:06:02 ack josb 17:06:39 josb: In this case, Current RDF and OWL compatibility document would just be a RDF compatibility document. 17:06:56 ok, bye 17:07:03 -Sandro 17:07:03 csma: In which case, this document is almost finished. (But we do have to note the change in document somewhere.) 17:07:10 -[IBM] 17:07:13 csma: Action review 17:07:26 ACTION 389 on Paula has been done. 17:07:28 +Sandro 17:08:11 ACTION 382 on Sandro to report any critical -path ssues related to extensibility --- continued until next week. 17:08:32 s/continued until/due/ 17:09:12 ACTION 372,373,375,382 on Sandro -- also due next week 17:10:03 - +39.047.1.aaaa 17:10:20 ACTION 349 on Dave to write up a use case for membership formulae -- done 17:10:30 http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0077.html 17:10:56 +josb.a 17:11:31 -bijan 17:12:27 ?item[oftype -> eg:HardwareType^^rif:iri] 17:12:55 or oftype(?item, eg:HardwareType^^rif:iri) 17:14:05 +1 this is indeed not a use case for the membership formulas 17:15:48 s/interesection/intersection/ 17:17:12 17:17:17 q? 17:18:38 q+ 17:18:55 q- 17:19:32 -Sandro 17:19:36 Dave: Axel's use case is neutral: doesn't argue for having a RIF member-of 17:19:50 csma: because could equally well use type-of 17:19:58 q+ 17:20:07 ack josb 17:20:12 +Sandro 17:20:14 csma: so, we still don't have a use case arguing for a single member-of function. 17:20:46 csma: that is use case for having one single way for representing different types of membership. 17:21:05 s/member-of function/membership formula/ 17:21:31 harold: we have to view this in conjunction with classification as well. 17:21:55 harold: look at slotted extensions, which have membership and classification. 17:22:09 q+ 17:22:16 ack igor 17:22:22 csma: we don't have use cases for classification formulae. 17:22:54 igor: are we making the same mistake as we did in Core? Should we leave all these elements in BLD, and then define various profiles = subsets? 17:22:56 q+ 17:23:08 igor: easier to define various profiles than to define extensions. 17:23:22 csma: But the question is: does anyone need these even in BLD? 17:23:30 igor: Seems like a basic construct. 17:23:54 csma: But not in rules languages. The question is --- where in rules do you need to assert or test something about classiciation? 17:24:11 q- 17:24:25 igor: to me, seems like a nice bridge between rules languages and DL languages. 17:24:36 In a way, Igor is saying that rules and data models are independent - and I agree : they are orthogonal 17:25:04 I haven't thought about this too much ... 17:25:12 but I could imagine this coming up when doing marketing 17:25:28 q+ 17:25:34 When developing new banking products, e.g, 17:25:39 ack josb 17:25:48 one would want to see if it can be classified in various ways ... 17:26:10 e.g., finding out if there is something that can be considered both a savings product 17:26:11 in Objects forward chaining engines tend to match against a hierarchy. So if someone does Collection() it'll match List, ArrayList, LinkedList etc. but thats as far as I know it goes. 17:26:16 and an investment vehicle 17:26:21 q+ 17:27:27 q- 17:27:38 zakim, who is talking? 17:27:46 Ignore what I just wrote. 17:27:50 JeffP, listening for 10 seconds I could not identify any sounds 17:27:56 Mark Proctor 17:28:03 MarkProctor: It seems one would need to check membership rather than classification 17:28:05 (to jeff) 17:28:06 thx, csma 17:28:06 q? 17:29:29 :) 17:29:37 q+ 17:29:56 sandro: Michael feels checking classification is necessary; should convince csma 17:30:25 ack hassan 17:30:29 q+ 17:30:47 hassan: no difference, conceptually. 17:31:03 in RIF, there is a difference 17:31:03 hassan: can do with only classification, which is more general. 17:31:12 (in OWL there is not) 17:31:17 hassan: membership is equivalent to singleton being a subclass. 17:31:25 ack leora 17:32:25 Hassan, because we are intensional here, a # S could be reduced to Nominal(a) ## S. 17:33:02 :-) 17:33:10 +1 17:33:11 I don't think you would want to say match X if its a subclass of Y. as that information is implicit in your model. 17:33:13 +1 17:33:16 +1 17:33:23 -Harold 17:33:25 bye 17:33:26 -Gary_Hallmark 17:33:27 -josb.a 17:33:28 - +012242aabb 17:33:29 -Hassan_Ait-Kaci 17:33:30 -Darko_A 17:33:31 -Mark_Proctor 17:33:33 -Dave_Reynolds 17:33:40 -IgorMozetic 17:33:40 zakim, who is on the phone 17:33:41 I don't understand 'who is on the phone', csma 17:33:41 -josb 17:34:03 zakim, zho is on the phone? 17:34:03 I don't understand your question, csma. 17:34:17 rrsagent ;ake record public 17:34:30 rrsagent, make record public 17:35:00 rrsagent, make minutes 17:35:00 I have made the request to generate http://www.w3.org/2007/11/27-rif-minutes.html csma 17:36:27 scribenick: LeoraMorgentstern 17:36:55 scribenick: LeoraMorgenstern 17:37:10 rrsagent, make minutes 17:37:10 I have made the request to generate http://www.w3.org/2007/11/27-rif-minutes.html csma 17:38:04 -Leora_Morgenstern 17:39:03 -Sandro 17:39:05 -csma 17:39:06 SW_RIF()11:00AM has ended 17:39:07 Attendees were bijan, Leora_Morgenstern, Harold, Sandro, csma, IgorMozetic, josb, [IBM], +1.919.541.aaaa, Dave_Reynolds, Hassan_Ait-Kaci, Gary_Hallmark, JeffP, Mark_Proctor 17:44:26 csma has left #rif 18:08:20 sandro has joined #rif