rulepool: Architecture for Guidance in the API-Economy Olaf Resch

• Since 2006 Lecturer of Informationmanagement and E-Business at Berlin School of Economics and Law

• www.hwr-berlin-de • Research interests: API-Economy, BRM and

Internetsociety.

Application Programmming Interface

URL url = new URL( "http://api.opencalais.com/tag/rs/enrich" ); HttpURLConnection connection = (HttpURLConnection) url.openConnection(); connection.setRequestProperty( "x-calais-licenseID", apiKey); connection.setRequestProperty( "Content-Type", "text/raw;

charset=UTF-8" ); …

API: data -> functionalities -> competency

API-Economy: doing business based on multilateral, anonymous and dynamic

networking.

Dynamic Networking is great for Business.

Turn Offs Buyerside

• Ignorance. • Inertia. • Pure Fear. • Buying because of the nice Salesperson. !

• ComplexityAVOIDANCE.

Turn Offs Sellerside

• Unclear Business Models. • Coarse grained Product Line. • Low scalable Pricing. • Demanding TOS. !

• ComplexityIGNORANCE.

Business Rules: ! Guide Business Behaviour, Aligned with Strategy, Automated with Rule Engine, Maintained by Domain Expert with Rule

Builder. !NEED: Functionality to become active. !A Gold Customer always receives a 10% discount

API’s: ! Huge reservoir of functionality. NEED: Guidance. !

Thus Made for Each Other☺

rulepool project <Ad>serioussearch.de</Ad>

+ Business

Technology

+ Business

I think…. !

API‘s + Culture

+ Complexity Management (e.g.rulepool) = API-Economy. !

What do you think?

Thank you for your Attention and be well!