Question: Affordances or web link relations for modeling your API?
I have been pondering this question a lot lately. Given a resource and its attributes (semantic descriptors), would you model the API using the link / relations or resource affordances? May one relation as defined by RFC5988 Web Linking imply multiple affordances? For example does the
edit relation represents three affordances (retrieve, update, and delete)?
Is (should?) the perspective affordances vs. relations differ based on the point of view (API design, client, server).