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
Actually, some of us do care | 394 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Actually, some of us do care
Authored by: NigelWhitley on Friday, April 27 2012 @ 08:01 PM EDT
I don't see the point you're trying to make. The term API is generally used to
describe one of two things (Oracle tend to alternate between them without making
it clear which they are talking about). One can talk about an API as the
specified set of methods and variables which allow one to access the internals
of the library (that would be the catalog or more accurately the Dewey system).
Alternatively it can refer to the whole library i.e. both internal code and the
publicly defined interface to that internal code (the catalog and the books).

In order to "enhance our interaction with whatever
is on the inside" you would need to alter the design of the API, not just
the code within it (which is the analogy I was drawing with the
"implementation" details of the book).

With respect, it's not nit picking to notice that a catalog for a book library
isn't exactly like an API for a code library - it's just missing the point of
the analogy. There are indeed lots of ways in which a book library differs from
a code library. For example, a book catalog might be expected to give the
publication date, author's name, language but these are unlikely to be included
in the API methods for a code library (although it's possible someone could
design it in such a bizarre fashion). I don't see how that helps anyone to
understand Oracle's or Google's position regarding the Java APIs.
------------------
Nigel Whitley

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