New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DM: For Measurements, use UNCEFACT vocab instead of core code lists #269

Open

NiclasScheiber opened this issue Sep 25, 2024 · 0 comments

Contributor

NiclasScheiber commented Sep 25, 2024 •

edited

Loading

ONE Record 3.0 introduced cXML code lists to the standard. These include MeasurementUnitCodes.

There are few disadvantages:

The list from IATA is not exhaustive
The list from IATA mirrors UNECE Rec. 20
The list from IATA lacks key measurement units, such as angles for tilt sensors

UNECE themselves put out the complete code list as linked data as part of the BSP data model as UnitMeasureCode.

To

avoid double maintenance
keep the single source of truth (UNECE defines these codes anyway)
eliminate discussions about new codes down the line

I recommend to deprecate IATAs code lists in favor of the UNCEFACT vocabulary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment