&ND v2

+++document/meta
schemaVersion = "1"
id = "compound-unit-labels"
title = "Appendix — Compound Unit Labels (Informative)"
description = "Informative note on using compound unit labels such as m/s and kg/m^3 as opaque identifiers in conventions."
family = "conventions"
group = "Informative Convention Appendices"
standing = "official"
lifecycle = "draft"
normativity = "informative"
license = "CC0-1.0"
path = "specification/conventions/compound-unit-labels"
order = 90
publish = true
keywords = ["AEON", "measurement", "compound units", "unit labels", "reference"]
related = ["aeon-gp-measurement-v1"]
+++


# Appendix — Compound Unit Labels (Informative) [# appendix-compound-unit-labels-informative]

AEON GP Measurement v1 permits compound unit labels in the [$ unit] attribute.

Compound unit labels are treated as [* opaque identifiers] and are not parsed or interpreted by AEON.

Example:

~~~$ aeon
speed@{unit="m/s"} = 12
acceleration@{unit="m/s^2"} = 9.81
density@{unit="kg/m^3"} = 1000
bandwidth@{unit="Mb/s"} = 100
~~~$

---


## Interpretation [# interpretation]

Compound unit labels may describe derived measurements such as:

| Unit       | Meaning                   |
| <--        | <--                       |
| [$ m/s]    | meters per second         |
| [$ m/s^2]  | meters per second squared |
| [$ kg/m^3] | kilograms per cubic meter |
| [$ Mb/s]   | megabits per second       |
|~ Compound measurement unit examples

AEON does [* not] interpret or validate these expressions.

They are treated as [* plain unit identifiers].

---


## No Grammar Requirement [# no-grammar-requirement]

AEON GP Measurement v1 does not define a formal grammar for compound units.

Characters such as the following may appear within unit labels:

~~~$
/
*
^
-
~~~$

Example:

~~~$ aeon
power@{unit="kg*m^2/s^3"} = 120
~~~$

Processors, schemas, or profiles may optionally define stricter rules if needed.

---


## Recommended Practice [# recommended-practice]

When compound units are used, they should follow widely recognized conventions (such as SI notation) to improve
interoperability.

Example:

~~~$ aeon
flow_rate@{unit="m^3/s"} = 4
~~~$

---


## Summary [# summary]

Compound units are allowed because:

- they are common in scientific and engineering data
- they require no additional language features
- they remain consistent with AEON’s rule of [* opaque value labeling]

AEON therefore preserves compound unit labels exactly as written.

---