Abstracting payload across domains #105
Description
When an order is being fulfilled, there should be a schema that describes the physical description of an order if applicable. The abstracted name of this object should be called Payload. This is essentially useful in cascaded networks, where a logistics BPP agent is collecting the money on behalf of a retail BPP from the recipient of the package. in the case of mobility, the item being transported is a person plus additional luggage. In logistics, it is a delivery package. Is there a way to abstract this "entity" that is the "object" of fulfillment of an order. For service based BPPs, it should also reveal the details of the service being rendered during fulfillment. For example, in the case of home cleaning services, the package being given to the customer is not a physical package but a collection of activities performed by the Agent. Clearly there is a need for an abstracted object that represents the above.