Handling different media types

[mstade]

From @mstade on August 9, 2014 17:38

As we start fleshing out the client APIs and transformation functions like to, we'll inevitably run into issues with different media types. We can talk about hypermedia in a type-agnostic way -- @mamund does that very well through the use of his H-factors -- and we probably need to figure out a way for these transformation functions to work across media types.

A thought I have on this is that we could create protocols for different affordances, and a media type protocol. To implement support for a new media type would then mean extending these protocols with the relevant functionality. Functions such as to and submit would then use these protocols to define their semantics in a media type agnostic way.

More on this issue later..

Copied from original issue: sammyt/nap#15