Aleksa Sarai

Another issue with the current way of representing compression is that the ordering of multiple media type modifiers (such as compression or encryption) isn't really well-specified since MIME technically doesn't...

@stevvooe Can you explain how a tool like `umoci` should handle the following `index.json`? ``` { "schemaVersion": 2, "manifests": [ { "mediaType": "application/vnd.oci.image.manifest.v1+json", "size": 7143, "digest": "sha256:e692418e4cbaf90ca69d05a66403747baa33ee08806650b51fab815ad7fc331f", "annotations": { "org.opencontainers.ref.name":...

@qianzhangxa Two levels of indirection give you many benefits -- the most obvious of which is that you can have multiple tags that reference the same multi-architecture image. And the...

@qianzhangxa Sorry, I misspoke. What I meant was (and if you look at my example you'll see what I mean) was > the most obvious of which is that you...

@stevvooe But we **do** define what are valid values for annotations. Annotations in the `org.opencontainers.*` namespace are reserved by us and we have the right to specify how they should...

And to make the point more clear, the current CAS interface for `umoci` is this: ```go // Engine is an interface that provides methods for accessing and modifying an //...

@qianzhangxa **It isn't a benefit, my point is that the current system allows this and it shouldn't.** That's what this issue is about, removing this ambiguity.

@qianzhangxa I misspoke in that comment, and I corrected it [here](https://github.com/opencontainers/image-spec/issues/581#issuecomment-282438998). Sorry for any confusion.

@stevvooe > Where are you getting this requirement from? Collect the references and re-process them. Or, use the visitor pattern and pass in a function that does what you need....

@stevvooe I still don't see why this dereference walk: ``` ImageIndex[with same tag pointing to multiple manifests] -> Manifest -> ... ``` Is a good feature when this would be...