Acquisition and binding fields
Search equipment, configuration, capture and measurement-link fields. Choose a document to explore its structure.
Equipment & captures · object
Acquisition 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. Use extensions for namespaced additional data.
Document identity
3 fieldsEquipment and configuration
3 fieldsinstrumentslist of objectPhysical equipment identities, including explicitly unknown identities.Required11 nestedmanifestslist of objectPinned configuration revisions, their artifact declarations and available channels.Required43 nesteddeploymentslist of objectWhere and when equipment was deployed with a particular configuration.Required35 nested
Calibration and capture
3 fieldscalibrationslist of objectChannel-specific calibration declarations, validity periods, reports and review state.Required95 nestedacquisitionslist of objectCapture sessions: configuration, deployment, clock context and active channels.Required89 nestedproductslist of objectRaw artifacts linked to the acquisition that produced them.Required11 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:acquisition-context:0.1.0- Package export
@disclosureos/instruments/experimental/v2/acquisition/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.