Steve Lasker

+1 on splitting the annotations as strings and attach User may want to specific annotuonts on non-reference type artifacts

Thanks @FeynmanZhou Just to clarify, will the parameter be --manifest-annotation with or without the (s)? Would the CLI be: ``` oras attach acmerocket.azurecr.io/net-monitor:v1 \ --annotation "foo:bar" \ --annotation "something:true" ```...

As time yields on, developers automate, and we all recognize storage is: 1. not infinite 2. not free - someone pays 3. means I have old stuff that is insecure...

Are you asking for what the delete api would look like in the ORAS library and ORAS client? The current CLI: ```shell oras -h Usage: oras [command] Available Commands: help...

Thanks @Silvanoc, I think we're missing the generalization of what constitutes a layer in `oci.image.manifest` terminology. - In the OCI Artifacts terminology, a layer is persisted as a blob in...

Looks super interesting. Please open a PR for the proposal.

How an artifact is constructed should be left to the artifact author. Whether an artifact uses one more more files, or one more more blobs is really an implementation detail....

Thanks @gokarnm, The JWS format was a unique to notary implementation, as a placeholder, while we built on an existing standard. So, I'm not suggesting we change the `artifactType` when...

JWS was a placeholder, that we decided we needed to include, because we needed time to get security reviews of go-cose. I'm not suggesting we pull it out, rather just...

> The meaning of application/cose will be that every other client (different from Notary and not implemented according to the Notary specification) will be able to pull the signature and...