03 Feb 2009

See also: IRC log





changhai, on attend un peu que Zakim redemarre...

ok, on peut appeler, alors

<apaschke> I cannot attend since I have a lecture on Wednesday

<apaschke> afternoon


PROPOSED: Close ISSUE-63 with the understanding that the Group construct is sufficient


Paul, is there a HALT action in Blaze, that terminates an execution?

And in your engine?

<apaschke> this issue also relates to finiteness as we discussed it today

<apaschke> we said that it might be handeled by the conformance clause

<PaulVincent> Sorry I'm not on the call yet - Blaze has a "return" which terminates ruleset execution

<PaulVincent> In TIBCO: we never halt :)

<PaulVincent> ... instead we'd have to set a "terminate flag" or somesuch for that particular ruleset

PROPOSED: Close ISSUE-65 with the understanding that there is only one halting test in PRD, and no syntax to specify other ones at this stage.
... Close ISSUE-65 with the understanding that there is only one halting test in PRD.
... Close ISSUE-65 with the understanding that PRD does not add specific syntax to specify halting tests.

<PaulVincent> +1 to #3 :)


<Gary> Retract(obj[slot->*]) Assert(obj[slot->value])

<apaschke> i.e. modify = retract all old frames + assert new frame

<PaulVincent> Does this have issues with the collection / array semantics? ie retract * = empty an array if multivalued slots?

<cke> Agree with Adrian.



<cke> modify(obj[slot1->value1 slot2->value2, ...])

<apaschke> our semantics is defined in terms of snapshots

<apaschke> which are herbrand models

<apaschke> assert / retract actions lead to a new snapshot (state)

<PaulVincent> Modify is normally a.b = <value>

<Gary> Modify(obj[slot->v1 slot->v2])

<cke> Also: modify(obj[slot->v1 slot->v2 slot2->v3 slot2->v4 slot3->v5]

<cke> The point here is to remove everything, and re-state all the slots again.

<Gary> if Modify(obj[slot->value]) means the same as Do(Retract(obj[slot->*]) Assert(obj[slot->value])) then I am in favor of Modify

<cke> Gary, we agree here.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2009/02/03 19:43:17 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: csma
Inferring Scribes: csma

WARNING: No "Topic:" lines found.

WARNING: No "Present: ... " found!
Possibly Present: Also Gary PROPOSED PaulVincent apaschke cke
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 03 Feb 2009
Guessing minutes URL: http://www.w3.org/2009/02/03-rif-prd-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]