Jon Johnson

> Do we see edge-level infrastructure and root-level infrastructure implementing the same APIs? I'm not sure what kind of topology you have in mind, but I think it's reasonable to...

> How can we define and agree on useful? By having this discussion. I can PR my proposal, if you'd rather do it on a PR, but it's all just...

> We just don't want to ship yet another API that doesn't get implemented because, ...we didn't capture the needs... Sure, here's the need, IMO: **All manifests in a registry...

I'm fairly opposed to adding `artifactType` anywhere, but assuming that lands, I think having `artifactType`-specific filtering ability isn't really the right approach. I'd prefer a generic way to filter by...

It would help me understand what's being proposed if you could revisit the [`OCI Artifact Manifest Properties`](https://github.com/opencontainers/artifacts/blob/3e34f029537052639eed59b469cb6c43706ac3d0/artifact-manifest.md#oci-artifact-manifest-properties) section a bit. I'd like to see a really rigorous description of these...

> The deck is here. Is this available in a less hostile file format? > filibustering sigh > Since it's a superset of image.manifest I don't believe you understand what...

> Initially, I had looked at content descriptors to describe things and their relationships. I do this all over the place, and it's a good pattern. The content descriptor is...

> Should we also consider recommending a unique pull/push correlation Id which corresponds to a logical operation from the client. I think non-standard headers like `X-Correlation-ID` serve this purpose already....

> seems to have narrowed the scope of cross-repository blob mounting @sargun I can't tell from the GitHub discussion -- was this an intentional narrowing?

I am a _little_ worried about giving the registry more visibility into blobs. Right now, they are completely opaque to the registry until you push a descriptor that references them,...