Re: W3C RIF BLD Last Call (10 days left in comment period)

Just on first reading I find the syntax to be quite problematic. It  
clashes with other well known syntaxes namely Turtle, SPARQL and N3.

The two problems I see is that in those languages square brackets are  
used for blank nodes, and { } to delimit graphs.

As an example take the following

Forall ?x ?y ?z (?x[ex:uncleOf -> ?z] :-
        And(?x[ex:brotherOf -> ?y] ?y[ex:parentOf -> ?z]))

If I were to write the above in SPARQL I think you meant to say

PREFIX ex: <>

CONSTRUCT { ?x ex:uncleOf ?z }
      ?x ex:brotherOf ?y .
      ?y ex:parehtOf ?z .

In N3 similarly

{ ?x ex:brotherOf ?y .
   ?y ex:parehtOf ?z . } => { ?x ex:uncleOf ?z . }

SPARQL is already widely deployed, and there are a lot of N3 rules out  
there, that are very useful guides for people working their way around  
the web. There is even more Turtle around, and it is a blessing that  
it is now being used, as RDF/XML though very nice in many ways, leads  
to a huge amount of confusion.

My feeling is that the current human readable syntax, not being  
aligned with SPARQL is going to create confusion unecessarily. It  
seems to be that an attempt should be made to get something that fits  
better with SPARQL and N3 intuitions, so as to make the learning curve  
as light as possible for people who are new to this world.


On 9 Sep 2008, at 16:51, Sandro Hawke wrote:

> The W3C specifications for logic rules and for using rules with RDF  
> and
> OWL are in their "Last Call" public comment period.  This is the time
> for people to read them and tell us about anything that doesn't seem
> right.  After this, if you don't like something in the spec, it will  
> be
> increasingly hard to get it changed.  We would like comments by
> September 19 in order to consider them for our next set of revisions.
> For more details, see this e-mail I sent August 1st:
> Thanks!
>     -- Sandro

Received on Tuesday, 9 September 2008 15:58:33 UTC