Re: [h5md-user] H5MD developer's guide

[Olaf Lenz]

I completely agree with Konrad. I think by far the best solution is to provide 
a reference implementation, ideally as a library, so that it can be used by 
others. We are currently working on implementing the vmd plugin for h5md, and 
this turns out complex on the one hand and incomplete on the other. From that 
Plugin, we will try to get a reference implementation for some aspects. 

The has been a lot of discussion going on in the last days, and I haven't been 
able to follow all of it. Also, i do not want to read all of them now.  Do we 
have a changelog or something? Or is it best to use the git log? Is the 
discussion section in the spec up to date? 

Olaf

Konrad Hinsen <address@hidden> schrieb:
>And that's why I suggested a Developer's Guide. It would already be of
>value as a means of communication between the people on this list
>implementing different H5MD libraries for different languages.
>
>I don't believe it is possible to design a solid data model or file
>format without implementing it completely. Every single line in a
>specification needs to have some demonstrable impact on a reference
>implementation. If it doesn't, then it's useless, unclear, impossible
>to do, or all of that. Designing a file format without implementing
>it is like writing a program without testing it: bugs are guaranteed.