W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2010

[TF-Ent] RIF Core Entailment section

From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Sat, 06 Mar 2010 21:32:34 -0500
To: "SPARQL Working Group WG" <public-rdf-dawg@w3.org>
cc: "Birte Glimm" <birte.glimm@comlab.ox.ac.uk>, "Ivan Herman" <ivan@w3.org>, "Axel Polleres" <axel.polleres@deri.org>, "Sandro Hawke" <sandro@w3.org>
Message-ID: <C7B87A72.10310%ogbujic@ccf.org>

It has been fleshed out and I have added various references.  There are a
few editorial notes involving the following issues:

- the 8th condition (C8) of a common-RIF-RDF-interpretation includes the
set-theoretic semantics of rdfs:subClassOf that are also used by the RDFS
Entailment regime
- Embedding a subset of RIF-OWL combinations (OWL 2 RL for instance) as
extensions to this entailment regime (issues of consistency checking,
axiomatic triples and rules)

Are there examples of RIF Core (normatively) safe rulesets / documents that
use builtins that do not introduce new values into the domain that are
useful as arguments against the finite restrictions? I started by looking at
the extant N3 Logic / CWM builtins but none of them jumped out at me except
the obvious log:semantics, etc.

A mapping from all the SPARQL builtins to corresponding RIF builtins (beyond
those in the RIF Datatypes and Built-Ins document) could further close the
expressive gap between RIF Core and SPARQL.  I think they would all be safe
(and maybe also strongly safe).

Chime (chee-meh) Ogbuji (oh-bu-gee)
Heart and Vascular Institute (Clinical Investigations)
Architect / Informatician
Cleveland Clinic (ogbujic@ccf.org)
Ph.D. Student Case Western Reserve University


P Please consider the environment before printing this e-mail

Cleveland Clinic is ranked one of the top hospitals
in America by U.S.News & World Report (2009).  
Visit us online at http://www.clevelandclinic.org for
a complete listing of our services, staff and

Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank you.
Received on Sunday, 7 March 2010 02:33:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:59 UTC