Hello all, Recently we are asked to look into using Ontology as it is becoming a big buzzword in DoD for our project and I am not sure as how and where we can start and also to justify. Here is the scenario we are in: Ours is a service orineted architecure where we get data from several sources and store it in SQLServer RDMBS (not tripple store). Into the database and out of the database we have web services to consume and expose data ( rudimentary explanation of our architecture) Now we need to see how can we leverage the ontology concepts. 1. Do we need to create Ontology for our data structures and then migrate data from our current DB to triple store? 2. Can we keep our current RDBMS and use Ontology (tripple store) as an added layer? 3. If there is an advantage of using 1 over 2 or vice versa? 4. Is there an example or case study for some one has gone through a similar situation. I appologize in advance ifor my minimal knowledge about this realm of Ontology... Appreciate any response on this.. Regards Qadeer
-- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), 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
