[Tom Bunch]

For reference, this indicates that OmniPlan is unable to open or parse the contents.xml that should be inside the document (.omniplan file) wrapper. If you were to just create an empty directory calls foo.omniplan, you could make this happen. There are a lot of ways that you can create the situation that we can't do much about... (check the .omniplan directory out of svn, but not the contents.xml; make a shallow copy of .omniplan directory; hand edit the .xml file yourself...) but I wouldn't expect a user who'd do anything I can think of to be surprised when OmniPlan throws a tantrum. So assuming this file is exactly as it was when OmniPlan itself wrote it to your disk, we'd really love your help figuring out what happened!

-Tom