[Mono-list] Mono and Patents....
Richard Norman
normri@samc.com
Mon, 15 Mar 2004 14:41:24 -0800
--=__Part4B6A5004.0__=
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
Ok, I thought we killed this particular issue a long time ago.. (grin)
Here is the take I get from Miguel and someone correct the perception
if I am incorrect....
Your application makes use of the framework not the actual libraries
(unless you create a library that extends an existing one). So your OWN
libraries should be safe to do whatever you wish with them. Your
applications themselves should be fine.
If you were creating your own C# compiler or assemblies using the
existing APIs (System.Windows, System.Web, etc...) You "could" be at
risk. It again depends on what the terms of the ECMA agreement is and
what the API patents actually are.
This particular issue would fall into the lap of the Open Source apps
of dotGNU, Mono, and others (I think Intel has an implementation - but
not open source).
So the basics of the answer is that you are not directly affected if
Microsoft has some sort of fee. Your application can freely use the
libraries, but only for the creation of your own apps. If you are
planning to create a lot of extended libraries or your own compiler (I
think few of us are on this list for that), then you may want to review
it (the license and the RAND terms) more closely. Technically the people
to actually ask for your own satisfaction are Microsoft and ECMA to be
sure that they are all on the same page. ECMA regarding the ECMA specs,
and Microsoft for the API issue and overall RAND terms if you are
unclear.
Everyone, am I pretty much right? Miguel, is this the jist of the issue
you are trying to sum up for everyone?
Richard Norman
Application/Web Developer
**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to anyone or make copies.
**************************************************************************************************
--=__Part4B6A5004.0__=
Content-Type: text/html;
charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Description: HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 12pt Arial">
<DIV>Ok, I thought we killed this particular issue a long time ago..
(grin)</DIV>
<DIV> </DIV>
<DIV>Here is the take I get from Miguel and someone correct the perception if I
am incorrect....</DIV>
<DIV> </DIV>
<DIV>Your application makes use of the framework not the actual libraries
(unless you create a library that extends an existing one). So your
OWN libraries should be safe to do whatever you wish with them. Your
applications themselves should be fine.</DIV>
<DIV> </DIV>
<DIV>If you were creating your own C# compiler or assemblies using the existing
APIs (System.Windows, System.Web, etc...) You "could" be at risk. It again
depends on what the terms of the ECMA agreement is and what the API patents
actually are.</DIV>
<DIV> </DIV>
<DIV>This particular issue would fall into the lap of the Open Source apps of
dotGNU, Mono, and others (I think Intel has an implementation - but not open
source).</DIV>
<DIV> </DIV>
<DIV>So the basics of the answer is that you are not directly affected if
Microsoft has some sort of fee. Your application can freely use the libraries,
but only for the creation of your own apps. If you are planning to create a
lot of extended libraries or your own compiler (I think few of us are on
this list for that), then you may want to review it (the license and
the RAND terms) more closely. Technically the people to actually ask
for your own satisfaction are Microsoft and ECMA to be sure that they are all on
the same page. ECMA regarding the ECMA specs, and Microsoft for the API issue
and overall RAND terms if you are unclear.</DIV>
<DIV> </DIV>
<DIV>Everyone, am I pretty much right? Miguel, is this the jist of the issue you
are trying to sum up for everyone?</DIV>
<DIV> </DIV>
<DIV>Richard Norman</DIV>
<DIV>Application/Web Developer</DIV><FONT SIZE=3 COLOR=BLUE><PRE>**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to anyone or make copies.
**************************************************************************************************
</PRE></FONT>
</BODY></HTML>
--=__Part4B6A5004.0__=--