Current packaging guidance uses Bundle profiles to establish expectations for delivery packages for artifacts. These profiles specify a bundle type of "collection". However, when using collection, fullUrl is required, and there is no guidance about what the value of that element should be, or how it would be expected to be used by consuming systems.

In addition, the use of "transaction" bundles is more aligned with the target use case of a "deployment" package.

Consider alternate approaches to expressing the constraints for the package, and provide better guidance about use of "transaction" as opposed to "collection" bundles for the purposes of distribution, especially how the request and/or fullUrl elements of the bundle are expected to be used by both by authoring systems from a packaging perspective, and implementing systems from a consumption/ingestion perspective.