From fd08bae1c7ee70f2d9eceda6b1080b3a1b296a99 Mon Sep 17 00:00:00 2001 From: Hidde Beydals Date: Wed, 2 Nov 2022 15:46:33 +0000 Subject: [PATCH] RFC: reword summary Signed-off-by: Hidde Beydals --- rfcs/0005-artifact-revision-and-digest/README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/rfcs/0005-artifact-revision-and-digest/README.md b/rfcs/0005-artifact-revision-and-digest/README.md index 41d08bca..6e148681 100644 --- a/rfcs/0005-artifact-revision-and-digest/README.md +++ b/rfcs/0005-artifact-revision-and-digest/README.md @@ -13,12 +13,12 @@ Must be one of `provisional`, `implementable`, `implemented`, `deferred`, `rejec ## Summary -This RFC proposes to establish a canonical format for an `Artifact` which -points to a specific checksum (e.g. an OCI manifest digest or Git commit SHA) -of a named pointer (e.g. an OCI image tag or Git tag). In addition, it proposes -to include the algorithm name (e.g. `sha256`) as a prefix to any advertised -checksum in an `Artifact` and further referring to it as a `Digest` as opposed -to a `Checksum`. +This RFC proposes to establish a canonical `Revision` format for an `Artifact` +which points to a specific revision represented as a checksum (e.g. an OCI +manifest digest or Git commit SHA) of a named pointer (e.g. an OCI image tag or +Git tag). In addition, it proposes to include the algorithm name (e.g. +`sha256`) as a prefix to an advertised checksum for an `Artifact` and +further referring to it as a `Digest`, deprecating the `Checksum` field. ## Motivation