Updates AIP-140 and AIP-141 with guidance on naming quantity fields with compound and/or inverse units#1524
Merged
noahdietz merged 2 commits intoaip-dev:masterfrom Jun 10, 2025
Merged
Conversation
This includes a new subsection covering compound units, a new subsection covering inverse units, and some overall wording adjustments to clarify when plural form should be used for field names.
AIP-141 has been updated with more detailed guidance on the use of the preposition "per" in field names representing quantities, and this note should be updated to refer to that guidance. Note that the previous note guidance here may have suggested that an event-frequency field should be named like e.g. "failures_per_hour", while after this change it will point to guidance in AIP-141 that specifies the format as e.g. "failure_count_per_hour". This may be interpreted as a functional change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.