Re: Potential text for time-permitting features in F&R

 > I think we should then say RIF Core and RIF BLD. This is all 'time
 > permitting', so if BLD is too complex (I do not believe the difference
 > is so big, though), it could be skipped... But let us not promise/talk
 > about PLD.
 >
 > Axel, what do you think?

I agree with all the observations mentioned before.
Anyways, strongly safe Core [1] is a straightforward starting point, as 
it guarantees finiteness.

Ordinary Core and BLD may still yield infinite sets of consequences 
which why extended BGP matching doesn't fall out that easily, probably.

</chair>
(now getting even "more time"-permitting) on a more fine-grained level, 
in fact, it might be useful to:

1) define our own dialect  which can be more restricted or extend RIF 
Core in parts; e.g. a dialect that could handle full SPARQL patterns in 
rule bodies (which current RIF can't because not all FILTER functions 
are covered), that could be done by an additional SPARQL-built-in function.

2) present an easier to read presentation syntax for RIF which is 
aligned with SPARQL's syntax, at least for examples. This would be 
fairly simple and very useful for promoting RIF in the SPARQL cummunity.
<chair>

1. http://www.w3.org/2005/rules/wiki/Core#Strong_Safeness_.28Informative.29


Ivan Herman wrote:
> 
> Chimezie Ogbuji wrote:
>> On 6/25/09 9:23 AM, "Ivan Herman" <ivan@w3.org> wrote:
>>> Ie, I would rather say:
>>>
>>> [[[
>>> [...] Time-permitting, the SPARQL WG will use the existing framework to
>>> define the semantics of SPARQL queries for one or more of these
>>> entailment frameworks:
>>> + OWL 2 with both Direct and RDF Based Semantics, including OWL 2 profiles
>>> + RDF Schema
>>> + RIF rule sets
>>> ]]]
>>>
>>> Another issue I have is with RIF Rule sets, (I would leave Axel to say
>>> that): I would have thought that only RIF Core and RIF BLD dialects are
>>> really o.k. with SPARQL. I do not believe that RIF PLD would be a
>>> reasonable candidate...
>> Certainly not RIF PLD, and perhaps RIF Core alone.
>>
> 
> I think we should then say RIF Core and RIF BLD. This is all 'time
> permitting', so if BLD is too complex (I do not believe the difference
> is so big, though), it could be skipped... But let us not promise/talk
> about PLD.
> 
> Axel, what do you think?
> 
> Ivan
> 
>> ----------------------
>> Chimezie Thomas-Ogbuji (oh-bu-gee)
>> Heart and Vascular Institute (Clinical Investigations)
>> Cleveland Clinic (ogbujic@ccf.org)
>> Ph.D. Student Case Western Reserve University
>> (chimezie.thomas-ogbuji@case.edu)
>>
>>
>> ===================================
>>
>> 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 (2008).  
>> Visit us online at http://www.clevelandclinic.org for
>> a complete listing of our services, staff and
>> locations.
>>
>>
>> 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.
>>
> 


-- 
Dr. Axel Polleres
Digital Enterprise Research Institute, National University of Ireland, 
Galway
email: axel.polleres@deri.org  url: http://www.polleres.net/

Received on Friday, 26 June 2009 11:31:32 UTC