Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>
Co-authored-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com>

…/type.yaml

…nition src files

… to be a list

Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>

Co-authored-by: Johan Bergsma <29785380+JPBergsma@users.noreply.github.com>

…ferences

Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>

Co-authored-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com>

Co-authored-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com>

…tionship is not exact

Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>

Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>

…y Definition example based on review

Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>

Co-authored-by: Antanas Vaitkus <antanas.vaitkus90@gmail.com>

…andards

…es with a generic 'id' for future-proofing

…ated text.

…type and id, cannot be excluded from the response.

…userfriendly

Co-authored-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com>

…emas make sense. Important: this changes how units are ordered in Compound Unit Expressions

Allowing prefixes to be merged with unit symbols greatly complicates parsing and may not even make sense (or be unambigous) the way we now can mix and match symbols.
From a standards and implementation prespective it is also preferably not to have to treat prefixes differently from unitless constants.
Now all unitless prefixes and constants go first (in alphabetical order) and then comes all "real" units (in alphabetical order).

…tand-alone versions

Co-authored-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com>

…nd Physical Unit Definitions

…units to be defined one level higher, but rename unit-defintions to units so the fields can be named the same thing.

…units to be defined one level higher, but rename unit-defintions to units so the fields can be named the same thing.