Many companies, government agencies, organizations, and individuals have an interest in the success, growth, and value of their organisation. The internet has reached the critical mass and has become the dominant means of communication and commerce.
Since the introduction of the World Wide Web, companies have set up web sites and provided users with information. What these websites lacked was complexity.
- Web 1.0 sites are static. The information contained in these websites does not change and therefore there is no reason for a visitor to return to the site at a later stage.
- Web 1.0 sites are not interactive. Most organizations have profile pages that visitors can look at but not impact or alter.
- Web 1.0 applications are proprietary. The Web 1.0 philosophy does not promote the sharing of knowledge and tries to retain exclusivity. Therefore each time an organisation or individual wants to create a web service they have to re-invent the wheel.
Bulletin boards, online forums, personal web pages with guest-books, and chat rooms appeared. These sites enabled people to ask questions, make statements, share information, and clobber each other in arguments and debates. These new enablement's have given rise to what we call nowadays Web 2.0.
Although the term Web 2.0 suggests a new version of the World Wide Web it does not refer to an upgrade of any technical specifications but to changes of how software developers and end users make use of the web. There is no exact description of Web 2.0, but most people agree that it involves making new and improved forms of online connections between:
...two or more people
Consumer Generated Media is about using online technologies to connect people to each other in a social network or business teams. This includes things such as social networking sites, wikis, blogs, and online videos. Websites such as Facebook, MySpace, Wikipedia, Blogger, and YouTube allow anybody to add as well as to access content, to leave messages and comments, and to exchange digital media including photos and videos.
...individual users and software applications
Software as a Service is the application functionality being offered directly over the internet. In turn user data and application can then be accessed from any internet enabled computing device. In simple terms it's like having all the work packages installed in a desktop available online. Therefore using them will not require the user to install them. For some years human resources and project management applications have been successfully offered over the internet. In recent years, online replacements for personal desktop applications have also been made available. For example, GoogleDocs is an online word processing, spread sheet and presentation package available for free over the web.
...two or more online services
Web Application Programme Interfaces are components of an online functionality which can be plugged together in order to create an integrated online system or Mashups. For example many companies use the web service of a payment service provider such as PayPal to allow them take online credit card payments. This results in customers interacting with two organizations that are automatically interlinked via the internet. A number of Mashups are facilitated by these APIs and this is a big tenant of Web 2.0.
Key Benefits of Web APIsReach & Relevance
The size of the web is growing vertiginously. On the bright side this growth brings with it an increased number of possibilities to promote products and services. On the other hand it is becoming more difficult to get noticed.
With Web 2.0 the website owner has the option to provide the functionalities which its website make use of, to third parties through an API. An API is wired through the infrastructure of a company, thus giving access to invocations which return what was previously considered as 'private' data. Thus, the website owner opens a gateway through which the data, its functionalities provide, can be retrieved and used on third party websites. As a result our website owner increases the possibility of users making use of its functionalities and therefore reaching a larger client base.
Third parties will only make use of functionalities if they are relevant to the services provided in their websites. In a nutshell an API allows our website owner to reach a client base interested in its functionalities and therefore increasing traffic.
Providing access to their services via APIs has been a major winner for several companies: Twitter and Flickr just to name a few. These companies have managed to gain platform leadership - and their API plays a crucial role in that. Many other companies are following suit: from e-commerce over content & media, business services to the government
APIs provide a key enabler that allows Internet businesses to go beyond their own website and try to be visible on every other website.
New distribution channel
APIs can simply be seen as a new distribution channel. While the original website is usually the main channel. APIs allow to reach, promote and sell the company's content or functionality to other websites.
Innovation & Synergies
Through APIs our website owner will have its content and functionalities available on a number of third party websites. But that is not all there is to it. Other website owners may decide to effect further enhancements to the content and functionalities retrieved with the possibility of making it more attractive and useful. The moral - have an API and let someone else decide to do it for free because there are lots of smart people out there. Give them the chance to make cool stuff and if they are passionate about the site, they will. Our API holder will then reap the benefits because more traffic is generated, and more importantly, more user activity in the site.
Creating a website can either be done by paying a developer or Mashup content and functionalities provided by several APIs. This might seem as being a typical example of free-rider principle. However this is not the case, since the original website would be continuously marketing itself.
Due to flexible integration and re-usage of content & functionality on the web, APIs foster innovation. The next major evolution cycle of the Internet will be a web, mashed-up from various sources of raw data, exploiting synergies to create something new with additional value added.
API Terms and Conditions
An API allows the public to access on line data in a controlled manner. Any user wanting to make use of an API is given a unique key. What can be accessed and retrieved is determined and monitored by an API and is limited per key. Users send a request for data retrieval to the API, this in turn confirms whether the user is authorised to access such data. If in the affirmative, then the API will allow the user to retrieve data from the library. This data will have to be passed through the API so that the user can take data which can be clearly read and understood.
Ensuring Compliance to the API Terms and Conditions
Security to the API provider, is limited to traffic data management, i.e. the API provider at most requests an Authentication key in order to be able to access and take hold of API data. Many Internet businesses have not yet done the switch from an open API (without access control) to a managed API (with access control).
However, at present the Product Manager has no means to confirm whether the Terms and Conditions of use are abided to, other than manually accessing the website and verifying whether its contents are compliant. This means that once the data is being given to the users, the Product Manager has no control of it and the user/client can amend and manipulate the data to one's discretion.
The solution proposed is one which addresses this problem at runtime, where a web based application is made available to both the API companies and users willing to make use of specific API content. The application will act as an intermediary between an API and the client. The intermediaries' main concern will be the licence restrictions required by the API provider.
A sample prototype of the actual application has been developed and explained by the below diagram:
- An API Provider wanting to enforce the API Terms and Conditions will logon to our Online Application. This application will provide the project manager with a list of security constraints to choose from. He will in-turn select the security constraints to be invoked for specific API calls.
- From now onwards, API providers will be giving out a new API URL which will be that of the Proxy server. As a client invokes a request to the API, this will be directed to the proxy.
- The proxy will send the request with some added verification details to the API.
- The API will send back the data requested by the client to the proxy.
- The proxy will send the data provided by the API together with the security measures linked to the request done by the Client. From the client point of view, once the user has requested API content, the intermediary will send the sandbox to the website which requested the API content and will check for the Security Restrictions provided by the API provider. If the website is compliant to these Security Restrictions, the sandbox will provide the user with the data requested; else no data is given to the user.
The major problem perceived in enforcing the API Terms and Conditions was the use of IFRAMES. An IFRAME is an HTML document embedded inside another HTML document on a website. The IFRAME HTML element is often used to insert content from another source, such as an advertisement, into a Web page.
This test case was taken into consideration since the use of IFRAMES can 'fool' the Sandbox, in such a way as to make it believe that the data in the website is compliant with the API Terms and Conditions. While in reality, although the data retrieved by API is placed in an HTML document which is compliant to the Terms and Conditions, the various other HTML documents embedded in the same website are not.
Prototype Evaluation Technique
Thus, these professionals will try to show the data even though the web content is not desired.