I hate to be THAT guy but someone was going to say it so it may as well be me :) This is a collection of patterns, right? Well why not make this really REST an

I hate to be THAT guy but someone was going to say it so it may as well be me :) This is a collection of patterns, right? Well why not make this really REST and rather than list a bunch of URL templates provide REL types for each of these like so: REL subscriptions-list -> GET subscription-create -> POST subscription-read -> GET subscription-update -> PUT subscription-destroy -> DELETE Now it doesn't matter what the URL structure is, I can pull the <link> elements from the page and be TOLD the URL, rather than follow a URL template. That way, this doesnt rely on out of band knowledge i.e this web page and its (poor) description.