[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mon, 09 Sep 2013 12:56:04 +0200
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
-----BEGIN PGP SIGNED MESSAGE-----
On 09/09/2013 12:11 PM, Konrad Hinsen wrote:
> I think the same approach could work for H5MD: provide a
> "convention" field in the H5MD metadata, and let people work out
> conventions for their respective domains. For the species
> information, this could range from a simple convention such as
> "use chemical element numbers" to more elaborate ones such as "the
> species is an index into an array named xxx that stores additional
Your concept of "conventions" seems to be pretty similar to what I have
called "modules" in a (off-line) discussion with Pierre and Felix,
however coming from the technical point of view. My idea was that
instead of trying to define everything in the H5MD specs, it would be
nice to allow for "modules" on top of the H5MD specs (which would be the
My idea was the following:
1. A module has a name (e.g. "protein description").
2. A module contains further specifications on top of the H5MD
specification that describe how certain fields look like (syntax) and
how they are to be interpreted (semantics). A "protein description"
module would probably contain specs how to describe the type of an atom
and its position in the protein sequence.
3. When a h5md file uses a module, this should be specified in a group
in the file (probably h5md/modules).
4. Modules can be proposed by users and user groups, and they can be
published on the h5md home page.
5. When a module has proven its value, it can be integrated into the
Dr. rer. nat. Olaf Lenz
Institut für Computerphysik, Allmandring 3, D-70569 Stuttgart
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----