« Twitter client restrictions - bad for everybody (including Twitter) | Main | Welcome to the New 3scale! »

02 July 2011

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e553e776ea883401538f94af45970b

Listed below are links to weblogs that reference My Data, Your Service - The thin red line of User Data Access APIs (LinkedIn shuts out BranchOut and Others):

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

JohnDennehy

The rev share proposal is a great one if a company derives all or most of its value from LinkedIn data. It's a little trickier if less than say 50% of the service's value is derived directly from LinkedIn API usage.

Thankfully I was able to sign in to comment on this blog using Twitter, without you, me or anybody being charged.

I've tried to summarize the contentious terms and conditions of the LinkedIn API here if anybody is interested in a layman's interpretation: http://bit.ly/kNNnUM

Steven Willmott

Fair point on the attribution problem - that does cause issues and great summary on your blog. There are other business models to be applied though and it's a matter of finding one. The X% cut model seems to be becoming common for digital goods delivered on a single platform, but it would certainly be possible to do this by volume - low/zero costs for partners that use less than a certain volumes and then different licensing agreements as volumes get higher. It's by no means easy to balance the goal of distribution of the content and monetization - but cutting off access entirely is potentially also very negative.

The comments to this entry are closed.

Twitter Updates

    follow me on Twitter

    July 2012

    Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5 6 7
    8 9 10 11 12 13 14
    15 16 17 18 19 20 21
    22 23 24 25 26 27 28
    29 30 31        
    Blog powered by Typepad