Dear Andy,
thank you very much for your comment and idea. I recognize that HDF format may have some clear advantage and if I am not mistaken Matlab do also make use of it to store its .mat files. The argument not to use HDF, at least for this first version (i.e. version 1.x) of OEIT, would be the one of the broadest compatibility. What I find very attractive in using ZIP encoding is that you now-a-days find ZIP codec installed per default in almost every OS. The choice of using ZIP was also made by .docx and .odt developers. I guess that the main reason for that is that you can browse the archive as folder/file structure, which I find very convenient.
The point is that ZIP is not a definitive choice, if at some point HDF becomes a much broader standard we could switch to it any time because the basic structure of OEIT remains the same and is not based on the way we encode the data. This was the idea behind decoupling the content (folder, files, configuration files...) from the way it is actually stored in binary format on the hardrive.
What do you think? What would be the main argument to switch to HDF?
Pascal