{"API Evangelist"}

Weekly API.Report For April 27th, 2015

This week's report was a painful one, because I did very little work last week when it came to monitoring the space, thus I was forced to play catch up this week after #APIsBerlin. It took 20 hours to produce this work, and get myself up to speed. #ouch

My Weekly API.Report represents the best of what I've read throughout the week, and is only what I personally felt should be showcased. Each news item comes with a link, and some thoughts I had after curating the piece of API related news. I'm trying to break down stories into as coherent buckets as I can, but it remains something that is ever changing for me, but ultimately I will settle on a clear definition for each of the research areas.

More on Account Management with APIs:

Continuing the Acquisitions discussion from last week:

Some Analytics news from last week:

An interesting look at API Copyright:

An API Debugging story:

For a change, a RAML API Definition story:

Couple of API Deployment nuggets:

Three API Deprecation stories:

The API Design tips for the week:

From API Evangelism world:

Busy week for API Events, because #APIsBerlin ya know!!!

The API Management news I tracked on:

Couple of API Monetization related items:

A valuable API Monitoring feature released this week:

The API News roundup of roundups:

The API Performance news:

When it comes to API Reciprocity:

Keeping the increasing number of API Testing stories by themselves:

As I get my Github monitoring more fine tuned, you'll see more API Tools like this:

Specifcally API Visualizations:

How to manage Applications:

Some Authentication items:

World of Automobiles:

A single Banking story:

A browser plugin story:

From the world of Business of APIs:

Another CAD story this week:

Watching Cameras:

Three Careers items this week:

Certification in the real-time space:

Hard to figure out what to break up into Cities or government:

The companion City Government section:

A smaller Cloud Computing section this week:

We don't see many Comments related stories:

On the Commerce front:

I've been waiting for this Conference Call related story for a while:

A shorter Containers section too:

Content delivery via APIs:

Some Copyright, with overlap above:

A single Crowdsourcing story:

Handful of Data stories:

Breaking out Data Rights by itself this week:

The Database stories from the week:

Hard to stand out in Documents this week, with BoxDev:

Three Drone related items to share:

More weather, but also Drupal related:

Education from the master:

Interesting Email concept:

We need more Encryption!!!

Tracking on Energy:

Selling to the Enterprise:

Big Environment data.

Replay, but this time for Events:

An Excel + Wordpress feature:

Handful of Federal Government items:

The Financial news:

Import Gender related studies:

The Hackathon news for the week:

An almost Hacker Storytelling piece:

When it comes to Healthcare:

Because I love History:

Understanding the History of Compute:

A simple How To:

Microsoft getting the IDE world in order:

International moves:

Internet of Things wasn't important to me this week:

Investments and the markets this week:

On the Legal side of things:

When it comes to Libraries:

Keeping things Local:

Is Location being recorded right?

Logging of everything:

The area of Machine Learning:

A single Mapping item that caught my eye:

Two Messaging related stories:

The popular area of Microservices:

Keeping an eye on everything Mobile:

In the Note space:

Open Data conversation blew up this week, with some fresh research published:

Open Source news makes me happy:

  • Evercam Goes Open Source - I spoke with the Evercam team about this decision. My advice is this move is essential to the company achieving the global scale they are looking for.

From the Outdoors:

Partners are important, lets see what happened:

ON the Patent front:

Two Payment stories:

A single Podcast to tune into:

The world of Politics:

And specifically the Politics of APIs:

Physical world of Printing:

Important area of Privacy:

Protection, for lack of a better term at this time:

Keeping things Real-Time:

You should Reclaim Your Domain:

A single tale of Regulation:

Scraping of all the good things:

SDK items:

Search over at Google:

The important Security discussions from last week:

A sinlge Sensor story in NYT:

The APIs who Showcase their integrations:

From the Spreadsheets world over at Google:

A single, distrurbing Surveillance item:

Translation is important space:

Microsoft dominating on the Transparency front for a change:

The University stories:

A Validation item from Twilio:

An important API Version release:

Other Visualizations from the week:

Keeping an eye on the Watch space:

Monitoring the Weather:

A single Wordpress item:

That concludes my report on what I read last week across the API space. I'm still working on pulling together a summary e-newsletter version, allowing people to get an executive summary of what I thought was important from the week--I am hoping it will be available next week. I'm also going to auto-generate some visualizations, and summary counts for each week. I'd like to see a tag cloud, and overall counts to help me understand the scope of news I cover each week.

If you know of something I missed, feel free to email or tweet at me, and make sure I know about your company, and have a link to your blog RSS. If you don't tell the story and share, the world will never know it happened.

It is a good time to be tracking on the API space--lots going on!



