The current approach to manifests involves a single manifest with all version binding information in the manifest for all the artifacts in the collection. However, there are cases where it makes sense to provide version binding information per artifact within the same collection. Allow for this possibility by allowing an artifact collection to include either the artifact or a manifest for the artifact as the component.

This will mean that artifact processing will need to account for the additional layer of indirection, each component may be either an artifact, or a manifest for the artifact.

Note that this use case is focused on communicating version binding for artifacts as part of release, this is not an authoring use case.