#153: Requirements related to specific standard names
-----------------------------+------------------------------
Reporter: martin.juckes | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
Comment (by martin.juckes):
Dear Jonathan,
On 2nd thoughts, however, in connection with updating "frequently and
easily", we need to be careful about backward compatibility. E.g. if we
introduce it in parallel with CF-1.7, files which were considered valid
under CF-1.6 might become invalid. We want, I think, such files to
continue to be considered as vaild under CF-1.6, hence the checker should
not use this extension when checking against earlier convention versions.
This differs from the policy with the standard name list, for which the
latest is always used. This implies, I think, that this document would
need to be clearly versioned in a way which makes the link to convention
versions clear, eg. we might start with 1.7.00 and increment to 1.7.01 etc
until the convention moves to 1.8.
I can see that we want flexibility to add rules about new standard names
when the standard name table is updated, and this is far more frequent
that convention updates. We need to be careful about dealing with rules
for existing standard names which might have been overlooked. Once we have
a 1.7.00 version, we should not change any rules for existing standard
names until 1.8.00 is launched, though we could perhaps add advisory notes
where appropriate.
Does this sound workable?
regards,
Martin
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:6>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
