Profiling bundle for this purpose seems problematic since the number of artifacts in a specification could easily exceed typical page size and bundle size limits of servers. Consider defining a profile of Library (US Public Health Specification Library, US Public Health Supplemental Library, eRSD Specification Library, eRSD Supplemental Library) as an asset-collection using composed-of slices to describe the contents of the specification, and a $package operation to support retrieval of the contents of the specification as a Bundle. This will lend itself better to server-side paging implementations where Bundle is a paging wrapper rather than a content wrapper.