Skip to content

Observatory Protocol 0.1 · open specification

The open protocol for shared observation.

How an instrument that has never met the grid joins it, proves what it is, keeps time and publishes what it measures, with provenance, uncertainty and quality on every value. Open to every implementer, changed in public.

Version
0.1.0-draft
Status
Draft specification
Specification
CC BY 4.0
Code
Apache-2.0
Steward
GCRI Canada
Source
obsp-0.1-foundation
OBSP0.1Join01Admit02Describe03Time04Observe05Qualify06Federate07Orchestrate08Correct09Exchange10Prove11Exit and decommission12

Six ways in

Start where your work is.

Read the protocol from the side you meet it: where it is applied, how it is built, how it runs, how to implement it, who takes part and how to learn it.

  1. Applied

    Every sector, industry and use case, read as the functions, objects and evidence it needs.

    Sectors
    13
    Industries
    21
    Use cases
    25
  2. Technical

    Architecture, data model, interfaces and conformance: the contract every implementation keeps.

    Functions
    12
    Objects
    41
    Domains
    16
  3. Operational

    Deployment, operation and assurance, each step entered on evidence and recorded.

    State machines
    12
    Flows
    12
  4. Developers

    Schemas, the conformance checker, SDK quickstarts and the wire bindings of every plane.

    Wire bindings
    7
    Profiles
    5
  5. Ecosystem

    Implementers, adopters and the open governance that changes the protocol in public.

    Participants
    33
    Open standards
    48
  6. Knowledge

    Guides, explainers, a glossary and plain answers, each tied to the clause it explains.

    Courses
    4
    Topics
    8

Applied

One protocol across every sector.

Each sector runs its own scenarios; each scenario uses the same functions, objects and evidence.

All industriesAll use cases

Technical

From first contact to retirement, function by function.

Each function moves named objects between named participants and is drawn against open standards.

  1. JoinA node proves what it is, receives an identity and a policy, then a signed plan.
  2. AdmitProviders enter by manifest, rights, security and technical review, for a stated scope.
  3. DescribeEvery instrument and observation carries what, where, how and by whom.
  4. TimeOne time base across the grid, with time quality as explicit state.
  5. ObserveStreams and files move over whatever link the site has, with store and forward.
  6. QualifyQuality flags, calibration and provenance travel with each value.
  7. FederateNodes form cells, cells form clusters, and clusters federate across trust domains.
  8. OrchestrateSoftware, configuration and upgrades roll out by signed plan, with evidence for every change.
  9. CorrectAn upstream correction marks dependants stale, triggers recompute and publishes a new version.
  10. ExchangeGoverned products reach people and applications through versioned APIs, events, maps and exports.
  11. ProvePeers answer unpredictable challenges and emit signed proof receipts for an independent verifier.
  12. Exit and decommissionEvery material provider has an open export and replacement path, and decommissioning closes the record.

Read the functionsTechnical overview

Interfaces

One binding per plane, each an open standard.

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.

Wire bindingsSchemas

Assurance

Conformance is a tested scope, stated with its evidence.

  1. Declared
  2. Self-tested
  3. Lab-tested
  4. Qualified

A level is reached only with the evidence the profile names, produced by the open conformance tool or a qualified laboratory. "Conformant" describes a tested scope only; it never means an outside body has approved it.

ConformanceCheck a document

Open standards

Composed from open standards.

The protocol names the standard it uses for each part and adds only what none of them covers.

Protocol of protocols

One protocol over the protocols that already work.

It replaces none of the standards that carry signals, time, identity and data. It binds them with common rules for identity, time, provenance, quality and governance.

Explore the stack

Across the consortium

Built with the networks of the consortium.

Each network relates to the protocol in its own way. Each is quoted from its own public page.

Ecosystem

Open to every implementer, changed in public.

Protocol development is stewarded by GCRI Canada, lead organisation of the Nexus Consortium.

Specification
CC BY 4.0
Code
Apache-2.0
Version
0.1.0-draft