Claim-history fields
Search source statements, unassessed questions, assessed claims and their revision links in base claim history 0.1.0.
Claim history · object
Claim-history 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 history root. Use extensions for namespaced additional JSON.
Choose a claim shape
3 alternativesEach item in claims uses one of these three shapes. A source statement has no assessment status; an unassessed question has no outcome.
Document identity
3 fieldsObservation and claims
2 fieldsAdditional 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:claim-history:0.1.0- Package export
@disclosureos/records/experimental/v2/claims/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.