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 | # ]
|
|
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 | # ]
|
|
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
|
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 | # ]
|
|