Witness and account fields
Explore people, distinct accounts, attributed reviews and the separate source-file checklist.
Witnesses & accounts · object
Witness and account 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
4 alternativesEach entry in entities uses one type. Include only the types your material needs.
Document identity
5 fieldskindstringIdentifies the document kind.RequiredschemaVersionstringThe document contract version.RequiredidstringA scoped document identity.RequiredrecordedAtstringWhen these declarations were recorded, separate from the event and account dates.Required4 nestedrecordedBystringWho assembled these declarations.Required
Snapshots and declarations
3 fieldsHow 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:research-entities:0.1.0- Package export
@disclosureos/records/experimental/v2/entities/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.