There has been discussion on and off in the community about expanding STIX to include a <STIX_Packages> element wrapper around one or more <STIX_Package> elements. The intent here would be to allow the <STIX_Package> to take on the role of representing a single report and allow the <STIX_Packages> element to serve as a root node to enable specifying multiple packages (reports). This could be implemented in several different ways however, taking into considerating:
- Can STIX constructs belong to more than one report?
- Can STIX constructs belong to no reports?
- What metadata about a report do we want to capture? Anything beyond what's in STIX_Package now?
- Where would you want to specify handling and supported profiles?
- Etc.