Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow period and hyphen in attribute names #478

Merged
merged 4 commits into from
Mar 1, 2024
Merged

Allow period and hyphen in attribute names #478

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a14b14b
Allow period and hyphen in attribute names
Dave-Allured Nov 10, 2023
65b3591
Merge branch 'cf-convention:main' into period-hyphen
Dave-Allured Mar 1, 2024
6aa8243
Conformance doc, characters in attrib names
Dave-Allured Mar 1, 2024
4ff7ddb
History doc, characters in attrib names
Dave-Allured Mar 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ch02.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,7 @@ 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.

Dave-Allured marked this conversation as resolved.
Show resolved Hide resolved
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.
Expand Down
1 change: 1 addition & 0 deletions conformance.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ 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.
Dave-Allured marked this conversation as resolved.
Show resolved Hide resolved
* No two variable names should be identical when case is ignored.

[[section-2]]
Expand Down
1 change: 1 addition & 0 deletions history.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@

=== Working version (most recent first)

* {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)
Expand Down
Loading