Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderI dont understand what the purpose of this is. I thought the whole point of REST is that it is discoverable at runtime. If you have an "API Spec" doesnt that mean the server owner is now beholden to that spec; that changes to their resources would break compatability with any client written to conform to the spec? I thought everything you needed to write a REST API client is included in the media-type specification and the rel profile? For…
I wrote a Python parser for this called RAMLfications (https://ramlfications.readthedocs.org/en/latest/) I actually built the API console for my company - Spotify (https://developer.spotify.com/web-api/console/) - based off of RAML and am in the process of open sourcing the tech behind it. The first bit being RAMLfications, and the second, called Griffin (https://github.com/spotify/griffin) is a super alpha version of a static doc generator based off of RAML. The next/last bit to open source is the console itself…
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 178
- Total comments
- 112
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2013-10-02 | RAML - RESTful API modeling languageFirst breakout · Best thread | DanI-S | 94 | 55 |
| 2015-07-22 | RAML – RESTful API Modeling Language | hliyan | 3 | 0 |
| 2015-09-10 | RAML – RESTful API modeling languageLatest 20+ point return | tilt | 80 | 57 |
| 2015-12-04 | RAML v1.0 (RESTful API Modeling Language) | davidbarker | 1 | 0 |