Re: Is SPIN still a valid direction?

Isn't the issue that SPIN is supported only by a single vendor?  You should
either talk to them about it or develop a competitive implementation.

The old version of :BaseKB was derived by a process that used the in-memory
Jena models and I implemented as much of the processing that I could in by
writing SPARQL construct queries that would fill up new models with facts.
This is very much in the spirit of SPIN,  as if it were running in the
"sequential mode" which most rule engines support.

A concise example of this is here

https://github.com/paulhoule/infovore/blob/v1.0/hydroxide/src/main/java/com/ontology2/hydroxide/turtleTwo/ConstructTurtleTwoApp.java

As for what tools to use,  it's time to go back to the future and use tools
based on the predicate calculus,  FOL,  Modal logic and so forth.  The good
news is that these tools have improved greatly in recent years and they
also have a good track record in commercial use;  i.e. at least one of them
supervises every transaction you make at your bank.



On Fri, Dec 19, 2014 at 12:33 PM, Antonino Lo Bue <lobue@pa.icar.cnr.it>
wrote:

> Hi everyone,
>
> I'm wondering if someone from the list could make a clear point on SPIN
> adoption and usage status. I'm planning to use it in my research work to
> model SPARQL inferencing on Open data->Linked open data workflows , but I
> have heard that something new is coming and would/could replace SPIN with
> a more flexible language.
> Is this the case and so I could risk to work with outdated and legacy
> stuff? Or do you encourage the adoption?
>
> Thanks and regards
>
> Antonino Lo Bue
> CNR-ICAR Palermo
> LinkedIn: http://www.linkedin.com/in/antoninolobue
>
>
>
>


-- 
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254    paul.houle on Skype   ontology2@gmail.com
http://legalentityidentifier.info/lei/lookup