First, we'll fix the description to actually be talking about unsolicited rather than solicited.  Second, we agree that wrapping data with Communication is not appropriate here.  We will replace this section on unsolicited communication with the different options covered by the data exchange decision tree - which includes allowance for simple RESTful POST/PUT, batch, transaction and bulk data, but also allows for the use of operations and messaging.  As yet, we haven't identified a need for unsolicited transmissions of data that wrap their information using Communication, but we will talk with the attachments (PIE) work group to understand their use and, if necessary, incorporate that into the decision tree and HRex as well.