Doug Tody a écrit :
MEF files are an important part of FITS, but unfortunately this issue
of describing the overall MEF as a structured object has never been
adequately addressed. While it may be possible for a MEF to be a random
collection of FITS extensions that are concatenated together, this is
not the only model nor necessarily even the best one. In many applications
one would like to consider the MEF to be a structured object, and be able
to add high level information to describe the object, indendent from
what is stored in the individual extensions. The most logical place to
put this information in FITS currently is in the primary header.

One could easily argue that we need *more* keywords in the primary
header to properly describe a MEF, not less as seems to be the trend
of this discussion.

Or one could take the (in my view more logical) view that a MEF file
is the wrong choice when strong structural information needs to be
included :-)