From 6134a77f599c858e49e9e9f3ea416c2d9dd6fa37 Mon Sep 17 00:00:00 2001 From: Dave Allured Date: Wed, 9 Oct 2024 13:22:11 -0600 Subject: [PATCH 1/3] ch02: Revert PR 478, period and hyphen in names * Revert #478 --- ch02.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/ch02.adoc b/ch02.adoc index a0e569bf..895db1c6 100644 --- a/ch02.adoc +++ b/ch02.adoc @@ -51,7 +51,6 @@ By the word _letters_ we mean the standard ASCII letters uppercase `A` to `Z` an By the word _digits_ we mean the standard ASCII digits `0` to `9`, and similarly _underscores_ means the standard ASCII underscore `_`. Note that this is in conformance with the COARDS conventions, but is more restrictive than the netCDF interface which allows almost all Unicode characters encoded as multibyte UTF-8 characters (link:$$https://docs.unidata.ucar.edu/nug/current/file_format_specifications.html$$[NUG Appendix B]). The netCDF interface also allows leading underscores in names, but the NUG states that this is reserved for system use. -ASCII period (.) and ASCII hyphen (-) are also allowed in attribute names only. Case is significant in netCDF names, but it is recommended that names should not be distinguished purely by case, i.e., if case is disregarded, no two names should be the same. It is also recommended that names should be obviously meaningful, if possible, as this renders the file more effectively self-describing. From 5c96e4e5be837d058e7385cb019666d4f2cef718 Mon Sep 17 00:00:00 2001 From: Dave Allured Date: Fri, 25 Oct 2024 08:21:13 -0600 Subject: [PATCH 2/3] history.adoc: Remove PR478, reverted by PR549 . * False change: Period and hyphen in attribute names. * Sentence was added, then removed later within same working version. --- history.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/history.adoc b/history.adoc index bac81795..69d8507c 100644 --- a/history.adoc +++ b/history.adoc @@ -16,7 +16,6 @@ * {issues}511[Issue #511]: Appendix B: New element in XML file header to record the "first published date" * {issues}509[Issue #509]: In exceptional cases allow a standard name to be aliased into two alternatives * {issues}501[Issue #501]: Clarify that data variables and variables containing coordinate data are highly recommended to have **`long_name`** or **`standard_name`** attributes, that **`cf_role`** is used only for discrete sampling geometries and UGRID mesh topologies, and that CF does not prohibit CF attributes from being used in ways that are not defined by CF but that in such cases their meaning is not defined by CF. -* {issues}477[Issue #477]: Period and hyphen allowed in attribute names * {issues}500[Issue #500]: Appendix B: Added a **`conventions`** string to the standard name xml file format definition === Version 1.11 (05 December 2023) From e19ebb50382ef9e5ef0a9778a72c9900e535aba4 Mon Sep 17 00:00:00 2001 From: Dave Allured Date: Fri, 25 Oct 2024 08:23:46 -0600 Subject: [PATCH 3/3] conformance.adoc: Remove PR478, reverted by PR549 . * False change: Period and hyphen in attribute names. * Sentence was added, then removed later within same working version. --- conformance.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/conformance.adoc b/conformance.adoc index 4e490ab9..57369773 100644 --- a/conformance.adoc +++ b/conformance.adoc @@ -37,7 +37,6 @@ See https://github.com/ugrid-conventions/ugrid-conventions for the UGRID conform *Recommendations:* * Variable, dimension and attribute names should begin with a letter and be composed of letters (A-Z, a-z), digits (0-9), and underscores(_). This corresponds to ASCII characters in the decimal ranges (65-90), (97-122), (48-57), and (95). The corresponding Unicode codepoints are (U+0041-U+005A), (U+0061-U+007A), (U+0030-U+0039), and (U+005F). -* ASCII period (.) and ASCII hyphen (-) may also be included in attribute names only. * No two variable names should be identical when case is ignored. [[section-2]]