Thank You Berlin For Helping Make APIDaysBerlin / APIStrat Europe So Amazing!

I am still coming off the high that was @APIDaysBerlin / @APIStrat Europe this last April 23rd through 25th in Berlin. There were a number of talks that I enjoyed, ranging from open data, to 3D printing, to hypermedia--too many to list. I love the German view of technology, data privacy, and generally on what is going on in the United States.

Other than the wifi issues, the conference was a success. We sold out the event, with 450 people in attendance (goal was 400), and even with the final day being on a Saturday, the turnout was very impressive. Each session I ran, was full of questions, with an IoT session, and another architecture session running 10 minutes over, because there were so many good questions, I didn't want to stop.

We are processing the videos from the conference, which I will spend time watching each one--telling stories along the way. So keep an eye out on API Evangelist, and on the @APIStrat blog for each video release, as we will be trickling them out as each video comes off the production line over the next couple of weeks.  

Thank you to 3Scale, APIDays, and Commerce Tools to for making sure this amazing event came together. I'm just now getting my brain back in gear, so look for more  @APIDaysBerlin / @APIStrat stories over next couple weeks!

Thank you so much Berlin! I look forward to coming back for the next event.



My Open Data Panel At APIDaysBerlin and APIStrat This Friday In Berlin

In addition to helping be the MC for the API event, one of the conversation I am facilitating at @APIDaysBerlin / @APIStrat Europe this Friday in Berlin, is an open data discussion on the main stage. What better place to discuss the world of open data and API, then in Germany. The country has some of the strictest laws when it comes to protecting the privacy of German citizens, and when it comes to API access to data, I couldn't think of a better place to have an open discussion in 2015.

I have invited two data specialists to the stage Friday afternoon:

Ali Jelveh (@jelveh), CEO & Founder Protonet GmbH and Free Your Data -  Ali Jelveh is Co-Founder and Chief Revolutionary Officer of Protonet. Protonet builds Personal Severs for small and medium sized teams. The German-Iranian software engineer has been amongst the first developers at XING after dropping out of his college career. He is on a mission to transform the internet from centralization in the cloud to a state of distributed infrastructure and independent users.
Jonathan VoigtDigital Strategy Advisor / Country Representative of UN Influx - Jonathan Voigt is a startup founder, corporate entrepreneur and digital strategy advisor. Following a master’s degree in innovation management, he co-founded a digital marketing start-up and is now supporting Germany's leading agency for digital transformation. In an honorary capacity, Jonathan is the German representative of UN Influx , a charity that organizes hackathons to help the UN and the public engage better with one another.

I am looking forward to hearing what Ali and Jonathan have to say about open data, from a European perspective. To help stimulate the conversation, I've also invited one of our keynotes to join us:

Chris Taggart (@countculture), EO & Co-founder of OpenCorporates - Chris Taggart is the CEO and co-founder of OpenCorporates: The Open Database Of the Corporate World, which has worked with the open data community to build a database of over 25 million companies, all open data. Originally a journalist and later magazine publisher, he now works full time in the field of open data, and is on the UK government’s Local Public Data Panel, and Mayor of London’s Digital Advisory Board.

I do not have a list of questions prepared for these gentlemen. I think we all know the space well enough, just discussing who they are, their projects, and the wider open data space is sure to fill up 30 minutes of main stage action. I am eager to hear Chris's keynote as well, as I'm extremely interested in what OpenCorporates is doing.

If you aren't registered, there are like 20 tickets left, so you better jump now before the conference sells out. Feel free to send me any questions or topics you'd like to see disccussed, and I'll see you in Berlin this Friday and Saturday.



Weekly API.Report For April 20th, 2015

My Weekly API.Report represents the best of what I've read throughout the week, and is only what I personally felt should be showcased. Each news item comes with a link, and some thoughts I had after curating the piece of API related news. I'm trying to break down stories into as coherent buckets as I can, but it remains something that is ever changing for me, but ultimately I will settle on a clear definition for each of the research areas.

Accessibility is something I'm pushing more on:

A handful of interesting Acquisitions:

Not sure if it is API, but some scarey Agriculture data:

A few Analytics stories that caught my attention this week:

Some interesting API Deployment lessons:

More API Deprecation out of Google and Blackberry:

The required API Economy talk:

A healthy dose of API Evangelism:

The API Event goings on:

The neverending API Lifecycle:

Couple of API Management lessons I pulled out of this week:

Some API Monitoring wisdom from the past week:

The growing area of API News:

Increasingly popular API Performance related stories:

A free range API Reciprocity story:

An intresting Application story from legal realm:

The Architecture big picture:

Cool Audio offering out of Pop Up Archive:

