Mike Brown

It's not a spec.. it's going to be a running reference with guidance... The samples will define the dependencies, such as versions of the image and distribution spec.

> Can we get released versions of artifacts? I would expect each artifact type to have versioning, releases, ... https://github.com/opencontainers/artifacts/blob/master/artifact-authors.md#defining-a-unique-artifact-type

> Without releases I can't tell its stability. Is this an experiment that might easily change or something that's stable with staying power? See here: https://github.com/opencontainers/tob/blob/master/proposals/artifacts.md#versioning--roadmap We would have to...

Quota implies authorization, which is generally out of scope for this iteration. However: ``` Authentication and authorization support: While authentication and authorization support will influence this specification, those details MAY...

> I'd like to distinguish that the WG is a project created under the OCI organization ok? > specifically for the purpose of extending the spec. However I'm hearing there...

.. sry about fat fingering your comment ^ > As a visitor to the page, I think it would be useful to distinguish that the WG is under the OCI...

> Similar to the distribution-spec, does it also make sense to add a conformance test when ready to cut a spec release? Yes, OCI has tried to do conformance for...

suggest creating an incoming or under-consideration path for artifacts in progress and an approved path for artifacts approved... this is more a common extension but I'd still put it in...

+1 on extension

other... @lachie83 's `subject` mention in slack drawing from proposal A... seems to me to make it very clear. Otherwise refers is fine let the documentation explain that it's the...