Current events

From RIF

Jump to: navigation, search


[edit] Older events

  • Telecon 1 July 2008 Agenda Minutes
    • RESOLVED: Mark "External Frames" AT RISK in BLD.
    • RESOLVED: Change the tag name of the sub elements of Equal in BLD XML from side to left and right
  • Telecon 24 June 2008 Agenda Minutes
    • RESOLVED: BLD refers to DTB by version number. If/when dialects need other things, they refer to new versions. BLD still refers to old one.
  • Telecon 17 June 2008 Agenda Minutes
  • Telecon 10 June 2008 Agenda Minutes
    • RESOLVED: reword req. 5.2.8 to "RIF semantics"
    • RESOLVED: replace req. 5.2.9 with re-wording: "The semantics of a RIF document must be uniquely determined by the content of the document, without out-of-band data."
    • RESOLVED: change req. 5.2.12 to "must" support ability to merge rule sets
    • RESOLVED: change req. 5.2.13 "will" to "must" & remove parenthetical comment: RIF must support the identification of rule sets.
    • RESOLVED: Move 5.3.1 to 5.2.14 and make it a SHOULD instead of MUST. (support XML as data)
  • Telecon 3 June 2008 Agenda Minutes
    • RESOLVED: change text of 5.1.3 to: It must be possible to create new RIF dialects which extend existing dialects (thus providing backward compatibility) and are handled gracefully by systems which support existing dialects (thus providing forward compatibility).
    • RESOLVED: For this next draft of UCR, add an editor's note to 5.1.6 to note that we're still working on how to define a coverage requirement. (unless we come up with some consensus text before publication)
    • RESOLVED: rephrase 5.2.1 to: The RIF specifications must provide clear conformance criteria, defining what is or is not a conformant RIF implementation.
  • F2F10 26-28 May, 2008, Galway Minutes
    • RESOLVED: Publish BLD as last call!
    • RESOLVED: Publish SWC as last call!
    • RESOLVED: Publish DTB and PRD as FPWD
    • RESOLVED: Publish FLD as 2PWD
    • RESOLVED: Request a 1-year extension
    • ...over 40 resolutions passed
  • Telecon 20 May 2008 Agenda Minutes
  • Telecon 13 May 2008 Agenda Minutes
    • RESOLVED: to close ISSUE-52 per the current version of BLD and SWC drafts, with the understanding that ISSUE-33 and ISSUE-39, and the new issue to be raised about profile mixing, are moved out of BLD critical path as a consequence.
    • RESOLVED: (on Axel's point 4) go with Prefix as Axel proposes (whitespace between prefix name and uri), as long as in the presentation syntax it is in a pre-amble, as a directive, so it is not easily confused with a fact.
    • RESOLVED: Presentation Syntax will follow option 1a (where Const ::= ANGLEBRACKIRI | CURIE | STRING^^ANGLEBRACKIRI | STRING^^CURIE )
  • Telecon 6 May 2008 Agenda Minutes
  • Telecon 29 April 2008 Agenda Minutes
  • Telecon 22 April 2008 Agenda Minutes
    • RESOLVED: ISSUE-37 is not critical path for BLD.
    • RESOLVED: ISSUE-38 is not critical path for BLD.
    • RESOLVED: ISSUE-46 is not critical path for BLD.
    • RESOLVED: ISSUE-48 is not critical path for BLD.
  • Telecon 15 April 2008 Agenda Minutes
    • RESOLVED: That FLD be published as a FPWD with [three additional] Editor's Notes.
    • RESOLVED: That BLD be published as a WD with [three additional] Editor's Notes (same as FLD).
    • RESOLVED: Publish rif-rdf-owl (aka SWC) as WD.
    • RESOLVED: Close ISSUE-14. It is addressed in the RDF+OWL document
    • RESOLVED: Close ISSUE-15. It is addressed in the RDF+OWL document
    • RESOLVED: Close ISSUE-24. It is addressed in the RDF+OWL document. At the time the issue was opened, Core was BLD.
    • RESOLVED: Close ISSUE-16, it is addressed (as far as Phase 1) in FLD and BLD through the external call mechanism
    • RESOLVED: Postpone ISSUE-17, ISSUE-18, ISSUE-19 and ISSUE-20. They are not covered by Phase I of RIF.
    • RESOLVED: Close ISSUE-21 - unclear what it means and most likely subsumed by ISSUE-38.
    • RESOLVED: Remove ISSUE-26 from critical path (of BLD 1.0).
  • Telecon 8 April 2008 Agenda Minutes
    • RESOLVED: Repeal resolution regarding moving "RIF-BLD as a specialization of FLD" to appendix and keep that as last section before refs
  • Telecon 1 April 2008 Agenda Minutes
  • Telecon 25 March 2008 Agenda Minutes
    • RESOLVED: Use fully-striped syntax for next WD (option 3 from here)
  • Telecon 18 March 2008 Agenda Minutes
    • RESOLVED: Open an issue on terminology around terms/functions/predicates and include an editorial comment in WD2 asking for feedback, but keep "atom" and "expr" for this draft.
    • RESOLVED: remove nested Foralls for BLD WD2. Maybe we'll get some use case some day for putting them back in.
  • Telecon 11 March 2008 Agenda Minutes
    • RESOLVED: BLD builtins are not sensitive to order of evaluation (closing issue-40).
    • RESOLVED: Approve Michael's alternative proposal on lists and update FLD+BLD syntax/semantics accordingly to reflect that and the previous resolution on lists
  • Telecon 4 March 2008 Agenda Minutes
  • F2F9 21-22 Feb, 2008, Paris Agenda Minutes
    • RESOLVED: Create a new Document with provisional title "Data Types and Builtins" to contain elements common to all dialects with Harold and Axel as editors.
    • RESOLVED (REPEALED on 8 Apr): make "specialization of FLD" sections (of BLD) appendices, leaving standalone sections in place, and making both standalone and specialization normative.
    • RESOLVED: make argument names distinct.
    • RESOLVED: We keep named arguments, explaining in BLD that: A RIF consumer that does not support named arguments can implement them, with relative ease, by treating them as positional arguments (of a different predicate, formed in a stable but implementation-dependent way) in the lexical order of the argument names. (Closing ISSUE-44).
    • RESOLVED: No reification in BLD. This is like WD1, except no nested frames. A change from 18-Feb draft: Equality, frames, subclass, membership are no longer terms.
    • RESOLVED: (Approach 3) Functions on error return an error element that is in the domain. BLD Spec does not require that predicates return F on error, just that they have a truth value. BLD spec recommends using guards with builtins, to give predictability. Without guards, rules may behave unpredictability on error.
  • Telecon 19 February 2008 Agenda Minutes
  • Telecon 12 February 2008 Agenda Minutes
    • RESOLVED: Fixed interpretation functions will be represented as functions and fixed interpretation relations as predicates, rather than representing functions as predicates.
  • Telecon 5 February 2008 Agenda Minutes
  • Telecon 29 January 2008 Agenda Minutes
    • RESOLVED: to close issue 36 without action (that is, direct mapping between presentation and XML syntaxes, e.g. presented as a table).
  • Telecon 22 January 2008 Agenda Minutes
    • RESOLVED: close issue 45 by including lists in BLD as sequences for both presentation and XML syntaxes.
  • Telecon 15 January 2008 Agenda Minutes
    • RESOLVED: to close issue 47 without action (i.e. equality stays in BLD as it is currently specified)
  • Telecon 8 January 2008 Agenda Minutes
    • RESOLVED: Close Issue-43 by including in BLD subclass formulae of the form a ## b. In the RDF compatibility document, ## and rdfs:subClassOf will be connected appropriately, i.e. whenever a ## b holds, a rdfs:subClassOf b is required to hold.
    • RESOLVED: Close Issue-41 by including in BLD membership formulae of the form c # a. In the RDF compatibility document, # and rdf:type will be connected appropriately, i.e. a # b holds iff a rdf:type b holds.
  • Telecon 18 December 2007 Agenda Minutes
  • Telecon 11 December 2007 Agenda Minutes
    • RESOLVED: Go with Axel's option C, that is using a special syntax to distinguish evaluated functions/predicates from logical functions/predicates
  • Telecon 4 December 2007 Agenda Minutes
    • RESOLVED: Close Issue 42 such that the relationship between the xml syntax treatment of constants and the presentation treatment of constants is specified in the syntax mapping table
  • Telecon 27 November 2007 Agenda Minutes
  • Telecon 20 November 2007 Agenda Minutes
    • RESOLVED: close ISSUE-2 based on Jos' analysis
    • RESOLVED: We'll refer to XSD 1.0 instead of XSD 1.1 in our document for now, including a clear note that it our intention to change to XSD 1.1 when it becomes available, so that people can use XML 1.1.
  • Telecon 13 November 2007 Agenda Minutes
  • F2F8: Nov. 5-6, Boston, MA F2F8 Minutes day1 Minutes day2 Minutes PRD breakout session
    • RESOLVED: All official (ie standard) dialects will use the main RIF namespace. We will support user extensions using other namespaces.
    • RESOLVED: WG asks for 6 months extension. Plans to get BLD to Last Call and hold 2 more F2F meetings by end of May.
    • RESOLVED: Core will be what is currently called BLD with Equality removed, function terms removed, and perhaps safeness, and perhaps slotted terms. We will not get rid of BLD. (Ignoring editorial issues for now) Frames stay in core.
    • RESOLVED: CLOSE ISSUE 25. Addressed by SWC document.
    • RESOLVED: close ISSUE-27 with the understanding that neither RIF Core nor RIF BLD will have constraint logic programming.
    • RESOLVED: close ISSUE-28 with the understanding that RIF Core (as defined earlier today) does not have the problems which caused us to raise this issue.
    • RESOLVED: to close ISSUE-35 with the understanding that this issue is settled in our latest published version of BLD.
    • RESOLVED: no invisible extensions (official or user extensions)
    • RESOLVED: Be nice to Michael until mid-december
  • F2F7 27-28 September 2007, Hawthorne, NY, USA
  • F2F6 2-3 June, 2007, Innsbruck, Austria
  • F2F5 26-28 February, 2007, McLean, Virginia, USA
  • F2F4 4-5 November 2006, Athens, Georgia, USA
  • F2F3 8-9 June 2006, Budva, Montenegro
  • F2F2 27-28 February 2006, Cannes-Mandelieu, France
  • F2F1 8-9 December 2005, Burlingame, California, USA
Retrieved from "http://www.w3.org/2005/rules/wiki/Current_events"
Personal tools