Mark Radcliffe on intellectual property, software patents, & open source software is Eating the World

Mark Radcliffe on intellectual property, software patents, & open source software is Eating the World

API Economist: Is the reason why intellectual property and software are so challenging due to the sheer lack of case law that's been established?

Mark Radcliffe: I think that's part of it. But I also think you need to go back a little bit and talk about how software came to be covered by copyright. If you go back to the 1980s, there were very respectable intellectual property lawyers who would tell you that software was not copyrightable because it was a functional “work”.  Only certain types of software would be copyrightable. Moreover, when the Copyright Act of 1976 was enacted, Congress deferred the decision about protecting software under copyright until they received a report from a special committee, the National Commission on New Technological Uses of Copyrighted Works (CONTU). Although CONTU recommended protection for software under copyright, one commissioner suggested that copyright not apply to “computer program in the form in which it is capable of being used to control computer operations.”  Now the courts have made it very clear that software is protected by copyright, in fact almost any form of software is copyrightable. But copyright is actually a pretty poor fit for software. It's a poor fit because there's a large degree of functionality in software. Copyright was designed for music and literature and novels, things where you'd have immense scope in the choice of how you create the “work”.

Read More

Kin Lane on spreading his API evangelism to the community and the government

Kin Lane on spreading his API evangelism to the community and the government

API Economist: How did you become the API Evangelist?

Kin Lane: I was the VP of Technology at an events management company, WebEvents Global, leading their technology and architecture. I ran all SAP events, including Sapphire for two years. I was also involved with TechEd and a lot of the North American events. I was brought on to move them out of the data center and be more elastic in the cloud, and meet the demands of the global events. I moved it into the Amazon Cloud and re-architected the whole system using APIs and Amazon APIs. I loved APIs. But I wanted to do something else. I started studying the API space. I quickly realized that there are a lot of technical pundits in this space. But no one was keeping eye on the business of APIs, the myriad of tools it takes to be successful, nor approaches to evangelism and marketing to developers and the whole politics of APIs. So I launched API Evangelist and just started studying this space. Three years later I'm still doing it.

Read More

Julius Marchwicki on Ford using APIs for better customer experience

Julius Marchwicki on Ford using APIs for better customer experience

API Economist: Congratulations on being the first automobile manufacturer to launch a mobile app developer program, announced at CES back in January.

Julius Marchwicki: Thank you very much!

API Economist: What was your API strategy behind the launch?

Julius Marchwicki: The strategy behind SYNC at large and what Ford has done is really to focus on what our consumers are doing. We went out and talked to a large number of consumers. We started to understand what they were doing inside of their vehicles, and what gaps we needed to fulfill for them. That's how embedded navigation came to be many years ago.

Read More