Hi James, you could try to Save as... and select N3 or NT format to save it. Maybe this particular error only happens in RDF/XML syntax.
But the more general problem is that TBC directly writes to the target file. It would probably be safer to first write to another file and only replace the original file if no error showed up. We'll look into this. Holger On Feb 5, 2009, at 9:42 AM, James A Miller wrote: > > I loaded an ontology into TBC, which appeared to load correctly. In > TBC, it was tagged as "changed" (with the asterisk). So I pressed > Save, and received the following popup: > > > <mime-attachment.gif> > > I am not concerned about the error--the file has a syntax problem > that I will address. > > My issue is that, when I press OK on this dialog, my OWL file > (presumably the one with the error) is now completely empty. It > appears that maybe my ontology is still in memory, but since it is a > syntax problem, I need to look at the text version. And the text > version shows an empty file (as do the File Properties). This > situation was easily repeatable. > > I have a (reasonably) recent backup of this file, so it is not > catastrophic for me at this time, but could be a big problem in > different circumstances. > > Thanks, > Jim > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
