siren

that managed to dig up a couple of random links. I am glad that it mentions rfc9457 though.

hypermedia format (and, again, I do not believe that HTML is the only hypermedia format). Markdown, for example, is a (limited) hypermedia format imposed on top of plain text. When combined with a client that understand Markdown it forms a hypermedia system. > If your custom non-standard XML DSL is hypermedia, then everything is This section is very difficult to parse. I did not create HXML, however I do think it qualifies as a hypermedia format due to the presence of hypermedia controls. And I agree that the hypermedia client for HXML is just as important as the format itself in creating a mobile hypermedia system. I also want to stress that I think you can impose a hypermedia format on top of JSON. You offer some examples and another one I'm familiar with is Siren (https://github.com/kevinswiber/siren). This is analogous to how HTML imposes a hypermedia format on top of SGML, or HXML imposes a hypermedia format on top of XML. As you rightly note, that isn't enough however: you also need a hypermedia client that understands that format and can present non-linear actions to a user. You seem very focused on the idea that I think only HTML is a hypertext. I want to stress again that do not believe this to be the case, that appears to be a language misunderstanding. Finally, we have this: > Hypermedia, as Roy Fielding himself says, is the property of a machine talking to another machine using a media type both understand. The media type aka format itself doesn't matter as long as both machines understand it. Even presentation of controls to the user is a secondary concern and can be performed by the machine as it sees fit. Because, once you've unwrapped the contortionist back into their human shape, hypermedia is a property of the client. This conclusion is contradictory. "A machine talking to another machine using a media type both understand" makes the effective use of hypermedia a property of both the client and the server (both machines). I agree strongly with that conclusion, drawn directly from your own words, which is why I titled my book Hypermedia Systems rather than, say, "HTML is the only hypermedia format".

} ] }

ood hypermedia types. Edit: I wanted to also add a couple other interesting media types to check out, HAL [4] and Siren [5]. I'm sure there are other really good ones, too. [1] By definition I'm taking it to mean fully describing an API. [2] https://github.com/ongithub/businesses/blob/gh-pages/busines... [3] http://amundsen.com/media-types/collection/ [4] http://stateless.co/hal_specification.html [5] https://github.com/kevinswiber/siren

the semantic profile detailed in the ALPS document. The bot (written in JavaScript), knowing only the semantics involved with registration and "create post" links/forms, and an entry point for the API, is able to signup and begin making posts. The interesting thing is that the precise implementation of the API is not important, e.g. whether it's written with NodeJS or PHP or Clojure or whatever. Also, from one implementation to another, the pages served by the API could vary in terms of the layout of the pages, CSS, etc. So long as the pages conform to the semantic profile, the bot should be able to work equally well with a wide variety of implementations. Regarding JSON, there are a number of attempts to develop hypermedia-rich media types on top of it: HAL http://tools.ietf.org/html/draft-kelly-json-hal-03 JSON-LD http://json-ld.org/ Collection+JSON http://www.amundsen.com/media-types/collection/ Siren https://github.com/kevinswiber/siren There are others as well.