Few newbie questions. 1. How an Ontology is used? I mean is there any technical use of the ontology or is it only for functional use i.e. to understand the structure/scope/extent of the data? 2. We are working on a SOA based project where we are getting data from different sources. Can we use the ontology to mapp data from different sources? 3. Can an ontology coexist and be meaningfull technically with the physical database? I appreciate any respone or links or pointers here. Thanks in advance
--- On Fri, 10/7/11, Irene Polikoff <[email protected]> wrote: From: Irene Polikoff <[email protected]> Subject: RE: [topbraid-users] setup teamwork changes repository To: [email protected] Date: Friday, October 7, 2011, 10:04 AM Hi Paul, What I am writing here should work in principle, but we are not testing or "officially" supporting such setups. All TBC-ME users will need to have a connection to the same change (teamworks) repository in their workspaces. You will need to create user names (just change the users file) for all of them. Each user will need to be logged in with their user name when they make updates. TBC-ME will prevent them from making changes to the teamwork controlled database if they are not logged in. To login they just go to their local EVN home page and enter their user name. They only need to do this once and it must be entered exactly to provide consistency/traceability for you. It is a honor-based system. Since there is no application server, there is no security/user name management, they could just make up a user name. With this in place, changes made in TBC-ME should be logged. As far as web clients, since you are not using TBL, you would need to implement change logging yourself. You can look at the teamworks schema. It is pretty self explanatory. Each time you run an update query, you would need to update the teamworks repository. Of course, you'd need to make sure that everything stays in sync. That is - only changes that succeed get logged and every change that succeeds gets successfully logged. Regards, Irene -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of PaulZH Sent: Friday, October 07, 2011 4:55 AM To: TopBraid Suite Users Subject: [topbraid-users] setup teamwork changes repository Context. Working on a POC: - where a few clients using TBCME heavily to talk to a OWLIM-SE within the OpenRDF Sesame Framework (up and running) - where web clients do very occasionaly SPARQL updates to the same OWLIM-SE (up and running) It would be nice to have some global change tracking in place. I do find documentation on setting up the teamwork changes repository within the context of EVN and using EVN, but I wondered if this could also be used in a scenario not using EVN or Live as described above. If yes, is this documented somewhere? Regards, Paul -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
