Migrating eagle-i MIREOT files and reestablishing ISF MIREOTs.

[GoogleCodeExporter]

This issue was created by revision r309.

Starting to move eagle-i MIREOT files and integrate them with the ISF. The 
first one being migrated is the GO MIREOT. It is copied to the ISF mireot 
folder and given the IRI: http://purl.obolibrary.org/obo/arg/go-mireot.owl with 
a file name of go-mireot.owl

Original issue reported on code.google.com by sha...@essaid.com on 10 Dec 2013 at 5:21

[GoogleCodeExporter]

This issue was updated by revision r310.

The eagle-i MIREOT file was copied to the "mireots" folder in the previous 
commit. This commit has the result of a script that:
1. looks at each axiom in the file and if there is a matching axiom (except for 
declaration axioms) in any ISF file, the axiom is removed from the ISF file and 
it is kept in the go-mireot.owl file.
2. If an axiom in go-mireot.owl does not exist in any ISF file (i.e. it is a 
new axiom), it is moved to the temporary go-mireot-new.owl file for later 
review and curation. 
3. For the script does 1 & 2, few axioms might have been manually moved to the 
go-mireot-other.owl file and these need manual review. This done because the 
script doesn't take care of all types of axioms. The script is really meant to 
deal only with Class, OP, and DP entities and other axioms need manual review.
4. There is a log of the script actions in the Dropbox folder in "round 3". 
Also see the todo.txt in the same folder.

Original comment by sha...@essaid.com on 10 Dec 2013 at 6:26