See:
http://code.google.com/p/owltools/wiki/OortMultipleOntologies
Midori, this should sort your problem with FYPO. You will have to hand edit on the first round to get rid of the line in the previously merged stanza.
Then the next time you run Oort your external classes should look like this:
[Term]
id: CHEBI:33822
name: organic hydroxy compound
namespace: chebi_ontology
def: "An organic compound having at least one hydroxy group attached to a carbon atom." []
synonym: "hydroxy compounds" EXACT IUPAC_NAME [IUPAC:]
synonym: "organic hydroxy compounds" RELATED [ChEBI:]
property_value: IAO:0000412 http://purl.obolibrary.org/obo/chebi.owl
is_a: CHEBI:24651 ! hydroxides
is_a: CHEBI:50860 ! organic molecular entity
Then on subsequent releases, anything that has the imported_from tag will be removed first prior to merging - and then in most cases a fresh one merged back in provided its still in the closure.
More documentation coming soon. There are a few different scenarios whereby you have dependency chains, e.g.
A <-- B <-- C
and
A <-- C
If a subset of C is already merged into B and they have the imported_from tags, then this subset is flushed and you end up with the subset of C that is either referenced directly in A, or referenced in the subset of B that is referenced in A.
--
To sign up for this list:
http://code.google.com/p/owltools/wiki/OortMailList
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Obo-ontology-release-tool mailing list
Obo-ontology...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/obo-ontology-release-tool