From: skaller <skaller@ozemail.com.au>
To: Benjamin Geer <ben@socialtools.net>
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Commercial application written in O'Caml: ExcelEverywhere
Date: 21 Sep 2003 21:55:39 +1000 [thread overview]
Message-ID: <1064145147.11705.46.camel@pelican> (raw)
In-Reply-To: <3F6CB865.8030902@socialtools.net>
On Sun, 2003-09-21 at 06:28, Benjamin Geer wrote:
> skaller wrote:
> > In particular, I would like my product to
> > be ISO Standardised,
>
> IANAL, but it seems to me that the ISO standardises specifications, not
> implementations. Patents are an issue for specifications, because they
> affect all possible implementations (as in the case you mentioned), but
> source-code copyrights aren't, because only affect one particular
> implementation; anyone is free to make their own implementation of the
> same spec.
It isn't quite that simple. As I'm sure you know
programming languages contain facilities for defining
interfaces, for example, for libraries.
In addition, libraries contain definitions.
In both cases, the library codes being copyright
can't be standardised. Often the actual source
definitions/interface specifications are best given
as a precise way of formulating a requirement.
Therefore, the existence of copyrighted codes may
actually hamper standardisation, and even if it doesn't,
the encumberance is not encouraging to a standardisation
body. See a similar comment from Pierre Weiss about
INRIA's licencing policy -- it isn't the Ocaml team
but INRIA lawyers that vet the terms by which Ocaml
is released. Meaning: it is useful to simplify administrative
and legal issues to get the job done.
In addition, all my sources are literate programmed,
and contain human script stating specifications,
as well as the source codes, so the specifications
I provide cannot be distinguished from the programming
language sources: both are physically embodied in the
same source files. Thus, to release the specifications
for standardisation I have to release the language
source codes as well (both are 'derived' from the
LP source files, and so are derived works covered by
the same copyright)
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-09-21 11:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 16:11 [Caml-list] possible typechecker bug Fernando Alegre
2003-09-19 2:00 ` malc
2003-09-19 2:06 ` Fernando Alegre
2003-09-19 6:57 ` Julien Signoles
2003-09-19 8:01 ` [Caml-list] Commercial application written in O'Caml: ExcelEverywhere Mattias Waldau
2003-09-19 9:26 ` Benjamin Geer
2003-09-20 8:12 ` Damien Doligez
2003-09-19 11:10 ` skaller
2003-09-19 14:49 ` Richard Jones
2003-09-19 15:02 ` Remi Vanicat
2003-09-19 17:20 ` Karl Zilles
2003-09-20 19:25 ` skaller
2003-09-20 20:28 ` Benjamin Geer
2003-09-21 11:55 ` skaller [this message]
2003-09-21 15:01 ` [Caml-list] how can I print graphics on my local printer under Linux? PL
[not found] ` <20030921161556.GA451@swordfish>
2003-09-22 8:10 ` PL
2003-09-22 8:38 ` Basile Starynkevitch
2003-09-23 20:24 ` Christophe TROESTLER
2003-09-23 21:48 ` Pierre Weis
2003-09-22 9:21 ` Olivier Andrieu
2003-09-19 22:29 ` [Caml-list] Commercial application written in O'Caml: ExcelEverywhere Oleg Trott
2003-09-20 9:09 ` Mattias Waldau
2003-09-20 9:25 ` Jean-Marc Eber
2003-09-21 9:38 ` Xavier Leroy
2003-09-20 20:01 ` skaller
2003-09-20 19:58 ` skaller
2003-09-19 11:48 ` Ville-Pertti Keinonen
2003-09-20 18:53 ` skaller
2003-09-20 19:31 ` Alain.Frisch
2003-09-19 14:47 ` Richard Jones
2003-09-20 19:32 ` skaller
2003-09-19 16:23 ` kknowles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1064145147.11705.46.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=ben@socialtools.net \
--cc=caml-list@pauillac.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox