Joe; One idea is to set your script up as a Web service and call it from a cron job that runs periodically.
-- Scott On Nov 25, 9:40 am, Joseph Shea <[email protected]> wrote: > We are automating the process of ingesting new data and inferencing of > that data into our ontology. > > SPARQLMotion Process: > > - A Readings ontology is refreshed periodically (say, every hour) > using a Spreadsheet import process. > > - The Classification ontology takes these readings, applies > classification SPIN rules, and infers how the readings get classified. > > - Once the inferences are made, the original readings and inferences > are added to persisted versions of these in their respective TDB’s. > > In the process above, we use the same baseURI as for the TDB, but an > empty Readings owl file (that supplies all the classes and properties, > but no instances) to process and infer. > > In order to do this, we have to make the empty file the current one > temporarily. > > After the SPARQLMotion inferencing is done, the application and > subsequent queries need to use the larger TDB version that grows over > time to millions of triples. > > We are testing this successfully in Composer, but how do we automate > this transactional-master file switch in TopBraid Live in production? -- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en.
