Difference between revisions of "Sub Ontology Tab"
(fixed formatting problems and improved grammar in more details section) |
|||
| Line 9: | Line 9: | ||
|Affiliation2=The CO-ODE Project | |Affiliation2=The CO-ODE Project | ||
}} | }} | ||
| − | + | ||
| + | <div style="width:100%; float:left;"> | ||
| + | == More Details == | ||
| + | Did you ever wish you could copy or drag and drop a class hierarchy from one ontology into another instead of typing it in? Or, did you ever wish you could extract the class hierarchy from one section of a large ontology like the NCI Metathesaurus or GO into a separate ontology? If so, the Sub Ontology Tab is your answer to these tedious tasks! What's more, the tab lets you copy the concept annotations in the hierarchy being copied/extracted across, so the concepts in your target ontology retain the metadata from the original ontology.<br /><br /> | ||
| + | </div> | ||
Revision as of 09:58, April 16, 2008
Sub Ontology Tab
by Jay Kola
Allows manipulation of axioms across ontologies.
Versions & Compatibility
This section lists available versions of Sub Ontology Tab.
| Version | Compatible with | Dependencies |
|---|---|---|
| Sub Ontology Tab 1.0.3 | Protege-OWL 4.0 |
If you click on the button below to add a new version of Sub Ontology Tab, you will be asked to define a page title for the new version. Please adhere to the naming convention of Sub Ontology Tab X.X.X when you define the new page!
Changelog
| Version | Changes in this version |
|---|---|
| Sub Ontology Tab 1.0.3 | no release notes were maintained for this version |
More Details
Did you ever wish you could copy or drag and drop a class hierarchy from one ontology into another instead of typing it in? Or, did you ever wish you could extract the class hierarchy from one section of a large ontology like the NCI Metathesaurus or GO into a separate ontology? If so, the Sub Ontology Tab is your answer to these tedious tasks! What's more, the tab lets you copy the concept annotations in the hierarchy being copied/extracted across, so the concepts in your target ontology retain the metadata from the original ontology.
