W3C home > Mailing lists > Public > public-rif-wg@w3.org > March 2009

[Admin] Agenda for RIF telecon March 10 [*ATTENTION* time of telecon]

From: Christian de Sainte Marie <csma@ilog.fr>
Date: Mon, 09 Mar 2009 18:55:08 +0100
Message-ID: <49B557FC.9080201@ilog.fr>
To: RIF WG <public-rif-wg@w3.org>
AGENDA Teleconference
W3C Rules Interchange Format (RIF) Working Group
10 March 2009

*ATTENTION* telecon is 1h *earlier* than usual in *Europe*!
North America is in the summer time and Europe is in the winter time:
1500 UTC, 0800 (West US) 1100 (East US) 1500 (London) 1600 (Paris)

Duration: *90 min* (max. Probably more like 45 mn)

*Agenda summary*
1. Admin (5 mn)
*PROPOSED:* accept minutes of telecon March 3 [1]
2. Liaison (5 mn)
3. F2F13 [2] (5 mn)
4. Action review [3] [4] (5 mn)
5. Safeness and termination (ACTION-702 [8]) [9] (5 mn)
*PROPOSED:* The issue of finiteness will be At Risk through CR, as we get implementor feedback. We need to know who wants / doesn't want this limitation in Core. (Safeness as defined by Jos [8] not being in question.)
6. ISSUE-80 [7] [15] (Should we extend DTB to include more general builtins?) (10 mn)
7. ISSUE-92 [6] [14] (N-ary builtins for strings) (20 mn)
8. Presentation syntax [11] (10mn)
9. ISSUE-93 [5] [11] (15 mn)
10. ACTION-689 [10] [12] [13] [16] (10 mn)
11. AOB

[1] 
[2] http://www.w3.org/2005/rules/wiki/F2F13
[3] http://www.w3.org/2005/rules/wg/track/actions/open
[4] http://www.w3.org/2005/rules/wg/track/actions/pendingreview
[5] http://www.w3.org/2005/rules/wg/track/issues/93
[6] http://www.w3.org/2005/rules/wg/track/issues/92
[7] http://www.w3.org/2005/rules/wg/track/issues/80
[8] http://www.w3.org/2005/rules/wiki/Core#Safeness
[9] http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0025.html
[10] http://www.w3.org/2005/rules/wg/track/actions/689
[11] http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0125.html
[12] http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0010.html
[13] http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0011.html
[14] http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0127.html
[15] http://lists.w3.org/Archives/Public/public-rif-wg/2009Feb/0128.html
[16] http://lists.w3.org/Archives/Public/public-rif-wg/2009Mar/0021.html

-------------------

*Detailed agenda*

Bridges: +1.617.761.6200 (US), +33 4 89 06 34 99 (F) or +44.117.370.6152
(GB)
Conference code: 74394# ('RIFWG')
IRC Chat: irc:irc.w3.org (port 6665), #rif
Web-based IRC (member-only): [http://www.w3.org/2001/01/cgi-irc]

*PLEASE POST REGRETS* TO [http://www.w3.org/2005/rules/wiki/TeleconRegrets]

Chair: Chris Welty
Scribe: Harold Boley (alternate: Leora Morgenstern)
See Scribes Ring [http://www.w3.org/2005/rules/wiki/ScribeRing]

Please note that RIF WG telecons are for attendance only by Working
Group Participants and guests invited by the chairs.

1. ADMIN (5 min)

- Roll call (please read before telecon the following)
RIF Regrets Policy:
[http://www.w3.org/2005/rules/wg/wiki/RegretsPolicy]
Using Zakim:
[http://www.w3.org/2005/rules/wg/wiki/UsingZakim]
Telecon Etiquette:
[http://www.w3.org/2005/rules/wg/wiki/TeleconEtiquette]
Action/Issues Tracker:
[http://www.w3.org/2005/rules/wg/track/]

- Agenda amendments

PROPOSED: accept minutes of telecon March 3 [1]

2. Liaison (5 min)

- Review active liaisons:
PRR (OMG) - Paul Vincent
OWL (W3C) - Sandro Hawke
HCLS (W3C IG) - Adrian Paschke

3. F2F13 (5 mn)

- F2F13 updates [2]

4. Action review (5 mn)

- Review actions due [3] and pending review [4]

5. Safeness and termination (5 mn)

*PROPOSED:* The issue of finiteness will be At Risk through CR, as we get implementor feedback. We need to know who wants / doesn't want this limitation in Core. (Safeness as defined by Jos [8] not being in question.)

6. ISSUE-80 [7] (Should we extend DTB to include more general builtins?) (10 mn)

- Pass a resolution if consensus (see Chris's summary, including proposed alternative resolutions [15] and following thread)

7. ISSUE-92 [6] (N-ary builtins for strings) (20 mn)

- Find consensus on a resolution.  The options currently under consideration seem to be  (see also Chris's summary, including proposed alternative resolutions [14] and following thread):
 1. Keep fixed arity for all predicates and functions and require explicit fixed arity in all RIF documents (but change the wording in DTB to make it clear);
 2. (here for completeness, since nobody seems to support that option) Keep fixed arity for all predicates and function, but allow for some pre-processing step in RIF implementations where functions like concat are replaced with their fixed-arity equivalents;
 3. Remove all wellformedness requirements: same symbol can have different arities, be a predicate, a function or an individual in different contexts;
 4. Remove only the well-formedness requirement on arity: symbols for predicates, functions and individual are kept separate, but function and predicate symbols can have different multiple arities;
 5. Drop the fixed-arity requirement for external function and predicate symbols only.

8. Presentation syntax (10mn)

- Debrief the PS TF telecon [11]

- Review issues

9. ISSUE-93 [5] (data type IRI mapping) (15 mn)

- Find consensus on a resolution (see also Chris's summary [11]

10. ACTION-689 [10] (Coreifying SWC) (10 mn)

- See Jos's emails wrt the difficulties [12] [13] [16]

10. AOB

- Next telecon: 17 March 2009
Received on Monday, 9 March 2009 17:55:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:03 GMT