---
title: "Questions and answers | Observatory Protocol"
description: "Plain answers, each from the text it cites."
url: https://nexusobservatory.com/knowledge/questions/
publisher: GCRI Canada
updated: 2026-11-18
---

1. [Observatory Protocol](https://nexusobservatory.com/)
2. [Knowledge](https://nexusobservatory.com/knowledge/)
3. Questions and answers

# Questions and answers

Plain answers, each from the text it cites.

Answers

## Common questions.

What is the Observatory Protocol?

The Observatory Protocol lets an instrument or computer that has never met the grid join it, prove what it is, keep time, publish what it measures with its metadata and quality, and be orchestrated, corrected, federated and finally retired, without trusting any single vendor, cloud or central service.

[Read the source](https://nexusobservatory.com/spec/)

Who stewards it?

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

[Read the source](https://nexusobservatory.com/governance/)

Under which licences is it published?

CC BY 4.0 · Apache-2.0

[Read the source](https://nexusobservatory.com/development/governance/#pol-ipr-and-licensing)

What is its status?

Observatory Protocol 0.1.0-draft is a draft specification. Any part of it may change before version 1.0, and until then a minor version may break compatibility.

[Read the source](https://nexusobservatory.com/governance/changes/)

What does a conformance claim mean?

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.

[Read the source](https://nexusobservatory.com/conformance/)

Does this site say an implementation conforms?

Nothing on this site states that an implementation conforms to it. A conformance claim states its tested scope and cites its evidence.

[Read the source](https://nexusobservatory.com/conformance/)

Which profiles exist?

OBSP-NODE, OBSP-SITE, OBSP-GRID, OBSP-PROVIDER, OBSP-CONSUMER

[Read the source](https://nexusobservatory.com/sdk/implementers/)

How do messages travel?

Control: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. Data, in the field: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. Data, site to upstream: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. Events: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. Exchange: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. Evidence: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. Telemetry: OpenTelemetry OTLP.

[Read the source](https://nexusobservatory.com/spec/wire-bindings/)

How can I check a document?

Check a document against its schema in your browser.

[Read the source](https://nexusobservatory.com/conformance/checker/)

How do I take part?

Propose a change, report a defect, review a draft.

[Read the source](https://nexusobservatory.com/contribute/)
