Units, money, locale and calendars
Reusable types for quantities, currencies, ranges, dates, calendars and localized labels.
Bundle → Layer → Finding → Questions Filled
2 bundles · 4 layers · 5 findings · 12 questions
Quantities and money Describe quantities, monetary conversions and bounded or unbounded ranges.
Quantity and unit
State the measurement scheme and numerical treatment of a quantity.
Stated unit
Bind a quantity to its unit, precision and rounding policy.
- Which unit and unit scheme does this quantity record use?
- What precision and rounding rule apply to this value record?
Money and exchange
Describe the currencies and rate interpretation used by a monetary conversion.
Currency conversion
Make a recorded conversion interpretable through its currencies and rate basis.
- Which currency does this monetary amount record use?
- Which rate source, effective date and applicable rate type does this conversion record specify?
- Which source and target currencies and quoted exchange-rate direction does this conversion record specify?
Ranges and bounds
Describe range endpoints and their interpretation.
Range boundaries
Distinguish inclusive, exclusive, unbounded and unknown range endpoints.
- What lower and upper endpoint values and common value type does this range record specify?
- For each endpoint of this range record, is it inclusive, exclusive, explicitly unbounded or unknown?
Time and language Describe temporal interpretation and the language of object labels.
Calendar and time zone
Apply calendar and time zone context only where the value's meaning requires it.
Working calendar
Distinguish elapsed duration, local civil time and calendar-based availability.
- What temporal value type does this record represent, and which calendar or time zone does its interpretation require?
- What effect, if any, does a daylight saving transition have on this interval record under its declared interpretation?
- What availability does this comparison record report for eight hours under each named working calendar over its specified interval?
Localised label
Identify a label's language without changing the identity of its subject.
- Does this label record translate an existing name or refer to a different object?
- Which language tag identifies this label record?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise contract
- Entry kind
- contract
- Domain
- EnterpriseXCT
- Industry
- Cross-industry
- Tags
- EM-XCT-06W0contractQuantityMoneyUnitReferenceCalendarReferenceLocalizedText
What it is Filled
Reusable types for quantities, currencies, ranges, dates, calendars and localized labels.
Why it exists Filled
Reusable types for quantities, currencies, ranges, dates, calendars and localized labels.
Distinguishing features Filled
- Every quantity carries a stated unit, and every monetary amount carries a currency.
- A currency conversion records its rate source, effective date, applicable rate type and direction.
- Date-only values and elapsed durations do not inherently require a time zone.
- Calendar and time zone context are stated when required to interpret civil time or working availability.
- Ranges distinguish endpoint values, inclusivity, explicit unboundedness and unknown bounds.
- A translated label names the same object and never creates a new one.
What robots and AI may and may not do Filled
Must not
- Assume eight hours yields the same availability across the concrete calendars and interval being compared.
- Convert currency without a stated rate source, effective date, applicable rate type and direction.
- Drop time zone information required to interpret a temporal value.
- Require a time zone solely because a value is a date-only value or an elapsed duration.
- Round values without stating the rule.
- Create a new object because a name appears in another language.
- Treat an unknown range endpoint as explicitly unbounded.
Only with a human decision
- Choose the official rate source for financial conversions.
- Approve changes to rounding rules used in billing or payroll.
- Approve working calendars that affect pay or contractual deadlines.
May
- Convert units and currencies with the rule, rate source, effective date, rate type and direction shown.
- Compute availability using the working calendar and applicable time zone of each party.
- Flag quantities without units and monetary amounts without currencies.
- Flag missing time zones only where the value's interpretation requires a zone.
- Attach translated labels to an existing object with a language tag.
Moral aspects Filled
- Errors in money, units or working time translate directly into wrong pay, prices or deadlines.
- Locale handling affects whether people can understand records in their own language.
Who is affected
- Employees paid by time records
- Customers and suppliers billed in different currencies
- Users reading localised content
Owners Filled
Steward
The curator of the meta-model catalogue who answers for shared types for units, money, locale and calendars.
Master systems
- Model registry
- Source configuration files
- Dependency lock files
- Policy store
Links to other meta-models Filled
references
- WM-XCT-008 - conceptual-candidate
- WM-XCT-010 - conceptual-candidate
- WM-XCT-031 - conceptual-candidate
- WM-XCT-032 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A unit is identified by its code in a named unit scheme, and a currency by its code in a named currency scheme.
- A calendar is identified by its identifier and version, and a time zone by its identifier in a named time zone database.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- A quantity or monetary amount carries a number and its unit or currency.
- A temporal value declares its type and any calendar or time zone context needed for interpretation.
- A localized label carries text, a language tag and a reference to the object it names.
- A range declares its endpoint values and whether each endpoint is inclusive, exclusive, unbounded or unknown.
- Typed values are distinguishable from bare numbers and formatted display strings.
Capabilities and actions required Filled
- Compatible values can be converted and compared using their declared interpretation and conversion basis.
- Calculations can be reproduced using the recorded rates and rounding rules.
Hazards and failure modes required Filled
- Silent unit or currency mismatches can corrupt totals.
- Incorrect daylight saving interpretation can shift civil-time intervals.
- Implicit rounding or floating point representation can lose precision.
- Reversing a quoted exchange rate can produce an incorrect converted amount.
- Confusing unknown and unbounded endpoints can change the meaning of a range.
Standards and interfaces optional Filled
- ISO 4217 from the International Organization for Standardization defines currency codes.
- Recommendation No. 20 from the United Nations Economic Commission for Europe provides codes for units of measure.
- The Unified Code for Units of Measure from the Regenstrief Institute provides machine-readable unit expressions.
- ISO 8601 from the International Organization for Standardization describes date and time representations.
- The Time Zone Database maintained by the Internet Assigned Numbers Authority provides time zone identifiers and transition rules.
- BCP 47 from the Internet Engineering Task Force defines language tags.
- The Common Locale Data Repository maintained by the Unicode Consortium provides locale data.
Context of use required Filled
- These types support records of quantities, prices, ranges, temporal values and multilingual names.
- Their interpretation affects finance, payroll, scheduling and cross-border operations.
Sources Filled
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
- W3C XML Schema Definition Language 1.1 Part 2: Datatypes - Checked live (HTTP 200) on 2026-10-07.
- BIPM: International System of Units (SI) - Checked live (HTTP 200) on 2026-10-07.
- Unicode Common Locale Data Repository - Checked live (HTTP 200) on 2026-10-07.
- IETF RFC 5545: Internet Calendaring and Scheduling Core Object Specification - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to preserve precision and the currency date?
- How to reconcile working calendars?
- How to distinguish a translated name from a new object?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-xct-06/brief.json, ver-cy/world-models/card-supplements/em-xct-06.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.