I take it you did the import through owl:imports for a file (i.e. the Import view)? You may be able to undo this by choosing the file in the Import view, deleting it, and choosing 'yes' to removing usages of the import. For imports of files in non-validates rdf, it is always best to test the import on an empty file to make sure it imports properly. And don't save the file until you know it is working or has not corrupted the ontology.
You may be able to salvage this file by globally replacing the URIs that have a ":" in the namespace with one that uses "#" to separate the namespace from the local name. We can add safeguards that will not allow .xlsx files to be imported. -- Scott On Jun 4, 7:27 am, [email protected] wrote: > Scott, > > Importing those Excel 2007 files completely destroyed the OWL file. I > had to add </rdf:RDF> to the end of the file to get it to open without > errors, but the import process overwrote all my top two tiers of > classes so all I was left with was about 10% of my bottom tier of > subclasses and any instances. I tried rolling back to a local history, > but that file was corrupt too. the lesson here is to save my own local > versons several times a day so I can roll back. I did this on a > previous project when my file went to OWL Full when I wanted OWL Lite > so I guess I relearned a valuable lesson. Lucky for me there was no > deliverable for this file, it was just a "for fun" project. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
