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] Pluging Protege on top of Jena.

Tania Tudorache tudorache at
Fri Feb 22 21:48:08 PST 2008


Please note that we have a separate mailing list for posting Protege-OWL 
related questions:

I did not understand exactly what you are trying to do. Protege has its 
own API which is used to built plug-ins or applications on top of 
Protege. For more documentation about the Protege APIs, both frames and 
OWL, please see [1].

Protege API is not built on top of Jena API. There are ways of obtaining 
a Jena model out of a Protege OWL model, which are documented here [2].

The KnowledgeBase, Cls and Slot classes are part of the Protege frames 
API. The Protege OWL API is built on top of it. However, if you want to 
develop a plugin or an application in OWL, you should not use the frames 
API, but the Protege-OWL API [3].

Please ask in future OWL related questions on the Protege-OWL mailing list.



Olivier Rossel wrote:
> Hello.
> I am trying to see the difficulty of pluging some Protege components
> on top of Jena.
> Basically, when browsing the sources, I am always sent back to
> KnowledgeBase.class.
> Even Cls and Slot are delagates of KnowledgeBase.class.
> Does it mean that achieving my goal is as simple as coding a
> JenaBasedKnowledgeBase.class?
> And injecting it into a JenaBasedProject.class ?
> I would appreciate any comment about that idea (especially from people
> used to Protege internals).
> PS: The point is to propose editing facilities for any project that
> has chosen Jena as its internal API.
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at
> Instructions for unsubscribing: 

More information about the protege-discussion mailing list