Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Table of Contents

Rules

  1. Specification shall always be publicly available

  2. Specification shall adhere to style as defined in the NMWDI style guide

  3. Modification of the specification requires consent of majority of the active TWG members

  4. Modification of the specification requires a formal proposal following guidelines defined in NMWDI Specification Enhancement Proposal (SEP)

The Zen of NMWDI

(inspired by https://peps.python.org/pep-0020/ )

Duplication is wasteful, linking is better
Data first, Apps second
Share the data you collect
Explicit is better than implicit
Consistent is good, standardized is better, validation is essential
Robustness.  Conservative in what we provide, liberal in what we accept

Style Guide

Rules:

  1. All lower case

  2. underscores between words

  3. spell out full words for clarity

  4. use nested properties instead of name qualifiers

Specification Enhancement Proposal Template

  • No labels