[Mono-list] FW: [Ocl-general] Re-using OCL: Clarification of Copyright

Smith, Scott D scott.d.smith@intel.com
Thu, 20 Sep 2001 10:03:28 -0700

Hi All,

Below is a clarification on using OCL (http://sourceforge.net/projects/ocl)
within your work.  BTW, the Platform Abstraction Layer (could be used as a
C# wrapper around your C wrapper for OS/VES interaction) is not part of the
standard, so use of that is not related to the ECMA copyright.

Hope this is useful.


-----Original Message-----
From: Smith, Scott D [mailto:scott.d.smith@intel.com]
Sent: Wednesday, September 19, 2001 2:44 PM
To: 'ocl-general'
Subject: [Ocl-general] Re-using OCL: Clarification of Copyright

Hi All,

Last week there was much discussion on other open source project mailing
lists regarding the copyright issues of re-using OCL within those projects,
because the OCL source baseline was generated directly from the draft ECMA
specification.  We have confirmed with Jan van den Beld, ECMA Secretary
General, the copyright issues pertaining to the standard itself:

"With respect to the ECMA Standard the situation is, and has never been
changed, that the contents are available free of charge and freely copyable.
Since ECMA is the owner of the ECMA Standard it is unavoidable that ECMA has
copyright on it, but ECMA has never made any claims with respect to this
right. However, we want to retain the copyright, e.g. for the case that
somebody would take the ECMA Standard, change it and still call it an ECMA
Standard: in such a situation ECMA would apply, if needed, legal means to
undo, or otherwise correct the situation."

Mr. van den Beld's statement only applies to the standard, not to specific
implementations (e.g. OCL), but as you know OCL has been released under the
Intel Open Source License - a fairly non-restrictive BSD style license.

We hope others can re-using OCL, gaining the following benefits:
- Ensures CLI implementations match, as close as possible, the class
libraries defined in the draft ECMA CLI standard.
- Provides implementations (some partial) of ~90 of the ECMA standardized
- Eliminates the need to manually code class, interface, enum, property,
method, etc. signatures for over 300 standardized classes
- In-line source documentation that matches the wording in the draft ECMA

If you have further copyright or related questions, please contact Mr. van
den Beld at: jan@ecma.ch


Scott D Smith
Solutions Oriented Architecture/Core Group
e-Business Solutions Lab
(480) 552-3311

The views and statements expressed here do not necessarily reflect those of
Intel Corporation, its subsidiaries, or its employees.

Ocl-general mailing list