Editorial changes for the CF-1.12 release documents #574
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix order for "Jon Blower" Change community to the "cfconventions" Updated file sizes and md5 checksum (how this works)
cofinoa
approved these changes
Dec 4, 2024
cofinoa
changed the title
| @@ -1,10 +1,10 @@ | |||
| { | |||
| "metadata": { | |||
| "title": "NetCDF Climate and Forecast (CF) Metadata Conventions", | |||
| "description": "This document describes the CF conventions for climate and forecast metadata designed to promote the processing and sharing of files created with the netCDF Application Programmer Interface. The conventions define metadata that provide a definitive description of what the data in each variable represents, and of the spatial and temporal properties of the data. This enables users of data from different sources to decide which quantities are comparable, and facilitates building applications with powerful extraction, regridding, and display capabilities. The CF conventions generalize and extend the COARDS conventions. The extensions include metadata that provides a precise definition of each variable via specification of a standard name, describes the vertical locations corresponding to dimensionless vertical coordinate values, and provides the spatial coordinates of non-rectilinear gridded data. Since climate and forecast data are often not simply representative of points in space/time, other extensions provide for the description of coordinate intervals, multidimensional cells and climatological time coordinates, and indicate how a data value is representative of an interval or cell. This standard also relaxes the COARDS constraints on dimension order and specifies methods for reducing the size of datasets.", | |||
| "description": "<p>This document describes the CF conventions for climate and forecast metadata designed to promote the processing and sharing of files created with the netCDF Application Programmer Interface. The conventions define metadata that provide a definitive description of what the data in each variable represents, and of the spatial and temporal properties of the data. This enables users of data from different sources to decide which quantities are comparable, and facilitates building applications with powerful extraction, regridding, and display capabilities.</p><p>The CF conventions generalize and extend the COARDS conventions. The extensions include metadata that provides a precise definition of each variable via specification of a standard name, describes the vertical locations corresponding to dimensionless vertical coordinate values, and provides the spatial coordinates of non-rectilinear gridded data. Since climate and forecast data are often not simply representative of points in space/time, other extensions provide for the description of coordinate intervals, multidimensional cells and climatological time coordinates, and indicate how a data value is representative of an interval or cell. This standard also relaxes the COARDS constraints on dimension order and specifies methods for reducing the size of datasets.</p>", | |||
There was a problem hiding this comment.
What's the reason for this change? Is it OK to have <p> in the Zenodo description?
There was a problem hiding this comment.
Yes, it's ok for Zenodo. It's needed if we want to split both paragraphs i. the abstract. All previous versions, include them, and also I have removed the [COARDS] and [NetCDF] text used as links.
JonathanGregory
approved these changes
Dec 4, 2024
cofinoa
approved these changes
Dec 4, 2024
cofinoa
approved these changes
Dec 4, 2024
| :current-version: {version} | ||
| :current-version-as-attribute: {version} | ||
| :doi: 10.5072/zenodo.FFFFFF |
There was a problem hiding this comment.
don't remove it, ad here the actual pre-resrved DOI for v1.12.
We will need to handle this better in the future
There was a problem hiding this comment.
Agreed. I moved the :doi: definition a few lines up, so it's still there.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No associated issue.
Release checklist
cf-conventions.adoc? Add in two places: on line 3 and under.Additional AuthorsinAbout the authors.cf-conventions.adocup to date? Versioning inspired by SemVer.history.adocup to date?For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then,
mainalways is a draft for the next version.