Event and setting fields
Explore sourced descriptions of events, places and conditions, and the claims that review them.
Context · object
Context 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 this document root.
Choose an entity type
7 alternativesEach entry in entities uses one type. Include only the types your material needs.
- EventEvent descriptions and connections to place and time.
- Reported objectReported appearance, behavior and contacts.
- PlaceLocations, terrain, airspace and proximity.
- PlatformObservers, stations, aircraft and vessels.
- EnvironmentConditions and links to ambient measurements.
- TemporalCalendar periods, relative dates and local clocks.
- CollectionCaptures, retention and declared alignment.
Document identity
5 fieldsSnapshots and descriptions
3 fieldsobservationRefobjectExact observation snapshot referenced by this context.Required3 nestedacquisitionRefobjectOptional exact acquisition snapshot for capture references.Optional3 nestedentitieslist of choiceTyped event, object, place, platform, environment, temporal and collection descriptions.Required7500 nested
How 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-context:0.1.0- Package export
@disclosureos/records/experimental/v2/context/schema/0.1.0
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.