This change corresponds with
https://github.com/opencontainers/image-spec/pull/999 as we reconcile changes needed to allow referrers API (subject field and artifactType field responses) to function smoothly on image-manifest.
Personal take on this:
After excesive extensive deliberation, that while it would be nice to have a clean-break to work with a generic manifest, we would be setting ourselves and the whole ecosystem up for the compatibility challenges similer to Docker schema 1 -> schema 2 -> OCI v1.
The biggest value for the community and ecosystem is to provide guidance on how to use the available data structures and APIs to already accomplish the same use-cases in the most broadly compatible way.
sajayantony
commented
1 year ago
This change corresponds with https://github.com/opencontainers/image-spec/pull/999 as we reconcile changes needed to allow referrers API (
subjectfield andartifactTypefield responses) to function smoothly on image-manifest.Personal take on this: After
excesiveextensive deliberation, that while it would be nice to have a clean-break to work with a generic manifest, we would be setting ourselves and the whole ecosystem up for the compatibility challenges similer to Docker schema 1 -> schema 2 -> OCI v1.The biggest value for the community and ecosystem is to provide guidance on how to use the available data structures and APIs to already accomplish the same use-cases in the most broadly compatible way.
Signed-off-by: Vincent Batts vbatts@hashbangbash.com