Sad to see the “RESTful API Modeling Language“ isn’t. raml.org
1
6
9
#RAML indeed cements the "let's call this #URI" anti-pattern ; maybe useful for RPC-via-HTTP, but certainly not #REST. / via @stilkov
1
1
@dret I've added this to my growing list of "description" formats. i have 12 so far. sadly all are URI-centric & instance-based @stilkov
5
2
@mamund @dret @stilkov Agree with the sentiment but believe these IDLs exist because non-procedural ReST clients are hard and extremely rare
2
@dfeist i would say creating hypermedia clients is _different_ but not hard. and yes, they are still rare. @dret @stilkov
2
@mamund the hardest part of hypermedia is that "APIs" disappear as strictly separate things; your API is the web of resources you're using.
1
2
@dret i agree. w/ hypermedia controls as the programmable interface, common thinking about "APIs" doesn't always apply. a mental model shift
1
@mamund @dret @dfeist @stilkov I spent most of this chapter chimera.labs.oreilly.com/boo… on building hypermedia clients.Would love any feedback.
3
2
5
Replying to @darrel_miller
@darrel_miller @mamund @dfeist @dret Wow! Great stuff! Will have to give it a more thorough reading before commenting, though

Oct 9, 2013 · 7:24 PM UTC