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
@mamund @dret @stilkov That said, it's a shame these IDLs ignore hypermedia, links and resource relationships.
1
@dfeist @leonardr and i are working ALPS (alps.io) a description format that focuses on hypermedia w/o URLs @dret @stilkov
1
@mamund @leonardr @dret @stilkov Any mock impl/example anywhere? Also, how do you see ALPS compares with Hydra (markus-lanthaler.com/hydra/)?
4
1
Replying to @dfeist
@dfeist AFAICT, only @mamund’s ALPS is independent of wire format @leonardr @dret

Oct 9, 2013 · 3:45 PM UTC