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

Appendix B: In exceptional cases allow a standard name to be aliased into two alternatives #510

Merged
merged 3 commits into from
Mar 22, 2024
Merged

Appendix B: In exceptional cases allow a standard name to be aliased into two alternatives #510

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
92c651b
Updated appb.adoc
larsbarring Feb 23, 2024
fa5bfbf
Updated history.adoc
larsbarring Mar 6, 2024
4cc3bc1
Merge branch 'main' into issue-509
sadielbartholomew Mar 22, 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
10 changes: 10 additions & 0 deletions appb.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,16 @@ Each **`alias`** element contains a single element:
</alias>
----

In exceptional cases the **`alias`** element may contain two elements:

----
<alias id="an_id">
<entry_id>Identifier of a defining entry ... </entry_id>
<entry_id>Identifier of another defining entry ... </entry_id>
</alias>
----


[[name-table-three-entries-ex]]
[caption="Example B.1. "]
.A name table containing three entries
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}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
Expand Down
Loading