You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 15, 2024. It is now read-only.
Keys MUST be unique within this map, and best practice is to namespace the keys.
Keys SHOULD be named using a reverse domain notation - e.g. com.example.myKey.
We could use land.oras to reflect https://oras.land/
Or, we could ask CNCF to create a oras.cncf.io domain.
The thing I like about the cncf.io sub-domain is it would align with a DiD based identity provider.
The text was updated successfully, but these errors were encountered:
I wonder if it's necessary to define/require a org.cncf.oras.artifact.created annotation given org.opencontainers.image.created is defined. The ArtifactManifest spec uses the image-spec annotation rules to define valid annotation values. They carry essentially the same meaning, but the duplication suggests none of org.opencontainers.image.* annotations should be applied to an Artifact.
We've been using the logical namespace of
org.cncf.oras.*
but the image spec calls out a suggestion to use internet reverse namespace:We could use
land.oras
to reflect https://oras.land/Or, we could ask CNCF to create a oras.cncf.io domain.
The thing I like about the cncf.io sub-domain is it would align with a DiD based identity provider.
The text was updated successfully, but these errors were encountered: