28 Apr 2009

See also: IRC log


Paul, Vincent




<apaschke> "not" was not accepted


<cke> why not just "neg"?

not, neg, naf

those ones are not for consideration

inflationary negation

<apaschke> not_class, not_inf, not_naf


<apaschke> maybe we should offer several different proposals and them simply do a straw poll in the next general RIF telecon

Not(Exists ?x P(?x))

<cke> another example: (not (customer.age > 20))

<cke> if the customer's age is 18, then this is true


<apaschke> prdNot, bldNot, coreNot, ...

Naf = Negation as failure

Nsf = Not supported by facts

<cke> and "boolean_not"?

<cke> I prefer it not to be an acronym. I like something explicit like "negation"


<cke> Can we avoid saying "fact"?

<cke> There can be only test, like (not (customer.age > 20))

<apaschke> I prefer Nsf over Notsf since NsF is like Neg, Naf

<apaschke> a variant could be "No matching facts" = Nmf

<cke> how about "notf"?

<cke> Another example (customer (age not > 20))

<cke> how about "binary_not"?

<apaschke> classical (Boolean) negation

<apaschke> is a two-valued true-false logic

<apaschke> three-valued logic with unknown truth value (Kleene negation)

<cke> And "pnot" for production rule not?

<cke> or maybe "prnot"?






<cke> I find ineg better

<cke> how do we write it?

<cke> ineg, INeg or Ineg?

PROPOSED: INeg (for Inflationary, or immediate, negation)

<cke> +1

<apaschke> subsumption is already an advanced concept to optimize the execution flow

<cke> Subsumption is very advanced, we have to do extensive analysis for this

PROPOSED: drop subsumion from the conflict resolution strategy, and come back to the previous consensus (refraction+priority+recency), maybe with an implementation note.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/04/28 18:20:30 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
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: PROPOSED apaschke cke csma
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Regrets: Paul Vincent

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: 28 Apr 2009
Guessing minutes URL: http://www.w3.org/2009/04/28-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]