Since the set of Product data transactions have the largest number of individual transactions (seven), we'll start with those in the hopes that they will expose any gaps in the design sooner rather than later. Each transaction ties back to one of the original iteration stories, and the specific story that relates to the transaction process will be called out. The specific implementation of to_message_data for the user/object combination will be defined in the first transaction for that combination, and refined if/as needed in subsequent transaction details. Any other specific needs for that particular combination will also be addressed.
Since all of the varied operations against any objects require the object to be identified, the one constant in all to_message_data outputs is the oid property of the object being transmitted. It plays a significant...