This is an experimental schema, not yet tested in Orthogramic.
Definition
Integration schema alignment refers to enhancing the metamodel to natively align with the schemas, taxonomies, and ontologies used by integrated enterprise platforms—especially data platforms, process engines, project tools, and data catalogues.
Purpose
Improve semantic consistency between systems (e.g. same capability names in ERP and business architecture)
Allow semantic layer abstraction
Support schema-level interoperability and metadata lineage tracking
Key motivations
Reduce the need for custom mappings between the Orthogramic Metamodel and source systems
Enable real-time query federation and lineage tracing
Support automatic alignment between business architecture domains and enterprise data models
Implications for the metamodel
Extension area | Description | Example |
|---|---|---|
| Add | “Maps to Atlan:BusinessDomain” |
| Unique ID or label that can be matched across systems for capabilities, policies, etc. | Capability ID = “CRM_001” used in both Orthogramic and SAP |
| Relationship field for Information domain, showing origin and consumption of data assets | Data source: “CustomerDB”, used in Capability: “Customer Analytics” |
| Optional metadata alignment to terms in shared vocabularies (e.g. FIBO, APQC, ISO) | Value stream aligned to “ISO 9001: Design and Development” |
Implementation considerations
Integration schema alignment can be embedded in the JSON schema definitions using
$ref,externalMapping, orlinkedVocabularyfields.Cross-enterprise features may be modelled as extensions or overlays rather than changes to core domains—keeping the model lean and modular.