Observation fields
Explore the fields, alternatives and constraints that make up an observation.
Observation · object
Record structure
Start with a top-level field, then follow its values and alternatives. The index stays available as you explore.
Required fields must be present. Lists may be empty unless a minimum is specified.
Extra fields: Not allowed at the observation root. Use extensions for namespaced additional data.
Identity and lifecycle
7 fieldskindstringIdentifies this document as an observation.RequiredschemaVersionstringThe observation contract version, separate from the npm package version.RequiredidstringA stable identifier for this observation.RequiredstatusstringWhere the record is in its publication lifecycle.RequiredcreatedAtstringWhen this record was created, separate from the time of the observation.Required4 nestedupdatedAtstringWhen this record was last updated. It cannot precede creation.Required4 nestedsummarystringAn optional description of the observation.Optional
Time and place
2 fieldsSources and measured values
7 fieldssourceslist of objectThe documents, testimony or instrument data on which the record draws.Required9 nestedproductslist of choiceRaw or derived data products. Native data stays in its own format.Required22 nestedmethodslist of objectDeclared methods and versions used for selection or processing.Required5 nestedframeslist of choiceCoordinate systems and vertical references used by positions and measurements.Required47 nestedassertionslist of choiceSource-specific statements about a time, position or measurement, with locators.Required321 nestedmeasurementslist of objectNamed quantities with a value, unit, uncertainty and source references.Required46 nestedprocessinglist of objectWho declared a processing step, which method was used, and its inputs and outputs.Required14 nested
Additional information
1 fieldHow to read this reference npm 2.0.0-beta.4
Required is local. A field marked required must exist in its containing object or selected alternative. A required list can be empty unless minItems says otherwise. Choose the alternative that describes your data; do not combine every alternative.
Structure and meaning are checked separately. These entries come from the published package. Explanations and grouping are editorial. Follow the validation guide for semantic checks such as unresolved references.
- Schema identifier
urn:disclosureos:experimental:observation:0.1.0- Package export
@disclosureos/records/experimental/v2/observation/schema
Repeated keys in different branches are separate schema entries. Their exact paths and field links preserve that context. The schema version is independent of the npm package version.