Offline device Catalogue

The thermostat, RGB lamp, door lock, metered power strip, irrigation controller and coffee machine examples provide authored models and conventional JSON Sample values for local development. Run the regression checks from the repository root.

cargo test --test device_catalogue

The private Rust runner invokes the existing Check plan CLI. Every case has an independent constraint or contract rationale and typed expectations for its native state, disposition, completion and Sample admission or comparison classification. Decisive diagnostics also require the expected source, effective and sample pointer relations. Every expected source acquisition remains visible, including deliberately failed acquisitions. Missing or unexpected source identities fail the runner. Case identities are checked once per plan. Missing, unused or duplicate expectations, unexpected or duplicate observed cases, host failures and malformed or unavailable reports fail the test with the device, variant and case identified where available.

An intentionally rejected Sample retains its native failed disposition and CLI exit 1. It passes the regression test when those results were expected. Completion is checked separately, including the limited thermostat’s known rejection alongside unavailable calibration meaning. Small controlled records exercise identity accounting, and altered admission, completion and diagnostic expectations demonstrate named failures.

These are supplied descriptions and values. They establish neither physical device behaviour nor network protocol interoperability. Each value is checked against its selected data description. No stateful device engine or interaction-sequence assertion is involved. The native meanings follow ADR 0003, Check findings and completeness, ADR 0004, Supplied catalogues and checking scope and ADR 0016, Selected samples with explicit admission and coverage.

Direct Check plans

cargo run -- check --plan examples/thermostat-check/minimal-plan.json --format json
cargo run -- check --plan examples/thermostat-check/rich-plan.json
cargo run -- check --plan examples/thermostat-check/limited-plan.json --format json
cargo run -- check --plan examples/rgb-lamp-check/rich-plan.json
cargo run -- check --plan examples/door-lock-check/rich-plan.json --format json
cargo run -- check --plan examples/power-strip-check/rich-plan.json --format json
cargo run -- check --plan examples/irrigation-check/rich-plan.json --format json
cargo run -- check --plan examples/coffee-machine-check/rich-plan.json

The minimal and rich variants of each family complete Initial Catalogue and Full selected-model checks. Their plans exit 1 because they contain intentional sample rejections. The rich lock plan also compares the minimal lock with the rich one. Both breaking changes are acknowledged, so that case passes with a breaking classification. The limited thermostat combines an invalid bound and missing dependency. Its model checks fail and remain incomplete. Its two undetermined samples and independently rejected sample also remain incomplete.

The limited lamp has only unavailable calibration meaning. Its model and sample cases are undetermined and incomplete, and its plan exits 3. The limited lock combines an invalid numeric bound with an unsupplied credential definition. Its plan exits 1, with failed incomplete model checks, an undetermined credential sample and an admitted complete state sample. Model findings remain distinct from selected-sample admission.

The power strip supplies three supported variants and one limited variant. Its rich model imports repeated outlets and shared meter definitions from an explicitly supplied second document. Its separate copied-requiredness plan imports an Object that requires its own declaration through an absolute pointer, and the copied requirement relocates to the importing outlet under ADR 0036, Copied reference relocation, so that plan exits 0. Its missing plan records the failed acquisition of a needed local dependency and exits 3 while preserving complete independent Sample admissions.

The limited irrigation and coffee models need unsupplied optional calibration meaning. Their model checks are undetermined and incomplete. Samples with absent optional calibration are admitted completely. Present calibration keeps applicable child work incomplete, while a missing required zone array or excessive servings still gives an independent rejection. Both plans exit 1.

All ordinary runs are offline and use existing finite allowances. The plans retrieve nothing and change no input bytes. Copy the complete directory for any family elsewhere, then pass the copied plan path to esdieff check --plan. All sources resolve relative to that plan. The Rust suite repeats every device plan from a temporary copy and checks that the original and copied bytes remain unchanged.

Device and constraint coverage

There are 19 model variants and 116 distinct Sample cases across 20 plans. The thermostat provides three variants and 20 cases, the lamp three variants and 16 cases, the lock three variants and 17 cases, and the power strip four variants and 22 cases. Irrigation adds three variants and 21 cases, and coffee adds three variants and 20 cases. The preserved thermostat entry plan shares the minimal model. The matrix lists actual cases rather than potential capabilities. Sample areas use the existing esdieff.sample/1 inventory from the Sample contract.

These families exercise all five selectors through Property, sdfData, Action input, Action output and Event output. Irrigation exercises Sample-array counts, text-element uniqueness and authored zone identifier patterns. These patterns are ordinary text constraints, rather than URI or UUID format checks. Repeated outlet declarations are model components rather than Sample-array checks. Nullability, presence, enum, Choice and temporal cases here do not claim exhaustive combinations.

Sources and adaptations

All thermostat models and samples are authored for this repository and use its MIT or Apache-2.0 licence. No external device document, vendor data, simulator implementation or historical SDF dialect is imported.

The minimal Catalogue reuses the existing thermostat.sdf.json without changing it. The entry plan.json, comfortable.json and too-hot.json also remain unchanged. The rich variant adds a nullable current reading, half-degree target steps, a configuration Action and an alarm Event. The limited variant is newly authored to demonstrate a faulty bound and unsupplied calibration definitions. Its namespace uses the reserved example.test domain as an identifier and is never retrieved. The Count examples remain a separate entry workflow.

The lamp and lock adapt interface ideas from the same pinned One Data Model playground revision used by the external-model pilot. Their lamp source notes and lock source notes identify the original documents, metadata, copyright notices and unchanged BSD licence text alongside the newly authored constraints, models, plans and samples. Historical source documents and their absolute required declarations are not imported into the standalone examples.

The power-strip source notes record the RFC composition ideas and the pilot’s pinned Binary Switch source with its original notice and licence. The meter definitions, exact readings, product override and distinguishing limitation variants are newly authored. No original external corpus needs to be downloaded or rerun. Its failed-dependency source expectations are checked explicitly, including a regression check that rejects hidden failed or successful acquisition attempts or a fabricated acquisition success.

The irrigation source notes identify newly authored examples and the recorded RFC array, map and Choice rules. The coffee-machine source notes pin Eclipse Thingweb’s interface ideas and original licence notice. Coffee resource readings and brew results are re-expressed as SDF with authored presence constraints, recipes and maintenance data. No simulator code, protocol forms, scheduling behaviour or upstream defaults are imported.