Observatory ProtocolNode registryEarth observation source
Earth observation source
A source of satellite or airborne Earth observation data, admitted by source manifest and release, and served onward through catalogues such as STAC.
- 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
Role
Data providers enter by manifest for a stated scope. (OBSP 0.1 §5.2) Archives are served through STAC. (OBSP 0.1 §5.10)
- Class
- Non-terrestrial and Earth observation
Satellite terminals and Earth observation sources. - Protocol role
PROVIDERProvider. (OBSP 0.1 §3)- Conformance profile
OBSP-PROVIDERHardware, software, model and data provider (OBSP 0.1 §7.1)- Technology domains
- Earth observation
Interfaces
The planes and bindings this type uses. Bindings are normative for OBSP 0.1; radio and link layers follow their own standards. (OBSP 0.1 §6)
| Interface | Binding | Sources |
|---|---|---|
| Admission | Source manifest and source release | (OBSP 0.1 §4.2; OBSP 0.1 §5.2) |
| Exchange | STAC for archives; OGC API for products | (OBSP 0.1 §5.10; STAC; OGC API) |
Schemas it emits and accepts
Each document is a JSON Schema 2020-12 contract. Open one in the schema explorer. (JSON Schema 2020-12) Every request, command and event also carries a request context. (OBSP 0.1 §4.3)
Emits
source-manifestSourceManifestsource-releaseSourceReleaseprovider-manifestProviderManifestsupply-chain-receiptSupplyChainReceiptprovenanceProvenance
Accepts
qualification-recordQualificationRecordrequest-contextRequestContext
Lifecycle and conformance
OBSP-PROVIDER 3 of 12 functions. (OBSP 0.1 §7.1) A level is reached only with the evidence it names. (OBSP 0.1 §7.2)
| Clause | Stage | In OBSP-PROVIDER | Contract |
|---|---|---|---|
| §5.1 | Join | No | Contracted |
| §5.2 | Admit | Yes | Contracted |
| §5.3 | Describe | Yes | Contracted |
| §5.4 | Time | No | Contracted |
| §5.5 | Observe | No | Contracted |
| §5.6 | Qualify | No | Contracted |
| §5.7 | Federate | No | Open gap G-FED-1 |
| §5.8 | Orchestrate | No | Open gap G-ORCH-1 |
| §5.9 | Correct | No | Contracted |
| §5.10 | Exchange | No | Open gap G-EXCH-1 |
| §5.11 | Prove | No | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | Yes | Contracted |
Conformance cases that apply
| Case | What it tests | Kind | Evidence |
|---|---|---|---|
| CT-PROVIDER-001 | Admit: provider manifest with supply-chain evidence | invariant | provider-manifest supply-chain-receipt |
| CT-PROVIDER-002 | Describe: source releases and model manifests | schema | source-release model-manifest |
| CT-PROVIDER-003 | Exit: the provider names a data export and replacement path | invariant | provider-manifest |
Run these cases in the onboarding check
Levels
- Declared
- Signed self-declaration naming profile, version and scope.
- Self-tested
- Conformance report (obsp conformance run) produced by the participant, with digests of the tested artifacts.
- Lab-tested
- Conformance report (obsp conformance run) and lab test record from a qualified lab.
- Qualified
- Lab report plus field observation for the declared scope and a qualification-record.
- Suspended
- Suspension notice with reason.
- Withdrawn
- Withdrawal notice.
Identity, attestation and security
Requirements of the security model that apply to this role. (OBSP 0.1 §8)
- Architecture
- Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
- Workload identity
- SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
- Supply chain
- SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (OBSP 0.1 §8)
- Privacy
- Observation data that can identify a person is a declared data class with its own policy; default is not to collect it (OBSP 0.1 §8)
Interoperability profile and standards
The primary standards this type draws on. Alignment with a standard is stated as alignment. It is not an approval by the standards body. (OBSP 0.1 §13)
- STACSpatioTemporal Asset Catalog specification(STAC)
- CEOS ARDCEOS Analysis Ready Data(CEOS ARD)
- CCSDS Blue BooksConsultative Committee for Space Data Systems recommended standards(CCSDS Blue Books)
- OGC APIOGC API family of standards(OGC API)
Not yet defined
What the protocol does not define for this type in version 0.1, stated as the specification states it. Nothing here is filled in from elsewhere.
The protocol lists no open gap for this type.
Across the consortium
Related pages on the consortium's other networks, in their own words.
- Standards
- Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.nexustandards.com
- Index
- Country risk indicators that observations with provenance and quality can inform.risksindex.com
- Academy
- Training for implementers and operators of observing systems.risksacademy.com
- Reports
- Published evidence with provenance, citation and corrections.nexustandards.com/nexus-reports
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §5.2: Admit Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.10: Exchange Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.1: Profiles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §4.2: Core objects Observatory Protocol 0.1 (draft), CC BY 4.0.
- STAC SpatioTemporal Asset Catalog specification stacspec.org/ Checked
- OGC API OGC API family of standards ogcapi.ogc.org/ Checked
- JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
- OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.2: Conformance levels Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
- CEOS ARD CEOS Analysis Ready Data ceos.org/ard/ Checked
- CCSDS Blue Books Consultative Committee for Space Data Systems recommended standards public.ccsds.org/Publications/BlueBooks.aspx Checked