
|
N3 formulation of RIF builtins [Was: fuXi not installing on AMD 64 + Ubuntu]
[sorry for cross-posting with public-cwm-talk]
Today I was able to make an initial
Eye rif-plugin plus test cases
at http://eulersharp.sourceforge.net/2007/07test/rifP.n3
and the actual N3 formulation of RIF
builtins is following
(args) func:xxx value.
(args) pred:xxx true.
which is different from what I said
before..
The test result of
eye --nope --plugin http://eulersharp.sourceforge.net/2006/02swap/rif-plugin.yap
http://eulersharp.sourceforge.net/2007/07test/rifP.n3
--query http://eulersharp.sourceforge.net/2007/07test/rifQ.n3
is looking like
#Processed by $Id: euler.yap 3080 2009-08-06
12:40:36Z josd $
@prefix func: <http://www.w3.org/2007/rif-builtin-function#>.
@prefix pred: <http://www.w3.org/2007/rif-builtin-predicate#>.
@prefix e: <http://eulersharp.sourceforge.net/2003/03swap/log-rules#>.
@prefix : <http://eulersharp.sourceforge.net/2007/07test#>.
@prefix var: <http://localhost/var#>.
@prefix r: <http://www.w3.org/2000/10/swap/reason#>.
@prefix n3: <http://www.w3.org/2004/06/rei#>.
{((0 1 2) 3) func:append (0 1 2 3)}
a :PASS.
{((0 1 2) 3 4) func:append (0 1 2 3
4)} a :PASS.
{((1 1) (1) (1) ((1))) func:append (1
1 (1) (1) ((1)))} a :PASS.
{(() 1) func:append (1)} a :PASS.
{(1 1) func:numeric-add 2} a :PASS.
{(5 2) func:numeric-divide 2.5} a :PASS.
{(5 2) func:numeric-integer-divide 2}
a :PASS.
{(10 3) func:numeric-mod 1} a :PASS.
{(6 -2) func:numeric-mod 0} a :PASS.
{(4.5 1.2) func:numeric-mod 0.9} a :PASS.
{(123.0 6.0) func:numeric-mod 3.0} a
:PASS.
{(5 2) func:numeric-multiply 10} a :PASS.
{(5 2) func:numeric-subtract 3} a :PASS.
{(1 1.0) pred:numeric-equal true} a
:PASS.
{(1.0 0) pred:numeric-greater-than true}
a :PASS.
{(1.0 1) pred:numeric-greater-than-or-equal
true} a :PASS.
{(2.0 3) pred:numeric-less-than true}
a :PASS.
{(3 5.0) pred:numeric-less-than-or-equal
true} a :PASS.
{(1 1.01) pred:numeric-not-equal true}
a :PASS.
{("""abracadabra"""
"""bra""") pred:matches true} a :PASS.
{("""abracadabra"""
"""^a.*a$""") pred:matches true} a :PASS.
#ENDS 8 msec
Before doing the full set of builtins
in http://www.w3.org/TR/rif-dtb/
I just wanted to give this the benefit
of your thoughts (on both lists)
Kind regards,
Jos De Roo | Agfa HealthCare
Senior Researcher | HE/Advanced Clinical Applications Research
T +32 3444 7618
http://www.agfa.com/w3c/jdroo/
Quadrat NV, Kortrijksesteenweg 157, 9830 Sint-Martens-Latem, Belgium
http://www.agfa.com/healthcare
| Jos De Roo/AMDUS/AGFA
07/21/2009 10:43 PM
|
|
That is really excellent news Chimezie!
Last night I also had some exchange
with Sandro but Eye will stick to N3
and w.r.t. the n-ary builtins I think
we can express them in N3 as
yyy func:xxx (args).
_:void pred:xxx (args).
and I am definitely prepared to invest
time to implement all of them either
in the euler.yap code directly or as
a
--plugin <yap_resource> command
line option such as e.g.
eye --nope --plugin http://eulersharp.sourceforge.net/2007/07test/plugin.yap
--query http://eulersharp.sourceforge.net/2007/07test/pluginQ.n3
Kind regards,
Jos De Roo | Agfa HealthCare
Senior Researcher | HE/Advanced Clinical Applications Research
T +32 3444 7618
http://www.agfa.com/w3c/jdroo/
Quadrat NV, Kortrijksesteenweg 157, 9830 Sint-Martens-Latem, Belgium
http://www.agfa.com/healthcare
On Tue, Jul 21, 2009 at 2:29 PM, <jos.deroo@...> wrote:
> Fuxi --input-format=n3 --output=n3 --ruleFacts --closure
> --rules=http://www.w3.org/2000/10/swap/test/reason/t5.n3
>
> runs fine and gives
Hey Jos. Thanks for checking this out.
> While at it, do you plan to have a --input-format=rif-xml
> For Eye we don't plan one but it would be great to have your engine
> connected for that :-)
Yes, I do actually. Sandro just pointed me to the current test cases
so I was going to get started on support for rif-xml serialization of
rules
-- Chimezie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"fuxi-discussion" group.
To post to this group, send email to fuxi-discussion@...
To unsubscribe from this group, send email to fuxi-discussion+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/fuxi-discussion?hl=en
-~----------~----~----~----~------~----~------~--~---
|