Nope, missed that part.  That did it though, thanks!  Looks like great
stuff!
 
Jeff

________________________________

From: Holger Knublauch [mailto:hol...@topquadrant.com] 
Sent: Thursday, March 26, 2009 3:41 PM
To: topbraid-composer-users@googlegroups.com
Subject: [tbc-users] Re: SPIN API is now open source


Hi Jeff,

did you call this at init time: 




// Initialize system functions and templates
SPINModuleRegistry.get().init();


This will load the spl namespace and the functions defined therein,
including the system functions such as sp:mul so that the SPIN engine
knows that they are abbreviated (e.g. using *).

Holger


On Mar 26, 2009, at 1:28 PM, Schmitz, Jeffrey A wrote:



        Hello,
          I finally got a chance to look through the new SPIN API, and
started
        with trying to run the SPIN rules on the spinsquare ontology.  I
think
        I'm pretty close, except it's choking on the line in the
spin:rule
        construct query that uses the multiplication symbol, i.e.
        
           LET (?area := (?width * ?height)) .
        
        Stepping through the code, I can see that this gets turned into
what I
        would guess must be a property function named sp:mul:  
        
          LET (?area := sp:mul(?width, ?height))
        
        However, I don't think my execution environment has access to
that
        function and thus the query doesn't return anything.  Is there
any way I
        could get this function and make it available to my execution
        environment, and is that documented anywhere?  Or is that not
part of
        the release?
        
        Thanks!
        Jeff
        
        -----Original Message-----
        From: Holger Knublauch [mailto:hol...@topquadrant.com] 
        Sent: Saturday, March 07, 2009 12:38 PM
        To: topbraid-composer-users@googlegroups.com
        Subject: [tbc-users] SPIN API is now open source
        
        
        Dear users,
        
        we have had several requests from people who would like to
integrate
        SPIN functionality (SPARQL-based constraint checking,
inferencing,
        user-defined functions) into their own applications. In order to
        encourage the wider adoption of SPIN in the community, we have
therefore
        decided to make the key features of our SPIN implementation open
source:
        
        http://www.topquadrant.com/topbraid/spin/api/
        The SPIN API is built on Jena and provides the following
features:
        
        * Converters between textual SPARQL syntax and the SPIN RDF
        Vocabulary
        * A SPIN-based constraint checking engine (via spin:constraint)
        * A SPIN-based inferencing engine (via spin:rule and
        spin:constructor)
        * Support to execute user-defined SPIN functions using Jena/ARQ
        * Support to execute user-defined SPIN templates
        
        The license has been selected to allow open source projects
(from
        universities etc) to use SPIN without further complications. For
closed
        source users, we offer a commercial license that also provides
business
        users assurance and support. With this policy we hope to
encourage
        researchers to provide their (open source) implementations back
to the
        community to help the SPIN community grow.
        
        The SPIN API is currently in beta, and the official 1.0 release
is
        scheduled in conjunction with TopBraid 3.0 in the next few
weeks. We
        appreciate your feedback in the meantime.
        
        Kinds regards,
        Holger
        
        
        
        
        
        
        






--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to topbraid-composer-users@googlegroups.com
To unsubscribe from this group, send email to 
topbraid-composer-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to