Authentication stories out of Azure and SalesForce:

More the Banking industry:

More Blockchain education:

An API Book to look out for:

Valuable Business data resources:

All about the Business of APIs:

A lone computer aided design (CAD) story:

A general Camera story:

The Career opportunities this week:

Cloud Computing stories from across the leaders:

A single Cloud Storage product:

AWS has a pretty big Command Line Interface stack:

Containers is mostly about money this week:

An education story, but pulling out and showcasing because it applies to larger Content conversation:

China rock'n the Cybersecurity war front:

All about the Data:

And the Data Portability:

Specifically about the Database world:

Not your usual Device company:

The Document space:

Just a couple Drone highlights:

New APIs, and some Education stories:

The Embeddable discussions:

A single Entertainment focused API:

Out of the Federal Government:

In the Fitness arena:

The Hackathons that made the cut:

Always my favorite, the area I call Hacker Storytelling:

The Healthcare sector:

History is important:

On the connected Home front:

At the HTTP level:

Plotting the future of APIs at the IDE level:

Something you don't see much in my roundups, Infographics:

Trying to keep the Internet of Things compelling, but I only can use what I find:

Lot of Investment to go round:

I wish there was more Library news:

The Local discussion around data and APIs:

Tracking on Location focused details:

The Mapping discussions that caught my attention:

Microsoft is all about the Media in the cloud:

A single Microservice story:

The Mobile items from the week:

Separating out the Museum element here:

Not API news, but News, news:

Beyond just data with Open Data:

The Open Source talk out of Box:

Highlighting the importance of Partners:

A few Patent blips this week:

Had to highlight this Policing data story by itself, hopefully we'll see many more:

Beek week for the Politics of APIs, being led by Twitter:

The important Privacy stories I read:

Just keeping an eye on Push Notifications:

Always keeping it Real-Time:

Resources are so important to API operations:

I love Robots:

Two Scraping things to share:

Some interesting SDK moves:

Let's talk Security:

A single lonley Sensor:

Always Showcase your important integrations:

Single Page Applications (SPA):

I spend a lot of time in Space:

Good to see this State Government story:

From the land of Telecommunications:

Something Trademark related I felt should be liberated by APis:

Keeping the Transparency conversation moving forward:

Move forward Versions:

An API pioneer makes some Video moves:

SalesForce talking Visualizations:

Watching the world of Watches, for anything interesting:

We need more Water APIs:

Another player in the Wearables space:

That concludes my report on what I read last week across the API space. I'm still working on pulling together a summary e-newsletter version, allowing people to get an executive summary of what I thought was important from the week--I am hoping it will be available next week. I'm also going to auto-generate some visualizations, and summary counts for each week. I'd like to see a tag cloud, and overall counts to help me understand the scope of news I cover each week.

If you know of something I missed, feel free to email or tweet at me, and make sure I know about your company, and have a link to your blog RSS. If you don't tell the story and share, the world will never know it happened.

It is a good time to be tracking on the API space--lots going on!



Quantifying My Minimum Viable API Footprint Definition As Real API Portal

I wrote a post the other day laying out what I'd consider a minimum viable footprint for API operations. My vision of just exactly what an API is, has gone beyond just the technical, ever since I started API Evangelist back in July of 2010. Early on I saw this was more than just about the API endpoints, and documentation, code samples, and many other building blocks were essential to the success (or failure) of any API platform, area, or ecosystem.

This recent post was an attempt, here in 2015, to quantify what I would consider to be a minimum definition for API operation. After writing it I wanted to take another stab at actually creating a portal, that would stand up to the API rhetoric that I regularly produce. What better place to start, than my own personal master API stack, where I am working to get control over my own infrastructure. Once I got a version 1.0 definition, I forked it, and setup a default API portal that I am calling my demo APIs.json driven portal.

I have published to Github, a version of my minimum API footprint, which I'm using APIs.json an engine. After looking at 10,000K+ APIs, I have a pretty good idea of what I like to see. This is my interpretation of all that monitoring of the space--a distillation of what I've seen while reviewing APIs. It isn't perfect, but neither is the space that we have, and my portal is just an attempt at quantifying what I'm seeing.

I'm going to create a minimum viable Internet of Things (IoT) version of this portal as well, and use APIs.json to deploy different interpretations of what constitutes a minimum viable API presence. If you have anything you'd like to see in my base template, let me know. If you want to fork and add to, then submit a pull request, even better. I'm just playing around, but also looking to establish a suite of APIs.json driven tools, that help me(and you), better understand the API space.

To help on-board you with my vision, I also added a walk-through for when you land on the site. Something I will be adding to when I have time.