Sure, let's break this decision into parts, starting with the high-level ones. 
I just reread all posts, and  my take is that the essential points are:

- There are some questions about where to register Zenodo (less work) vs 
directly through UCAR or UC Library (more freedom);
- How deep we want to go in the hierarchy (granularity & reproducibility).

The top-level DOI is not under discussion anymore. It will be the sole DOI or 
the overarching DOI collecting the sub levels. Both paths require it, so let's 
start with it. My suggestion here is to record a DOI for the CF concept, 
grouping CF-Conventions and CF-Standard Names together, no version-specific at 
this point ([item 
(A)](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-933831094__;Iw!!G2kpM7uM-TzIFchu!kUr9u2TlmcC9Dpenn0-cQxafPoPVFgQx2nkt4Oxq27UMOlVyIXC_58l6BaeamAxyEoKuA9SVbqA$
 )) Since this is a vital record, I strongly believe that we should have all 
the freedom to set it up (and update later) as we wish, so I would not consider 
Zenodo for this one. I believe that @ethanrd  has access through UCAR to 
register it, otherwise, I volunteer myself to do that through UC Library. Both 
paths are equally good, but I would give priority to @ethanrd if he wants that 
job (I can help).

Once we are done with that, we can start the discussion on sub-levels. If we 
decide on that route, the top-level DOI shouldn't require any change.

-- 
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-1006011961__;Iw!!G2kpM7uM-TzIFchu!kUr9u2TlmcC9Dpenn0-cQxafPoPVFgQx2nkt4Oxq27UMOlVyIXC_58l6BaeamAxyEoKuuobCPf0$
 
You are receiving this because you commented.

Message ID: <cf-convention/cf-conventions/issues/127/[email protected]>
This list forwards relevant notifications from Github.  It is distinct from 
[email protected], although if you do nothing, a subscription to the 
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to 
[email protected].

Reply via email to