Skip to content

Build against open schemas.

Everything an implementer needs, in the order it is needed: the schemas, a checker that runs in your browser, quickstarts for validation and the conformance suite, and the wire binding of every plane. Code is licensed under Apache-2.0.

Wire bindings
7
Profiles
5
Code
Apache-2.0

Path

From the first schema to a conformance claim.

  1. Read the schemasEvery object as an open JSON schema, explored field by field.
  2. Check a documentCheck a document against its schema in your browser.
  3. Run the quickstartsValidate, run the conformance suite, read the bindings.
  4. Pick a profileWhat each kind of implementation provides.
  5. State your claimProfiles, levels and the evidence each needs.

API reference

The wire binding of every plane.

PlaneBinding
ControlTLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
Data, in the fieldMQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
Data, site to upstreamAt-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
EventsEvent envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
ExchangeOpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.
EvidenceDSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
TelemetryOpenTelemetry OTLP.

Profiles

What each kind of implementation provides.

ProfileFunctionsFor
OBSP-NODEJoin, Describe, Time, Observe, Qualify, Orchestrate (apply), ExitNode agents and devices
OBSP-SITEOBSP-NODE plus Admit (local), Orchestrate (plan), Correct, Prove (verifier)Site controllers
OBSP-GRIDOBSP-SITE plus Federate and ExchangeCluster and grid control planes
OBSP-PROVIDERAdmit, Describe, ExitHardware, software, model and data providers
OBSP-CONSUMERExchange, Correct (subscribe)Applications reading products

Tools

Tools that run in your browser and on your machine.

Schemas

Every object of the protocol, as an open JSON schema.