docs: replace asset annotations with OCI ownership referrer#142
Open
piotrjanik wants to merge 5 commits into
Open
docs: replace asset annotations with OCI ownership referrer#142piotrjanik wants to merge 5 commits into
piotrjanik wants to merge 5 commits into
Conversation
piotrjanik
changed the title
<!-- markdownlint-disable MD041 --> Updates §6.3 of the OCI storage backend spec to trace assets to their owning Component Version via a separate *ownership referrer* manifest (linked through the OCI `subject` field), instead of mutating the artifact with annotations. This matches ADR 0015 and keeps the artifact's digest and any existing OCI signatures intact. - Defines the referrer manifest (artifact type `application/vnd.ocm.software.ownership.v1+json`, empty config/layer, same repository as the artifact) and discovery via the OCI Referrers API with tag-schema fallback. - Rewrites integrity (§6.3.2) and verification (§6.3.3) around the referrer; drops the obsolete `software.ocm.base.digest` annotation and the `ociArtifactDigest/v1` annotation-stripping normalization. - Requires referrers to travel with the artifact across registries and OCI Image Layouts. <!-- Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes: open-component-model/ocm-project#1031 Signed-off-by: Piotr Janik <piotr.janik@sap.com>
Author
|
Approval needed from TSC |
piotrjanik
changed the title
Contributor
|
/vote |
Skarlso
previously approved these changes
Jun 8, 2026
frewilhelm
dismissed
Skarlso’s stale review
Before merging this PR we need to find out how the GC handles referrers
Author
|
Regarding Garbage Collection: |
Member
|
I think the garbage collection behavior should be part of the spec |
jakobmoellerdev
previously approved these changes
Jun 15, 2026
Skarlso
previously approved these changes
Jun 16, 2026
Contributor
|
Look okay, @piotrjanik can you please sign the commit? :) |
frewilhelm
reviewed
Jun 18, 2026
Signed-off-by: Piotr Janik <piotr.janik@sap.com>
frewilhelm
approved these changes
Jun 19, 2026
Skarlso
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates §6.3 of the OCI storage backend spec to trace assets to their owning Component Version via a separate ownership referrer manifest (linked through the OCI
subjectfield), instead of mutating the artifact with annotations. This matches ADR 0015 and keeps the artifact's digest and any existing OCI signatures intact.application/vnd.ocm.software.ownership.v1+json, empty config/layer, same repository as the artifact) and discovery via the OCI Referrers API with tag-schema fallback.software.ocm.base.digestannotation and theociArtifactDigest/v1annotation-stripping normalization.Fixes: open-component-model/ocm-project#1031
What this PR does / why we need it
Which issue(s) this PR is related to