Yes. On TBL there is no concept of "primary" files any more. We assume that there is only one copy of each base URI. This case is rare but makes sense in TBC while people are working on multiple copies. But on a deployed setting, managing multiple files with the same base URI would only complicate things and lead to scenarios that are hard to track down and error prone. As Scott suggests, please try to work around it by giving each file/DB a unique base URI.
Holger On Nov 25, 2009, at 9:12 AM, Scott Henninger wrote: > I take it the problem is that default namespace and base URI for > Import.owl are coupled and hence new data created have the base URI as > the namespace. And that's why Import.owl and Export.tdb need to have > the same base URI. > > I think any reliable solution is going to require the Import.owl and > Export.tdb have different base URIs (they are different files, so they > need to have different unique identifiers). Start by decoupling base > URI and default namespace in Import.owl, delete the default namespace, > change the base URI, and define a namespace prefix that uses the old > default namespace. > > This will allow you to define resources in Import.owl using the > Export.tdb namespace, yet have a unique base URI for Import.owl. > > -- Scott > > On Nov 25, 11:00 am, Joseph Shea <[email protected]> wrote: >> Yes, that is how it is done in TBC. However, if this were to be >> automated through SparqlMotion, it woul dbe done on a TBL server, and >> would not involve someone opening files up manually every time that >> new data came in. >> >> On Nov 25, 11:56 am, "Irene Polikoff" <[email protected]> wrote: >> >>> Yes, the cron job can be done. >> >>> However, I believe the key question is how this process can update the >>> registry with respect to what is the primary data graph for a given URI. In >>> TBC, in cases where you have two files or databases use the same base URI, >>> you just double click to open and this will switch which one is primary. >> >>> -----Original Message----- >>> From: Scott Henninger [mailto:[email protected]] >>> Sent: Wednesday, November 25, 2009 11:01 AM >>> To: TopBraid Composer Users >>> Subject: [tbc-users] Re: Switching primary files with the same namespace >> >>> 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 >>> athttp://groups.google.com/group/topbraid-composer-users?hl=en.-Hide quoted >>> text - >> >>> - Show quoted text - > > -- > > 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. > > -- 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.
