Brandon Mitchell

> Wouldn't this concern only be an implementation concern? > We could easily say "the subject MAY NOT refer to a digest that exists in > the `layers`/`blobs`" or similar....

GC is one thing that probably doesn't like cycles, but this also applies to anything that recursively walks the graph. The purpose of referrers is to find artifacts that refer...

Can we close this as unplanned? We've managed to add logical loops into other parts of the spec, so that objection is no longer valid. But my question of how...

The artifactType field is [defined above](https://github.com/opencontainers/image-spec/blob/v1.1.0-rc5/manifest.md#image-manifest-property-descriptions): > This OPTIONAL property contains the type of an artifact when the manifest is used for an artifact. This MUST be set when config.mediaType...

I believe this is a duplicate of #1175. I'm curious if there's something outside of OCI happening that is causing the sudden attention on this?

> If I understood correctly, this requirement for Container images is related to making sure that the configuration in `mediaType.config` applied matches the layers that were set up in the...

Hi @SgtSilvio, I'm not a Java / Gradle / Kotlin dev, so this is out of my expertise. But that's not really needed to approve this. Do you have an...

I don't believe OCI disallows this behavior, so I'd say the Quay behavior is overly restrictive. The fact that a docker media type is a known media type would mean...

Part of the complication is the spec is written for multiple parties, the content producer, registry, and consumer. I think it makes sense for a registry to allow any descriptor...

At this point, I'm not sure there's anything for OCI to do here. I don't think it would be correct for OCI to mandate support for non-OCI media types. I...