Module model 

Domain models — layer 4 of ADR-0008.

Vocabulary follows CONTEXT.md: Project, DataModel, ResourceType, Resource, Field, Value, ValueType, BuiltIn. DSP-API wire types (OntologyDto etc.) live in crate::client, not here. See docs/dev/domain-language.md.

Re-exports

pub use auth::LoginResponse;

pub use data_model::DataModel;

pub use data_model::DataModelDetail;

pub use data_model::ResourceType;

pub use data_model::ResourceTypeSummary;

pub use dump::CreateDumpOutcome;

pub use dump::DumpStatus;

pub use dump::DumpTask;

pub use project::DataModelSummary;

pub use project::Project;

pub use project::ProjectDescription;

pub use project::ProjectDetail;

pub use project::ProjectRef;

pub use project::ProjectStatus;

pub use resource::DatePoint;

pub use resource::DateValue;

pub use resource::FieldValues;

pub use resource::FileValue;

pub use resource::ResourceAccess;

pub use resource::ResourceDetail;

pub use resource::ResourcePage;

pub use resource::ResourceSummary;

pub use resource::ResourceVisibility;

pub use resource::Value;

pub use resource::ValueContent;

pub use resource_type::Cardinality;

pub use resource_type::Field;

pub use resource_type::Representation;

pub use resource_type::ResourceTypeDetail;

pub use resource_type::ValueType;

pub use structure::DataModelStructure;

pub use structure::Relation;

pub use structure::RelationKind;

Modules

auth

Authentication domain shapes — shared across the client → action boundary.

data_model

Data-model domain shape — shared across the client → action boundary.

dump

Dump domain shapes — shared across the client → action boundary.

project

Project domain shapes — shared across the client → action boundary.

resource

Domain model for resource instances — ResourceSummary, ResourcePage, ResourceDetail, ResourceVisibility, ResourceAccess, FieldValues, Value, ValueContent, DateValue, DatePoint, and FileValue.

resource_type

Resource-type domain shape — shared across the client → action boundary.

structure

Data-model structure domain shape — shared across the client → action boundary.