See issue #301 for discussion of these changes.

# Release checklist
- [x] Authors updated in `cf-conventions.adoc`?
- [x] Next version in `cf-conventions.adoc` up to date? Versioning inspired by 
[SemVer](https://semver.org).
- [ ] `history.adoc` up to date?
- [x] Conformance document up-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 `master` 
always is a draft for the next version.

You can view, comment on, or merge this pull request online at:

  https://github.com/cf-convention/cf-conventions/pull/302

-- Commit Summary --

  * first draft of section 5.8
  * format typo
  * rewording
  * rewording
  * rewording
  * New 'Do' Use value, and 'dimensions' entry
  * Domain construct
  * rewording
  * rewording
  * rewording
  * formatting of computed_standard_name entry
  * rewording
  * rewording
  * rewording
  * top-level
  * rewording
  * move fig 3
  * rewording
  * span
  * rewording
  * data
  * rewording
  * rewording
  * rewording
  * conformance
  * recommended attributes
  * typo
  * dimensions
  * dimensions
  * format
  * typo
  * domain independence
  * domain optional
  * format
  * format
  * format
  * format
  * empty dimensions
  * long_name
  * UML

-- File Changes --

    M appa.adoc (19)
    M appi.adoc (122)
    M ch05.adoc (288)
    M conformance.adoc (52)
    M images/cfdm_field.pdf (0)
    M images/cfdm_field.png (0)

-- Patch Links --

https://github.com/cf-convention/cf-conventions/pull/302.patch
https://github.com/cf-convention/cf-conventions/pull/302.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/pull/302

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