W3C home > Mailing lists > Public > public-rif-comments@w3.org > April 2010

riftr implementation report

From: Sandro Hawke <sandro@w3.org>
Date: Fri, 23 Apr 2010 12:09:16 -0400
To: public-rif-comments@w3.org
Message-ID: <18915.1272038956@waldron>

This is an implementation report, as per 

>   1.  Your name, affiliation, and (optionally) the names of other
>   people who helped with the implementation.

Sandro Hawke, W3C/MIT.

>   2. The name of your system, a URL for its website (if any), and a
>   one-sentence description.

An open source Python framework for working with RIF

>   3. Which dialects your software is designed to support (eg Core,
>   BLD, PRD, or non-standard extension dialects). We would appreciate
>   some brief commentary about why you chose these dialects, and what
>   sorts of implementation techniques (eg algorithms) are being used.

Most of riftr is dialect-indenpendent.  Some bits are Core or BLD
specific, based on which languages or engines it's working with in that

>   4. Do you believe your system currently conforms to the RIF
>   Candidate Recommendations? Does it pass all the test cases for your
>   dialect(s)? If not, which features does it lack and/or which test
>   cases does it not yet pass? Do you have plans to make it conformant,
>   and make it pass all the test cases?

It's more proof-of-concept than complete.  It has passed some test
cases, including the test of list builtins, and some of the RDF Imports

>   5. Does it implement any parts of RIF RDF and OWL Compatibility? Any
>   issues?

Yes, it implemented RDF Importing.  No issues.

>   6. Did you implement the "at risk" features? If not, do you intend
>   to, or do you think we should remove them from RIF?

No, it does not implement them.  I think they can stay, but riftr
doesn't provide any evidence on the matter.

>   7. We'd appreciate your evaluation of whether the RIF Candidate
>   Recommendation is ready to proceed along the standards track toward
>   being a W3C Recommendation. If not, please be sure to tell us what
>   problems you think we need to address.

Yes (as recorded elsewhere)

>   8. Which datatypes & builtins do you support?

The framework is agnostic about datatypes and builtins. 

Only the list builtins are supported enough to pass a test case (using
SWI Prolog as the back-end rule engine, for that).

>   9. Finally, send your test results, as described in reporting test
>   results, which we can aggregate with software. If your test results
>   file includes information about your project, you may leave it out
>   of your implementation report, since we can get it from your test
>   results file.

Sorry, I haven't done this yet.  Not sure when I'll get a chance.
Received on Friday, 23 April 2010 16:09:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:07:00 UTC