From 149a49e1b336c76fb2e1b521f2ca70c831209547 Mon Sep 17 00:00:00 2001 From: Tom Hennen Date: Wed, 16 Oct 2024 19:18:58 +0000 Subject: [PATCH] content: draft: clarify "in the present context" My read is that "the present context" is what branches or tags point at the given revision. Making that explicit. fixes #1138 Signed-off-by: Tom Hennen --- docs/spec/draft/source-requirements.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/spec/draft/source-requirements.md b/docs/spec/draft/source-requirements.md index 2da69f9af..ff5a5cf44 100644 --- a/docs/spec/draft/source-requirements.md +++ b/docs/spec/draft/source-requirements.md @@ -196,7 +196,8 @@ Activities conducted on the SCS SHOULD be attributed to authenticated identities ✓✓ Source attestations -A source attestation contains information about how a specific revision was created and how it came to exist in its present context. +A source attestation contains information about how a specific revision was created and how it came to exist in its present context +(e.g. the branches or tags that point, or pointed, at that revision). They are associated with the revision identifier delivered to consumers and are a statement of fact from the perspective of the SCS. If a consumer is authorized to access source on a particular branch, they MUST be able to fetch the source attestation documents for revisions in the history of that branch.