We chose to launch API Commons at Defrag because we felt it was precisely the audience that would understand what we are trying to do, and we were right! Attendees of Defrag represent the leading edge of the tech space and provided us with the critical feedback we were looking for, while also helping us spread the word out about the project to all of the people who truly mattered.

The news coverage of the API Commons launch was everything we hoped for:

The feedback was 98% positive and we continue to welcome the constructive criticism we received and hope everyone will keep asking the hard questions. The positive feedback was more than we anticipated. We strongly feel that API Commons is a critical piece in moving the API space forward in a meaningful way, but it was great to hear that so many people can immediately see the same vision without any education about what is API Commons. It just speaks for itself.

Now that we've launched, what is next? The number one thing is get more API designs hung in the commons. We need you to step up and register your own API definitions, and help spread the word to other API providers about the importance for declaring their API definitions.

We believe that API Commons will resonate within city, county, state and federal government first, but commercial API providers will quickly see the benefits of putting their valuable designs into the commons.

If you have any questions, concerns or anything you think would benefit the API Commons community, please post it on the API Commons Google Group, on Twitter at @apicommons or email us directly at apicommons@gmail.com. The conversation around API definitions and data models is just as important publishing them in the commons.

API Commons is your project, so please help us make it the place everyone goes to discover, share and collaborate around the best API definitions and data models in the industry.

comments powered by Disqus