F2F4
Outcomes
Resolutions passed by the WG:
- The RIF CORE will be positve Horn.
- RIF Core will be based on current model theory with suitable extensions
- RIF core must have a clear and precise syntax and semantics. Each standard RIF dialect must have a clear and precise syntax and semantics that extends RIF core.
- For standard RIF dialects, model theories will be normative; in their absence it will be proof theories; in the absence of both it will be operational semantics.
- The RIFWG will define useful RIF dialects in Phase 1, e.g. including negation, not necessarily in a Rec
- new requirements:
- RIF should support the ability to merge rule sets
- RIF will support the identification of rule sets
- RIF will use URIs as in RDF (see below)
- RIF will provide a framework for defining RIF dialects
- RIF must have a standard core and a limited number of standard dialects based upon that core
- The implementability, semantic precision, standard components, and translator requirements will be treated as "general" (ie not specific to use cases)
- RIF will use URIs (IRIs) in the style of RDF and OWL, using them to identify at least: globally named predicates, functions, datatypes, constants (OWL individuals, not literal values), rules, and rulesets.
- Translators to and from languages which do not use URIs as names will need to use a name-mapping system (such as namespace prefixes)
- RIF does not mandate any particular mapping scheme. It will provide a metadata vocabulary to allow translators to record the mapping if they choose to.
- For example, in rule systems where the predicates refer to fields of java objects the metadata annotations might be used to carry the java fully-qualified classname and field name.
- For RIF these are purely annotations, any use of them for carrying semantic information steps outside of RIF.
Minutes
Day 1: http://www.w3.org/2005/rules/wg/meetings/f2f4/4-all.html
Day 2: http://www.w3.org/2005/rules/wg/meetings/f2f4/5-all.html
Logistical Overview
4-5 November 2006, just before ISWC 2006. 9am - 6pm.
Athens Classic Center, Cypress Ballroom 1 and 2, in the "old building" on Foundry Street email
Agenda
Objectives
- Prepare 3rd WD of UCR
- Complete the analysis of the UC
- Complete the reqs for phase 1
- Roadmap towards 1st WD of Technical Spec
- Agree on minimum requirements (on content) to consider publication (have Editor's draft done)
- Draft and agree on (or, at least, agree on and set up process and schedule to draft and agree on) said minimum content.
- Progress on RIFRAF
- 1st version of OWL ontology of RIFRAF
Saturday, November 4
(actual agenda, edited after meeting)
9-10 |
Review requirements |
||
10-10:30 |
Break |
||
10:30-11:30 |
Tech spec - review and discuss different proposals |
||
11:30-12 |
Use Cases & RIF-RAF |
||
12-1 |
Lunch |
||
1-2:30 |
UCR |
Tech Design (partial/complete semantics) |
Tech Design (Syntax Issues/URIs) |
2:30 |
Debrief break-out sessions |
||
3-3:30 |
Break |
||
3:30-5:00 |
UCR |
Tech Design (semantics) |
Tech Design (syntax) |
5-6 |
Debrief break-out sessions |
Sunday, November 5
(actual agenda, edited after meeting)
9-10:30 |
Debrief break-out sessions (continued from Nov4) |
||
10:30-11 |
Break |
||
11-11:45 |
Debrief break-out sessions (continued) |
||
11:45-12:30 |
RIFRAF |
Tech Spec (drafting semantics) |
Tech Design (extensibility) |
12:30-1:30 |
Lunch |
||
1:30-2:30 |
RIFRAF |
Tech Spec (drafting semantics) |
Tech Design (extensibility) |
2:30-3:30 |
Wrap-up break-out sessions |
||
3:30-4:00 |
Break |
||
4-5:00 |
Wrap-up break-out sessions (continued) |
||
5:00-5:30 |
Wrap-up meeting |
||
5:30-6:00 |
Introduction to Jacc (Hassan) |
Work Items
UCR
- Propose a final version of the text for each of the UC, including requirements analysis
- Propose text for section on RIF benefits
- Propose text for section on RIF processing models
- Propose a final list of the phase 1 requirements coming from the UC as well as of the non-functional requirements, including requirement labelling (UCx, charter, non-fctl) and extended text for each requirement
Tech Spec
This is just some rough ideas...
- Propose solution to interchange of identifiers (mapping to/from URI, curies, ...)
- Analyse approaches to RDF triple mapping
- Datatypes and Operators
RIFRAF
- Propose an OWL representation which helps us understand and prioritize requirements for RIF features
- Propose a plan for finalizing the OWL version, translating and processing the completed questionnaires
- Propose a plan for the 1st WD of the RIFRAF document
See RIFRAF in OWL, Survey, Survey Results
Venue
Athens, Georgia, at the Classic Center, about 1.3 miles away from the Georgia Center, the venue of ISWC 2006.
Hotels
There are many hotels available near the Classic Center, including a Holiday Inn, with current rates of $83 as of June 2006, and a Days Inn, with current rates of $57. Try "hotels near 300 N Thomas St, Athens, GA 30601" in Google Maps for a large list of hotels. No room block has been arranged as of yet.
The Georgia Center appears to be booked, so attendees may have to book into a hotel close to the Classic Center, although trying for the Georgia Center is probably a good idea. Attendees who are also attending ISWC 2006 could also stay at the Georgia Center, the site of ISWC 2006. When you register for ISWC you get to say which days you want to stay in the Georgia Center. You should also be able to extend your stay by contacting the Georgia Center directly.
Registration
There will be no sponsorship for the event. Registration fees will be on a cost recovery basis, which is $140 (including the cost of the registration service and taxes) for two days. Registration will include lunch and morning and afternoon breaks both days. Payment can be made by credit card to a local conference organizer, via fax or phone or mail. A registration form is available at attachment:RIF-F2F4.pdf. I believe that the most important thing to mention on the phone is the event number, 61885.
It has been reported that emailing a scanned form to register@georgiacenter.uga.edu will also work. This may or may not work - if you do this, ensure that everything is OK. If you are outside the U.S., then faxing to +1 706 542 6596 will also work.
Travel
Atlanta's Hartsfield airport is probably the most suitable. There are shuttle services available from there. See the travel directions for the Georgia Center for more information, at http://www.georgiacenter.uga.edu/conferences/about/directions.phtml#Shuttle. One such service is AAA Express, which runs a schedled servce, see http://www.aaaairportexpress.com/routes/athens.html.
Primary Contact
Proposals (old)
ISWC Colocation Proposal Nov. 4-5 in Athens, GA, USA
F2F4 MITRE Proposal Oct 5-6, or Oct. 16-17, or Nov 2-3 in McLean, VA (near Washington DC)