W3C home > Mailing lists > Public > public-rif-wg@w3.org > January 2008

Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification

From: Christian de Sainte Marie <csma@ilog.fr>
Date: Tue, 08 Jan 2008 16:51:12 +0100
Message-ID: <47839BF0.6060008@ilog.fr>
To: Chris Welty <cawelty@gmail.com>
CC: "Public-Rif-Wg (E-mail)" <public-rif-wg@w3.org>

Chris Welty wrote:
> Proposed: Close Issue-41 by including in BLD membership formulae of the 
> form c rif:type a.  In the RDF compatibility document, rif:type will be 
> defined to be equivalent to rdf:type.

An issue to take into account in discussing this is whether and how it 
would impact Dave's use case for the membership formula [1].


[1] http://lists.w3.org/Archives/Public/public-rif-wg/2007Nov/0077.html

I have another, different but somewhat similar use case, that is not 
made but was submitted to me by somebody from MISMO. The question was 
how a "not exists" condition could be handle in RIF, and the example was 
the following rule:

IF         <LoanPurpose>.Type = Refinance
            AND NOT EXISTS <REOProperty> with SubjectIndicator=Y
             Set Action -- DataValidation = Fail

Of course, it is rather a PRD example, but we should preferably have 
only one membership relation, if we need it in both BLD and PRD.

Knowing that the MISMO schema (xxx) contains the following type definitions:

<xs:complexType name="AUS_LOAN_APPLICATION_Type">
	<xs:element name="REO_PROPERTY"
                     type="AUS_REO_PROPERTY_Type" minOccurs="0"
<xs:simpleType name="AUS_MISMOIndicatorType">
	<xs:restriction base="xs:string"/>

I proposed that the RIF equivalent could be something like:

Forall ?loanApplication
If NOT(Exists ?reoProperty
                    # mismo: AUS_LOAN_APPLICATION_Type^^rif:iri
then ...

where the reference to REO_PROPERTY and @_SubjectIndicator are XPath-like.
Received on Tuesday, 8 January 2008 15:51:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:47:49 UTC