Examples
Examples from published documents
- Evaluator organisations need domain verification and then manual approval by a CASRAI editor before their accounts can submit anything, while lab and regulator accounts become active on domain verification alone (NIKOLAI Mapping Declarations plugin v0.1.0, casrai_nikolai_decl_rest_verify()).
- declaration_type must be confirm, dispute or new; any other value, including corroborate, is rejected with an invalid_declaration_type error (NIKOLAI Mapping Declarations plugin v0.1.0, casrai_nikolai_decl_rest_submit()).
Counter-examples
Not to be confused with
- An approved evaluator account confirming a crosswalk row about its own published methods is not corroboration: it declares the evaluator's own mapping rather than independently checking another organisation's declaration.
Related terms
Related AI safety terms
Terms defined under this element that are not NIKOLAI elements themselves, each as the cited document uses it. Every term is also listed in the AI safety glossary.
- Validation (CRediT role)
- Validation, in the CRediT contributor taxonomy, is checking that results, experiments and other research outputs can be replicated or reproduced, whether that checking is part of the original work or done separately from it.
- Source: ANSI/NISO Z39.104-2022, CRediT, Contributor Roles Taxonomy, section 2.2
Source of record
Where this definition comes from
ANSI/NISO Z39.104-2022 (CRediT, Contributor Roles Taxonomy), Role definitions, Validation
“Validation: Verification, whether as a part of the activity or separate, of the overall replication/ reproducibility of results/experiments and other research outputs.”
https://www.niso.org/publications/z39104-2022-credit
Divergence
Where sources materially disagree
Structurally the closest of the six to an actual CRediT role: CRediT's Validation is defined as verification, independent of the original activity, of results and outputs — the same independent-check function this role performs for a declaration instead of a research result. The analogy is functional, not definitional: NIKOLAI is not reusing CRediT's Validation wording or scope, only its structural pattern of a distinct verifying party.
Gap
Not yet a distinct step in the submission form: declaration_type accepts only confirm, dispute or new, with no 'corroborate' value and no field linking one declaration to another it independently confirms. This is a stronger statement than "no corroboration has been recorded yet": there is currently no code path that could record one. Evaluator organisations can hold accounts (after domain verification and manual editor approval), but they file the same three declaration types as anyone else.
