MCF version value for new YAML MCF format? about pygeometa HOT 6 CLOSED

+1 to default to 2.0.0, we should probably stick to x.y format (2.0) as a rule.

from pygeometa.

Agreed. Updating our local YAML MCFs. Leaving open until pygeometa documentation is updated

from pygeometa.

I just realized pygeometa has never made it to a 1.0.0 release yet. Should we keep the YAML version to 1.0 and assume the INI files were pre-1.0? We don't have to follow YAML version with pygeometa version per se, but given the INI files were never versioned it may make sense. Thoughts?

from pygeometa.

Agreed. Let's revert our local MCF version to "1.0". Copying @RousseauLambertLP

Furthermore, am I right that currently there isn't any validation of the MCF version value done when running pygeometa? There should be such a test that validates that the MCF version is indeed a supported version by pygeometa. If you agree, I'll create a new ticket accordingly. Merci

from pygeometa.

@alexandreleroux agree and +1 for a new ticket on how to deal with mcf version checking and management.

from pygeometa.

Done and closing this one

from pygeometa.