Paul J. Durack

@wachsylon can you answer the question whether DWD used CMOR (or a CDO2CMOR wrapped version) to write these data?

You folks are starting to get aligned with what we've been discussing. We are thinking of following a structure similar to  - note this has evolved a little, but...

@mauzey1 good question, the `further_info_url` (supported by ES-Docs, but I am unable to find a working example at this moment) is indeed supported for obs4MIPs (see https://github.com/PCMDI/obs4MIPs-cmor-tables/blob/master/inputs/pcmdi/RSS/RSS_prw_v07r01.json#L6), but all this...

@mauzey1 thanks for continuing to chip away at these issues. `further_info_url`, which uses the es-doc URL, is only applicable to the CMIP6 and obs4MIPs project, within input4MIPs we define this...

> Shouldn't `check_sourceID` be done regardless of the further info URL, or whether or not the project is CMIP6? And this is exactly correct. The way that we have things...

@mauzey1 it would be useful to update PrePARE alongside the last planned release of CMOR3 to enable consistency checking as much as possible - let's revisit this issue as the...

@taylor13 I agree with this, if we have a "final" CV template that we can build PrePARE4 (along CMOR4) to work with, then I suggest that's the best path forward,...

Conversation with @sashakames noted that in order for PrePARE to currently validate data, we need to match the `data_specs_version` attribute to the cmip6-cmor-tables version that CMOR (or other software) used...

@sashakames it seems we've solved the seats issue, so tagging you here - which will likely require @mauzey1 at some stage

@mauzey1 that would be a nice addition, as a warning. Thinking about this, ideally, it would be great to always check against the latest version of the tables, so that...