<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Craik Pyke</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Communications Enabled Applications: Building Value, not Monetising APIs</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Business Resource</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2010</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://timreview.ca/article/347</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Talent First Network</style></publisher><pub-location><style face="normal" font="default" size="100%">Ottawa</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Over the past decade there have been numerous attempts at opening telecom infrastructures to developers. As each attempt evolves to the next, there is an equal desire to monetise the exposure of telecom capabilities using traditional and well understood mechanisms: charge for necessary equipment upgrades and license the application programming interfaces on a per-invocation or &quot;block of simultaneous invocations&quot; basis. However, the various vendors and development companies involved in creating applications with embedded communications capabilities have had to re-examine their business and technology models in an increasingly competitive applications market where the rate of applications failing to gain market traction far outweighs the rate of success.

This article looks at the history of telecommunications APIs and the predominant business models that have accompanied those interfaces. By analysing the history of telecom APIs and recognising the gradual shift from a strongly vendor controlled environment to a highly accessible component of IT networks, we can recognise the shift in revenue generation from a typical monetisation model to a value based model. Additionally, we can examine how incumbents and new entrants are dealing with the more unpredictable business models and emerging methods for de-risking value based revenue opportunities. 
 </style></abstract><issue><style face="normal" font="default" size="100%">May 2010</style></issue><work-type><style face="normal" font="default" size="100%">Articles</style></work-type><custom1><style face="normal" font="default" size="100%">Coral CEA
Craik Pyke is a mobile enthusiast and part-time developer, with a professional background in telecommunications engineering. He has 15 years of experience in the Ottawa high tech industry, working predominantly in communications-centric organisations. Craik is presently a Senior Technical Architect for Carrier Applications and Development Ecosystems at Nortel. Additionally, Craik contributes to the Coral CEA organisation as acting Leader of Technology and Architecture, and is a contributor to iPhoneCTO.com. </style></custom1></record></records></xml>