Skip to content
View as Markdown

Core

IRI: https://w3id.org/altium/cdm/core

Holds the abstract foundations shared by every bounded context: the base classes Entity (specialised as Artifact and Activity), Resource and Event; the mixins that add annotations such as GRID, maturity and API type; shared slots such as id and name; and the abstract relations (e.g. part of, input of, derived from) that domain relations specialise. It is not a product area and has no product documentation of its own.

In the product

No public product documentation exists for this bounded context.

Entities

Name Description
Activity Abstract base for process and work objects — things that happen, use inputs, and produce outputs. Examples: projects, design reviews, design workflows.
Artifact Abstract base for persistent data objects that are created, stored, versioned, and consumed. Examples: components, documents, system models.

Base types and mixins

Name Description
Entity Abstract base for all identifiable, versioned, platform-accessible domain objects. Carries a GRID, maturity level, and platform API reference.
Event Abstract base for domain events. Events carry no GRID and no versioning lifecycle; they represent things that happened rather than persistent domain objects.
Meta Abstract base for all CDM mixin classes. Provides a common root for mixins without participating in the main Entity hierarchy.
Resource Abstract base for lightweight platform-accessible objects that have API access but are not Entities; they carry no GRID and no versioning lifecycle.
With GRID Mixin that adds a GRID annotation slot to a class.
With Maturity Mixin that adds a maturity annotation slot indicating the lifecycle readiness level.
With Platform API Mixin that adds API type annotations: platformAPI names the Altium 365 Platform API GraphQL type; nexarAPI names the Nexar (Octopart) GraphQL type for supply-chain entities served by Nexar rather than the Platform API.
With Vault Mixin that adds a vault content type annotation to a class, indicating how its content is stored in the platform vault.
With Vault Link Mixin that adds vault link parent, child, and type annotation slots for tracking hierarchical vault relationships.