See also: IRC log
csma: PRR rechartered
chrisw: pls check over Chris' responses to public comments
harold: seeks feedback on adding common logic references
Chrisw: common logic community
doesn't care so much for BLD
... not politics, just "scientific" disagreement
csma: is it possible to map BLD to CL?
chrisw: we welcome help from CL community to do so
dates for F2F12 in Portland, OR, US: Jan 8,9 or Jan 15,16 2009 (both Thurs, Fri)
(other dates possible - at the moment only Tuesdays are bad)
<sandro> Then please include Wednesdays, Gary....
<sandro> and give at least one more week, I think.
<sandro> ChrisW, I've fixed the various formal scribe problems in Day 2, so the minutes are pretty, even if they might still be wrong, etc.
ok, I'll need to pencil those in first -- will send email later today
Axel: only strict safety need be defined
harold: weak safety now obsolete
axel: weak safety has some advantages, but harder to specify, so we drop it
hassan: XML<->PS translator work on hold now
harold: current translator uses old XML syntax
hassan: will update to latest pending agreement on some emailed issues
<Harold> The BLD LC PS frontend of Hassan's current tool is fine.
<Harold> The backend still is pre-LC.
<Harold> <side> is still wrongly used instead of <left>, <right>.
<sandro> Yes, of course we CAN do keyword-by-keyword improvements. Iterative design works damn well.
hassan: hopes to do new release by week's end
csma: all please email hassan with any issues
<Harold> Stella already translated http://www.w3.org/2005/rules/wiki/Factorial_Functional
<Hassan> Sandro: my point was not against iterative design (thanks for explaining though!) - it was about distracting the implementation effort from focusing on importing decisions
chrisw: recaps F2F11
... accepted many test cases
... delay next UCR WD
... add usage for rdf:text for i18n
... drop roundtripping paragraph
... metadata should be preserved where possible
... no formal definition of profiles
... all RIF dialects SHOULD extend Core
<sandro> csma: quoting RFC-2119: 3. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
chrisw: external data model
discussion led to some actions to propose a strawman
... discuss semantics of PRD conditions - should simplify by using more from the semantic structure
... external frames - increased understanding but didn't change anything
... agreed on equality in condition in Core, other Core issues
... discussed possible External(ATOMIC)
chrisw: parallel sessions for PRD and FLD
csma: recaps PRD breakout - no-repeat for conflict resolution
<ChanghaiKe> I have added: conflict resolution strategy could be additional XML tags, along with the rules. There can be several strategies like RETE, sequential, etc.
csma: agreed on overall semantic
framework but the details seem to vary by engine
... but at least we can start to attack the details
Changhai: we need syntax to specify the conflict resolution
ChrisW: recaps FLD breakout
... add modules
I seem to recall MK will add aggregates to FLD
ChrisW: bug fix with defn of
... negative guards permit entailment of disjunctive info
<csma> Gary: aggregates are something we agreed we would take some times to discuss during F2F11, but we could not find the time
ChrisW: will be more discussion
about negative guards
... addressed some DTB editors notes
csma: PRD breakout on
... 3 proposals for Do (?var), New, Retract/Remove/Erase object
... doc plans
... PRD, DTB, BLD, FLD - frozen in 1 month
... need DTB to LC before BLD to CR
for more detail on F2F11, please see minutes - available now