When I talk about how much I believe in APIs, what I am really talking about is just how much I really believe in the web. The web is how humans are consuming and sharing data, content, and algorithms with each other by using the Internet. Conversely, APIs are how systems, applications, and devices are doing this via the Internet.
I do not advocate for any single API, company, tooling, or technology. Instead, I am evangelizing for an open web. This is exactly why I am always a little ashamed of how incomplete my understanding is of the core concepts that make up the web and the certain specifications that are driving it. Thankfully, there are people such as Erik Wilde (@dret) who work tirelessly to help us understand these specifications. They also work to make these specifications available in a simple way, which is what Erik did with his Web Concepts project.
More specifically, Erik has organized 13 Web Concepts for use to learn about, detailing 445 distinct specifications across the International Organization for Standardization (ISO), Internet Engineering Task Force (IETF), Java Community Process (JCP), and the World Wide Web Consortium (W3C). There are a number of these specifications that I am already aware of, but there are numerous others I am not, and that just isn't right.
In order to help me increase my own awareness and hopefully yours as well, I am going to regularly tweet out individual concepts and their specifications with links to Erik's work. I encourage you to bookmark his work and to get to work improving your web literacy where possible. I encourage you to consider forking his work and sharing it within your organization as well. It is important that we are all aware of these core building blocks of the web and are reusing existing concepts and specifications across our work wherever possible.