<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Times New Roman","serif";
font-variant:normal !important;
color:windowtext;
text-transform:none;
text-shadow:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1954552947;
mso-list-template-ids:878065638;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;color:windowtext'>Mitchell,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:windowtext'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:windowtext'>Yes, this
helps tremendously! Thank you so much for sharing these comments.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:windowtext'><br>
Kind regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:windowtext'><br>
Maria</span><span style='font-size:10.0pt;color:windowtext'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;color:windowtext'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> Mitchell Baker
[mailto:mitchell@mozilla.com] <br>
<b>Sent:</b> Friday, April 02, 2010 5:27 PM<br>
<b>To:</b> license-discuss@opensource.org; maria@aet-law.com<br>
<b>Subject:</b> Re: What does "new" mean in Section 1.9 (b) of the
MPL v 1.1.?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Maria<br>
<br>
I think it's possible that the person describing the use case to you uses
words differently than the MPL does. If so, there might be an easy answer.<br>
>From the use case described to you, I can imagine a setting where the JAR file
is included as a separate <b><i>source</i></b> file and is sent to and
assembled by a browser along with a bunch of other proprietary files that
together make up a web application. If this is the case then the MPL
shouldn't affect the other proprietary files. <br>
<br>
To know if this is the case we could all probably use a deeper understanding of
what "proprietary web application files" are and where things are
assembled and run. <br>
<br>
More specifically, <o:p></o:p></p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'>it's possible that the people describing this to
you mean "assembled and run<b><i> in the browser.</i></b>"
If so, this is true of all content the browser displays and
something that doesn't matter so much to the analysis.<o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'>Does "proprietary web applications
files" mean something like a web application framework or a set of
directories composed of many distinct files? <o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'>If so, is the use case dropping the JAR file into
this framework or directory structure?<o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'>If so, are the lines of code in the JAR file combined
<b><i>within the same source code file</i></b> as other code?<o:p></o:p></li>
</ul>
<p class=MsoNormal><br>
If the JAR file is included as a separate source file and is sent to a browser
along with a bunch of other proprietary files, then the MPL wasn't
intended affect the other proprietary files. If the MPL code is included
in the same *source code* file then the setting is different. <br>
<br>
To get closer to your specific question, the thinking behind 1.9
(b) is that 1.9(a) says any change to an existing MPL file is a
Modification. An easy way to avoid that is to copy a bunch of stuff
from a file (which doesn't result to a change in that file) and past it into a
new file then make additions. I don't think we ever made a distinction as
to whether what was combined with the MPL code was pre-existing or not. So
if the use case in question turns out to be that MPL code is being combined in
the <b>same source file</b> with other code I don't think the timing of which
code (MPL or other) was created first would seem to matter.<br>
<br>
Does this help?<br>
<br>
And of course, this is not intended as legal advice, or creating an legal
representation, etc.<br>
<br>
mitchell<br>
<br>
<br>
On 4/2/10 1:54 PM, Maria Magliano wrote: <o:p></o:p></p>
<pre>Hi! <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The use case described to me is that the MPL-covered code (a JAR file) will<o:p></o:p></pre><pre>be embedded (unmodified) into pre-existing proprietary web application files<o:p></o:p></pre><pre>that are then assembled and run. Doesn't this mean that both of the<o:p></o:p></pre><pre>scenarios you describe apply? I'd be interested in your take under either<o:p></o:p></pre><pre>scenario if you think it makes a difference in terms of how the license<o:p></o:p></pre><pre>applies to the resulting combination.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Best,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Maria<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: Luis Villa [<a
href="mailto:lvilla@mozilla.com">mailto:lvilla@mozilla.com</a>] <o:p></o:p></pre><pre>Sent: Friday, April 02, 2010 1:08 PM<o:p></o:p></pre><pre>To: Smith, McCoy<o:p></o:p></pre><pre>Cc: <a
href="mailto:maria@aet-law.com">maria@aet-law.com</a>; <a
href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a><o:p></o:p></pre><pre>Subject: Re: What does "new" mean in Section 1.9 (b) of the MPL v 1.1.?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On 4/2/10 12:50 PM, Smith, McCoy wrote:<o:p></o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Since MPL is undergoing revision right now, you might want to post your<o:p></o:p></pre><pre>question on the revision site: <a
href="http://mpl.mozilla.org/">http://mpl.mozilla.org/</a> If that section<o:p></o:p></pre><pre>is unclear, they'd probably want to clarify it.<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre>We're also lurking here in case of questions like this, for what it is <o:p></o:p></pre><pre>worth.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>*From:* Maria Magliano [<a
href="mailto:maria@aet-law.com">mailto:maria@aet-law.com</a>]<o:p></o:p></pre><pre>*Sent:* Friday, April 02, 2010 12:48 PM<o:p></o:p></pre><pre>*To:* <a
href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a><o:p></o:p></pre><pre>*Subject:* What does "new" mean in Section 1.9 (b) of the MPL v 1.1.?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Hi Everyone!<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I'm trying to understand what the term "new" means in the MPL definition<o:p></o:p></pre><pre>of a "Modification" in Section 1.9. (b) (I reproduce the entire<o:p></o:p></pre><pre>definition below for reference). Does "new" mean a file that, apart from<o:p></o:p></pre><pre>the MPL-covered code, did not exist previously (i.e. anywhere in the<o:p></o:p></pre><pre>universe?) or, does it also mean a file that may already exist but was<o:p></o:p></pre><pre>not previously combined with MPL-covered code (so that "new" refers to<o:p></o:p></pre><pre>the novel combination of the two)? I'm trying to make sure that<o:p></o:p></pre><pre>pre-existing proprietary code is not considered as being "new" under<o:p></o:p></pre><pre>that subsection by being combined with MPL-covered code for the first<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre>time.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I have added a comment to our commenting tool to reflect the ambiguity <o:p></o:p></pre><pre>in the use of 'new' here:<o:p></o:p></pre><pre><a
href="https://mpl.co-ment.com/text/NMccndsidpP/view/?comment_id_key=kZDPJ6wstkI">https://mpl.co-ment.com/text/NMccndsidpP/view/?comment_id_key=kZDPJ6wstkI</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>It might help the discussion if you elaborated a bit on what you say <o:p></o:p></pre><pre>when you meant 'combined... for the first time'- do you mean that the <o:p></o:p></pre><pre>pre-existing proprietary code will be compiled together with the <o:p></o:p></pre><pre>MPL-covered code? Or do you mean that copyrightable material from the <o:p></o:p></pre><pre>MPL-covered code will be copied and pasted into the pre-existing <o:p></o:p></pre><pre>proprietary code?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Luis<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>