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
Time for Us Programmers to Help Define APIs in "Legal Termonology"? | 438 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Time for Us Programmers to Help Define APIs in "Legal Termonology"?
Authored by: calris74 on Friday, April 27 2012 @ 12:13 AM EDT
I think there needs to be a distinction between the API Definition and the API Specification

The Definition by definition (no pun intended) defines the API - The names of it's components/functions/parameters etc

The Specification is the formal presentation of the API Definition in a human-readable form (i.e. the documentation).

The Definition cannot be covered by copyright The Specification might by coverable by copyright as it actually has creative input.

It's like the plot of a novel is not covered by copyright, but the novel itself is

[ Reply to This | Parent | # ]

Time for Us Programmers to Help Define APIs in "Legal Termonology"?
Authored by: xtifr on Friday, April 27 2012 @ 12:20 AM EDT
The API is an interface--API actually stands for Application Program
Interface--so what anonymous called the "API name and syntax" is the
actual API. The idea is just an idea.

The specification is documentation. The actual words of the specification will
be subject to copyright, but the ideas expressed by the specification will not,
and someone else can write a similar specification in their own words.

Other than that, looks OK.

---
Do not meddle in the affairs of Wizards, for it makes them soggy and hard to
light.

[ Reply to This | Parent | # ]

Time for Us Programmers to Help Define APIs in "Legal Termonology"?
Authored by: Anonymous on Friday, April 27 2012 @ 01:19 AM EDT
If I see anyone else try to define an API, especially by use
of an analogy, I will track them down and cut out their hearts
with a blunt spoon :-)

[ Reply to This | Parent | # ]

  • restated.... - Authored by: Anonymous on Friday, April 27 2012 @ 07:26 AM EDT
missed a bit
Authored by: Anonymous on Friday, April 27 2012 @ 07:13 AM EDT

There are *two* API implementations

One is the source code, that (usually) tries to express in source code form the
idea presented in the specification document
(or vice versa, the document is an English language description of the idea
expressed in the source code))

One is the Object code form, which is the source code form compiled to machine
readable (binary)

[ 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 )