Transport: "combolining" proposal

combo-lining proposal. An evolved actions proposal with link-setting that relational data priority while allowing a clean way for extensions like transactional data
* Create representations have inlined resources like person.  This avoids composite update complexity
* when reading resources a standard HAL response representation is used where associated resources are linked and optionally _embedded
* when updating a resource with PUT or PATCH, only the attributes of the targeted resource are included.  Updating an associated resource must be done directly on that resource.
* Changing an association (say reassign a donation to a different person) is achieved by link relations like "osdi:set_person" on an individual donation resource
* Transactional data is cleanly layered in if the implementation supports it.  It is a separate resource that can be linked to and embedded in a donation resource retrieval
* Transactional data is created by the server.  The Create representation just contains 1 person information.  If the server supports transactional data, then it will create the donation_transaction resource.