<csma> http://www.w3.org/2005/rules/wg/wiki/Arch/Extensibility

<csma> A RIF dialect is forward compatible if a conformant implementation will process instances of any future or unknown extension according to the specification of the said extension.

<csma> obj[att=val]

<csma> = to ->

<csma> <object> to <Frame>

<csma> fallback="reject"

<csma> fallback=IRI

<csma> obj[att less-than val]

<csma> exist ?x obj[att->?x] and (?x less-than val)

default would be single valued (so Core users don't need to care about)

e.g. a Prolog like relation of a Frame http://fragrantfish.com/biz-vocabulary#Item.deliveredTo(Item, Item.deliveredTo)

and the Frame representation would be Item(http://fragrantfish.com/biz-vocabulary#Item.deliveredTo -> ?Item.deliveredTo)

we solved a similar transformation in the demo we had at RuleML-2008 between ILog, Oracle BRMS and Prova

the demo at RuleML-2008 http://ruleml-challenge.cs.nccu.edu.tw/?q=node/25

yes, to really support object models we would need to support type information such <Var type=xsd:Integer>X</Var>

<csma> Adrian, my prefered approach to that is that a RIF document should have an accompanying data model doc if needed; e.g. an XML schema, giving all the info about cardinality, data types etc

married(A,B) married(A,C) is valid

<Hassan> excl_assert(P) :- ( P , !, retract(P) ; assert(P)).

logically it is correct, it is only wrong with respect to the application which forbids that someone is married to two different persons

therefore you would need to add constraints

<cke> if married(A,B) married(A,C) is valid, the uncle and aunt relations will be wrong. Maybe we just say this is fine. So far, I try to understand what to do with this.

we could use an optional attribute in XML; by default or when omitted (as in Core) it means singel valued

<cke> in terms of processing, it is just simpler to consider married(A,B) and married(A,C) as valid. The logic will be an additive logic.

semantics of BLD frames can not be changed

due to last call

but in Core we don't have sets

lists etc.

<csma> Right, Adrian. But adding a datatype for sets/list/whatever is something we will have to discuss...

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: apaschke
Inferring Scribes: apaschke

WARNING: No "Topic:" lines found.

Default Present: csma, Hassan_Ait-Kaci, cke, GaryHallmark, apaschke
Present: csma Hassan_Ait-Kaci cke GaryHallmark apaschke

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: 27 Jan 2009
Guessing minutes URL: http://www.w3.org/2009/01/27-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