Ticket #6 (closed enhancement: wontfix)

Opened 7 years ago

Last modified 6 years ago

miscellaneous package => non redundant sum of all environmental packages

Reported by: whankeln Owned by: pyilmaz
Priority: major Component: environmental packages
Version: 2.2 Keywords:
Cc: Sensitive: no

Description

The environmental packages do not contain a package that is the non redundant sum of all environmental packages (the miscellaneous package doesn't fulfill this requirement). This is practical, let me again explain you why:

For the ease of use it would be really nice to have such a package. Then users have the choice, rather than searching in all packages for their desired fields and to combine them (rather time consuming. Don't you think?), to say:
"I pick the universal package, since it contains all fields and use only those parameters of it, that I need. This way I am on the safe side!"

Also, this suggestion is not a XOR to the combination of packages, but a useful addition.

Change History

comment:1 in reply to: ↑ description Changed 7 years ago by rkottman

Hi,

You point to weakness in in the specification.

For the ease of use it would be really nice to have such a package. Then users have the choice, rather than searching in all packages for their desired fields and to combine them (rather time consuming. Don't you think?), to say:
"I pick the universal package, since it contains all fields and use only those parameters of it, that I need. This way I am on the safe side!"

What you propose is exactly, what we try to avoid: Last exit to inconsistencies.

The different environmental packages have different requirements on the contextual data items. E.g. "depth" is mandatory in the "water" package but not in "air". Exactly to have the different requirements according to the environment. If we give the chance that everybody is using the "miscellaneous" package as the non-redundant set of all environmental parameters (where we would need to make everything just optional) we would defeat the purpose of having different requirements for different environments.

The set of environmental packages is chosen so that all should be applicable in almost all cases and was based on the different surveys we did (see e.g. MIMARKS paper (still named MIENS in this version)).

Then one can ask for what we have a "miscellaneous" package: The aim is to cover the rare case in which all other environmental packages do not apply. It does not cover this case well.

Nevertheless, "miscellaneous" is not meant for ease of use, it is meant for the difficult rare case that the other packages do not apply.

Therefore, I suggest to NOT make use of this package if not absolutely needed.

comment:2 Changed 6 years ago by pyilmaz

  • Status changed from new to closed
  • Resolution set to wontfix
Note: See TracTickets for help on using tickets.