Posted on 01-17-2013
I just posted a story on how I like the Guardian’s approach to data journalism, and spending time evolving on last nights thoughts about the possibilities of Markup APIs.
As I’m migrating much of the front-end of my websites to run on a home brew of Github Pages, Jekyll and JSON fueled Mustache Templates, I am seeing more of the potential of not just Markup APIs, but Markdown APIs that will run in a purely client side environment.
An example would be, that when I wanted the 2010 population for New York City, I could just write [population|New York|NY|US|2010], or something like that and would print out the actual population for that year in NYC, with a link to the source. Each time I used a markdown API it would add some sort of attribution to the source at the bottom of document.
Seems like we’d establish trusted, centralized sources of information, allowing anyone (even non-developers) to put open data and APIs to use via easy to implement markup or markdown APIs.
Think of the potential if facts around the web actually had the backing of trusted sources, and were able to be embedded anywhere on the web, via apps or digital documents.
It would be fun to create a markup and markdown API for API Evangelist, with a dictionary of terms, facts and other data that were relevant to the API industry.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use
- So You Wanna Do a Spreadsheet or Database To API Startup
- Jumpstarting the Automobile API Conversation With Carvoyant
- Some Of The Common Building Blocks of Payment APIs
- API Badging and Credentialing To Demonstrate Skills
- Finding Good API Developer Talent Is Hard
- Common Building Blocks Of API Design