ISSUE-33: Specification of data sources in RIF [NOT CP]

Specification of data sources in RIF [NOT CP]

Technical Design (multiple dialects/documents)
Raised by:
Deborah Nichols
Opened on:
[Modified by Dave Reynolds to reflect f2f7 discussion.]

We believe that RIF should support the ability for a ruleset to refer to
external data sets (not included as RIF facts inline with the ruleset).
Sometimes the data is local to the application, sometimes a specific external
data set must be referenced. If so:

(a) We require a mechanism by which such specific external data sets can be

(b) We also need to specify the data model associated with such data sets and,
in the case of RDF, any associated entailment regimes.

Both of these issues are discussed in where a metadata vocabulary
has been proposed.

The issue is open since we have not yet formally agreed that either or both of
these capabilities are indeed needed, nor have we formally agreed on the
proposed metadata vocabulary.
Related Actions Items:
No related actions
Related emails:
  1. Re: [Admin] Agenda for F2F11 (from on 2008-09-20)
  2. Re: [Admin] Agenda for F2F11 (from on 2008-09-19)
  3. [Admin] Agenda for RIF telecon April 21 (from on 2008-04-21)
  4. Minutes from April 15, 2008, telecon (from on 2008-04-18)
  5. [Admin] Draft minutes for Telecon 20 November 2007 (from on 2007-11-20)
  6. irc log from F2F8 (from on 2007-11-08)

Related notes:

At the 5/13 telecon, it was decided to remove this from the BLD critical path, as far as the BLD LC is concerned, this is covered by the imports mechanism, which addresses How to refer to an RDF graph or OWL ontology to be discussed, in relation with issues 39 and 46, and "RIF must cover OWL knowledge bases as data where compatible with Phase 1 semantics [] OWL data]) and "RIF must cover RDF triples as data where compatible with Phase 1 semantics" ([ RDF data])

Christopher Welty, 16 May 2008, 12:27:57

RESOLVED: Close issue-33 with the understand that our mechanisms for accessing RDF and XML data sources, and using externals, will be sufficient.

Sandro Hawke, 15 Jan 2009, 20:14:57

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 33.html,v 1.1 2013-02-08 09:09:34 vivien Exp $