The Open API Initiative group is evolving what has become the de-facto standard API Description Format to produce a consistent and compatible format for describing APIs, allowing interoperation between tooling, systems, and runtime environments. Tony Tam, creator of the popular Swagger Specification is providing an update on the group activity.
An interesting trend is emerging in the world of Web APIs, with various engineers and companies advocating for dedicated APIs for each consumer with particular needs. Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. You might need to optimize your API accordingly.
As this article’s author, Mark Foster, puts it, "Absent profiles, the API space will be relegated to blindly passing around 'magic strings, fooling ourselves into thinking we are passing reliable semantic information." Here, Foster — one of the editors of the ALPS specification — explains what semantic profiles are and how they can transform the way Web APIs are desgined and implemented.
John Milinovich explains why mobile deep links matter, how to implement them and search for deep links in other apps using the URX API.
This article (the first in a four-part series) focuses on the design of a hypermedia type, by mapping a particular problem domain to hypermedia messages, as a basis for the API. 1