decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
An INCREDIBLY obvious analogy for APIs | 394 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
An INCREDIBLY obvious analogy for APIs
Authored by: Anonymous on Wednesday, April 25 2012 @ 10:29 PM EDT
> OK. Now fill in the blanks with something from
> everyday life. Maybe use Dan Bornstein's dog.

I don't think a dog is a great analogy, but I can manage it if you permit me to
substitute a robot dog so that copyright applies to aspects of its behaviour.

* API = named idea.

The idea "Play Dead". You can't copyright this idea.

* API name and syntax = the interface between humans and computers. The name and
syntax are functional and fixed because computers are absolutely literal.

The spoken command "Play Dead Spot". If the human speaks a different
phrase like "Die Spot", the dog won't recognise it. If the dog is
programmed instead to respond to the phrase "initiate trick 37" then
the human won't be able to get it to perform. If robot dogs are common and
expected to respond in the same way then this becomes a purely functional `word'
in the language by which humans expect to talk to robot dogs.

* API Specification = a precise description of the named idea in human
language.

The text in the robot dog "instruction manual". For example "The
spoken command 'Play Dead Spot' will cause the rover3000(tm) robot dog to roll
over on its back and imitate a dead dog for ten seconds." You can copyright
the instruction manual.

* API Implementation = code to tell a computer how to do perform the activity
described by the named idea.

The millions of lines of complicated program code needed to enable the robot dog
to recognise the spoken command and move its little robot legs in the right
sequence to carry it out. You can copyright this code too.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )