REST services for creating, importing data & updating a Taxonomy/Ontology

[sanjeev devireddy]

Hi,
  
      We are planning to migrate taxonomies from our application to TopBraid EDG, by exporting from our application and then importing to EDG. We do have plans to automate this process as much as we can, by creating a job. So, we just want to check that whether are there any TopBraid  EDG REST services to create, update & import data (through ttl/RDF files) into a Taxonomy/Ontology or not. Could someone please help?



Thanks,
sanjeev

[Jack Hodges]

I haven't used EDG but we use Topbraid Live and there are no REST services to perform these necessary functions, only direct export from Topbraid Composer to TBL or direct import from a zipped Topbraid Composer project into TBL. If you find or build one please announce here. Thank you.

Jack Hodges, Siemens

[Irene Polikoff]

Hi Sanjeev,

Is it a one time migration or do you plan to do this on a regular basis? 

If latter, would this be a total replacement of previously imported content? In other words, if it is a subsequent import, could what you are importing have been modified both in EDG and in the source system?

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sanjeev devireddy]

Hi Irene,

          Sorry for the late reply. I was busy with other tasks.

            In our current system/application there are more than 1K (1000) taxonomies. For some taxonomies there are regular/monthly updates. In our system, for regular/monthly updates, a new version of the taxonomy is created and data is imported to that new version. And that new version contains some additional/updated nodes/concepts.

     Since there more than 1K taxonomies and we have limited number of resources working on migration, so we assume that migration may take few(1 or 2) months. For the time being, we are planning to maintain/run both the systems (our application & EVN/EDG) in parallel till the time all taxonomies are migrated and works fine in EVN/EDG as expected. That means taxonomies will be updated in both the systems (our application & EVN/EDG) during this migration period (which may take 1 or 2 months).

       And for the taxonomies that are imported to EVN, whenever a new version is created in our system/application then that should be imported to EVN/EDG also, so that in both the systems (our application & EVN/EDG) taxonomy data is same. We hope that the working copies in EVN/EDG can be used as versions of taxonomies in our system/application. Now, our plan is to automate this import of new versions of taxonomies from our system/application to EVN/EDG. I hope this make sense. Please check and let  me know.

 

 

Thanks,

sanjeev