The Atom Publishing Protocol is still a very good example of a #reallyrestful “API” spec ietf.org/rfc/rfc5023.txt
Oct 4, 2013 · 6:33 AM UTC
2
7
9
@prushforth No standard I’m aware of, but maybe do a GET to retrieve a form with the valid search criteria? HTML is usually a nice guidance
@prushforth I agree. It probably would have happened had the uptake been stronger
@prushforth Essentially that’s what I’m saying, yes :-) A URI template sent in a response is essentially a GET form
@prushforth Atom/AtomPub lacks a number of inline H-Factors. essentially all writes and queries require human-readable description @stilkov
@prushforth RFC6570 can help w/ describing reads (LT) inline, but not writes (LI, LN). and supporting transclusions (LE) is weak. @stilkov
@stilkov Atom is the best example, IMO. Now let's enumerate the loosely coupled, user facing 'HATEOAS' apps going more than one link deep
