hypermedia

HyperMedia APIs are another evolving technology for maintaining more control between the client and the server.

Whenever possible, hypermedia-based media type designers should use the technique of extending to make modifications to a media type design.

That might change if something awesome comes out via open hypermedia.

Why do you not find value in hypermedia?

I love how hypermedia enables these kinds of API explorers.

Kind of want reply both to you and @pjc50: I think moving images with sound as part of hypertext/hypermedia is a given -- and has been since (at least) the 60s.

Perhaps there is room for something that blends traditional hypertext/hypermedia and articles better - fundamentally I think such a system will be more like a complex (object) programming system than text.

With the massive investments in IoT being laid down along with VR/AR experiences coming out of Facebook, Google, and Microsoft, this trend will likely only continue, unless someone releases a new innovative hypermedia format & client that catches on.

JS * Building Hypermedia APIs, browser-based web applications, and reactive architectures * Distributed databases and cluster computing, with stuff like Cassandra and Spark Please email your resume to hiring [at] urgentconsult.com if you think you're a good fit.

Perhaps the term "web" is regressing to mean interlinked hypermedia, more so then a general term for applications built using the web + other technologies.

"is /api/thing the wrong path" - is fixed by hypermedia, so 404 generally means that resource cannot be found.

The point with Hypermedia APIs however is the "representational state transfer" via defined relationships between the resources.

The people who can create a "new peer-to-peer hypermedia protocol" can't configure basic DNS?

I prefer the approach of focusing on the link relations or media type vice URI or some other technique of versioning because it is consistent in the direction (wrt Hypermedia-based APIs) of the link relations as the point-of-coupling for your API, which makes managing and reasoning about changes to your API less complicated.