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 Is that list public?
1
@stilkov @dret i covered most of them (not RAML) in my @RESTFest talk last month: vimeo.com/75106815 Note i was pretty sick that day ;<

REST Fest 2013 \ Mike Amundsen

This talk covers the Application-Level Profile Semantics or ALPS (2013) IDL format. ALPS is designed to describe problem domains in ways that allow both client…

vimeo.com
2
5
@stilkov here's a tweet thread from August on Web IDLs: nitter.vloup.ch/mamund/status/36… it's already out-of-date! /cc:@dret
Mike Amundsen @mamund@mastodon.social @mamund
13 Aug 2013
WebIDL 2001-2013: WSDL, AtomSvc, WADL, Swagger, RESTDesc, ioDocs, APIBlueprint, JSON-Home, RSDL, JSON-HyperSchema. what can we learn here?
1
Replying to @mamund
@mamund @dret Interesting to see you included json-home in that list. Might have misunderstood it, but consider it a purely runtime thing

Oct 3, 2013 · 10:24 PM UTC

3
Replying to @stilkov
@stilkov yep, i also left out google's discovery format. while both are touted as runtime i've yet to see clients negotiate them. /cc:@dret
Replying to @stilkov
@stilkov @dret here are the slides from my @RESTFest talk (the video doesn't handle my slide display very well ;) g.mamund.com/hmhry
3
Replying to @stilkov
@stilkov you're right, #JSON home (and its #XML sibling) are pure runtime formats. design time info: start with a #URI and GET a homedoc.