Why Source Provenance Belongs in Every Design Reference Library
Preserve where a design reference came from, what was captured, and how your notes derive from it so evidence remains useful and auditable.
Direct answer
Source provenance records where a reference came from, who published or created it, when and how it was captured, and which later notes or decisions derive from it. That chain helps teams verify claims, revisit context, credit sources, detect stale evidence, and distinguish observation from interpretation.
Provenance is the history of the evidence
The W3C PROV model describes provenance through entities, activities, and agents: a thing, what happened to it, and the people or systems involved. A lightweight design-reference record can borrow that shape without implementing the full ontology. The source page or image is the entity, the capture is the activity, and the creator, publisher, or collector is an agent.[1]
This history answers practical questions. Is the reference still available? Was the note based on the live page or a cropped screenshot? Who published it? Which project principle cited it? Without those links, a folder of images gradually loses context and confident claims become difficult to audit.
Keep source, annotation, and derived decision distinct
The W3C Web Annotation model represents an annotation as a relationship between a body and a target. That separation is valuable for design work. ‘The checkout keeps the cost summary visible’ is your observation; the dated page or screenshot is its target. ‘Our checkout should keep the summary visible above the payment action’ is a later design decision derived from both evidence and project constraints.[2]
- Source: canonical URL or other stable identifier.
- Authorship: creator, studio, publisher, or account when available.
- Capture: date, method, viewport or state, and fidelity label.
- Annotation: what the collector observed and why it matters.
- Derivation: the brief claim, token candidate, or decision that used it.
Provenance is not permission
Attribution and provenance help identify a source, but they do not automatically provide permission to copy, republish, train on, or redistribute material. Archives and collections set their own access and rights conditions. The Library of Congress, for example, distinguishes access to archived material from responsibility for assessing rights and restrictions.[3]
Keep private references private by default, avoid publishing captured assets merely because their URLs are public, and consult appropriate legal guidance for a specific reuse. This article describes information hygiene, not legal advice.
A minimal provenance record makes restraint easier. It lets a system expose a citation or source link while keeping a private local asset behind its original access boundary.
Questions designers ask
What is the minimum provenance for a design reference?
Keep the original URL or identifier, creator or publisher when known, capture date and method, and the reason or claim for which you saved it.
Does crediting a source make reuse legal?
No. Attribution and permission are different. Rights depend on the material, jurisdiction, licence, and intended use; obtain specific advice when needed.
Sources checked
- PROV-O: The PROV Ontology — W3C
- Web Annotation Data Model — W3C
- Rights and access for the Library of Congress Websites Web Archive — Library of Congress