Annotations should keep enough context to survive reuse

Annotations should keep enough context to survive reuse. A highlight or comment may make sense beside the original page, but become unclear when copied into a note, index, or summary.

The W3C Web Annotation Data Model describes a standard model for annotations that can be shared between systems and reused without loss of significant information. That goal maps directly to everyday source work. A useful annotation should not only say “important” or “supports this.” It should identify the target passage, the reason it matters, the claim it supports, and any boundary that limits reuse.

A durable annotation can include four pieces: target, motivation, checked date, and reuse note. The target says which part of the source matters. The motivation says whether the annotation is defining, correcting, questioning, summarizing, or warning. The checked date says when the reader confirmed it. The reuse note says how far the source can be carried into another page.

This is useful for documentation, policy pages, research notes, public data summaries, and travel or product guides. If annotations are later gathered into a route, wiki, or digest, the context must still be readable without reopening every original tab.

The practical test is simple: if someone sees the annotation next month, can they tell what claim it supported and what it did not support? If not, the annotation is too thin for reuse.

Annotations should keep enough context to survive reuse

// COMMENTS

ON THIS PAGE