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
Yeah, But No... | 270 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Yeah, But No...
Authored by: Anonymous on Friday, April 20 2012 @ 12:17 PM EDT
A human readable document that fully specifies the application programming
interface(API) is in fact documenting the corresponding >Library<.
Granted, it is not the full documentation of that library because it does not
describe the implementation. But that 'API' document is of the Library itself
because it describes the calling conventions for each published tool in the
library.

Indeed, an API as such is (dare I say it) deterministically derived from the
Library. ALL the key/critical/essential (in legalese: material) words/symbols in
the API have to EXACTLY match the corresponding word/symbols in the library for
the Interface to, well, interface. That's the essence of functionality.

Granted modern APIs also define constants, records, and other programming pieces
used with the tools in the Library, but they also fall out of the inputs and
outputs of the library's tools.

An 'API' to a non-existent library is not an API, because it doesn't interface
to anything. Its not an Application Programming >Interface<. Umm... Call
it an APH (Application Programming Hope?

As for Oracle's 'API Specification'; its mystifying.

JG





[ Reply to This | Parent | # ]

  • Swing and a Miss - Authored by: Anonymous on Friday, April 20 2012 @ 12:33 PM EDT
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 )