Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Can I use my own database tables?

Jennifer Vendetti vendetti at
Mon Oct 9 17:45:12 PDT 2006


Fred wrote:
> I'm new to Protege. We have quite a few Oracle database tables used by our proprietary Taxonomy appliation and other applications. We are thinking of migrating to Protege. Besides the Protege, our other applications will still need the access to these tables.  I have a few questions:
> 1.  Can we still use our own tables in Protege for our ontology contents?  
Protege uses its own database format, described here: 

If you don't want to use the Protege database back-end, you can write 
"import" and "export" plug-ins that import & export your taxonomy to & 
from Protege into your own tables.

> 2. If we can, how can we access the content of these tables? Do we use APIs, PlugIns, or somthing else?
A common thing that people do is to use Protege as an editor and then 
periodically export snapshots of their ontologies/taxonomies into their 
own proprietary database tables.  The best way to do this is to write an 
export plug-in, documented here:

There are examples of export plug-ins in our source code repository.  
You might look at the HTML export plug-in:

Of course, you will also need to do an initial import of your data into 
Protege.  You can either write an import plug-in (a.k.a. "createproject" 
plug-in), documented here:

Or, you could try using the DataGenie plug-in to import your data.  This 
is a plug-in that allows you to import data from arbitrary databases 
into Protege.  It may or may not produce a result that you would like to 
move forward with:


More information about the protege-discussion mailing list