N0393 -

For more technical details on the standard's history, you can review the ISO/IEC JTC1/SC34 Document Register or the TMASD Application Definition . ISO/IEC JTC1/SC34 N0406

: Conformance to N0393 is often considered a matter of subjective human judgment rather than something easily verifiable by automated software alone. For more technical details on the standard's history,

: Efforts to "draft a piece" regarding N0393 often involve the Standard Application Model (N0396) . Alignment requires separating purely structural material from the material that defines higher-level semantics, like "Occurrence-ness". Drafting Considerations If you are drafting a piece to align

: Section 6 of N0393 describes how to define constraints and semantics for specific applications. A TMA definition uses the model's primitives to specify: For more technical details on the standard's history,

: One of the historical critiques of the N0393 draft was its lack of clarity on how the abstract model directly enables software-level interoperability.

If you are drafting a piece to align with or describe this model, your content should focus on these core structural and semantic principles: Core Concepts of the N0393 Reference Model

: Unlike some other syntaxes (like XTM) that allow for "lazy" references, the TMM requires reification to preserve integrity when maps are merged.