<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Below is a simple example of a marked up license.</div>
<div><br>
</div>
<div>The symbols << and >> designate the beginning and end of mark up statements.</div>
<div>In this case the top section is optional and marked as such with beginoptional and endoptional.</div>
<div>Within that and further down in the text are a total of three places where a copyright holders name can be used. For each of those is instruction on matching using a simple regex, in this case .+ which means any string of characters. For each there is
also an example and also a variable name so the actual text could be captured.</div>
<div><br>
</div>
<div>This (in addition to the aforementioned matching guidelines) is to instruct a person or a program how to go about matching this license to some license text found in the wild. </div>
<div><br>
</div>
<div>I continue to think it would be valuable to have a call with a couple of representatives from each organization to explore synergies.</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-family: Consolas; font-size: medium; "> <span class="Apple-style-span" style="font-family: monospace; font-size: 14px; white-space: pre; "><<beginOptional;name=copyrightSection>></span></div>
<div class="code-body highlight">
<pre><div class="line" id="LC2">Copyright (c) <<var;name=copyright;original= <year> <owner>;match=.+;example=John Doe>></div><div class="line" id="LC3">All rights reserved.</div><div class="line" id="LC4"><<endOptional></div><div class="line" id="LC5"><br></div><div class="line" id="LC6">Redistribution and use in source and binary forms, with or without</div><div class="line" id="LC7">modification, are permitted provided that the following conditions</div><div class="line" id="LC8">are met:</div><div class="line" id="LC9"><br></div><div class="line" id="LC10">1. Redistributions of source code must retain the above copyright</div><div class="line" id="LC11"> notice, this list of conditions and the following disclaimer.</div><div class="line" id="LC12">2. Redistributions in binary form must reproduce the above copyright</div><div class="line" id="LC13"> notice, this list of conditions and the following disclaimer in the</div><div class="line" id="LC14"> documentation and/or other materials provided with the distribution.</div><div class="line" id="LC15"><br></div><div class="line" id="LC16">THIS SOFTWARE IS PROVIDED BY <<var;name=copyrightHolderAsIs;original=THE COPYRIGHT HOLDERS AND CONTRIBUTORS;match=.+;example=JOHN DOE>> "AS IS" AND </div><div class="line" id="LC17">ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED</div><div class="line" id="LC18">WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE</div><div class="line" id="LC19">DISCLAIMED. IN NO EVENT SHALL <<var;name=copyrightHolderLiability;original=THE COPYRIGHT HOLDER OR CONTRIBUTORS;match=.+;example=JOHN DOE>> BE LIABLE FOR ANY</div><div class="line" id="LC20">DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES</div><div class="line" id="LC21">(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;</div><div class="line" id="LC22">LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND</div><div class="line" id="LC23">ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT</div><div class="line" id="LC24">(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS</div><div class="line" id="LC25">SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</div></pre>
</div>
</div>
</blockquote>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Phil Odence <<a href="mailto:podence@blackducksoftware.com">podence@blackducksoftware.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>" <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, February 25, 2014 7:14 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>" <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [License-discuss] [Infrastructure] Machine readable source of OSI approved licenses?<br>
</div>
<div><br>
</div>
<div>
<div style="color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>We'll get you some examples and some more detail, but the main idea is to support matching (for both humans and programs). The idea is to do as much as we can with the general guidelines, but to mark up where need be (as in my BSD copyright text example). </div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Luis Villa <<a href="mailto:luis@lu.is">luis@lu.is</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>" <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, February 23, 2014 6:21 PM<br>
<span style="font-weight:bold">To: </span>License Discuss <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [License-discuss] [Infrastructure] Machine readable source of OSI approved licenses?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">On Mon, Feb 10, 2014 at 8:02 AM, J Lovejoy <span dir="ltr">
<<a href="mailto:opensource@jilayne.com" target="_blank">opensource@jilayne.com</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We are in the process of updating the text files with markup to implement the license matching guidelines located here:
<a href="http://spdx.org/spdx-license-list/matching-guidelines" target="_blank">http://spdx.org/spdx-license-list/matching-guidelines</a> - the goal being to provide a way to ensure that when one SPDX user identifies a license, it is reliably the same as when
another SPDX user identifies the same license. Of course, the main example of this is the BSD 3 and 4 clause licenses and Apache 1.1, which may include the names of the specific copyright holder even though the rest of the license is exactly the same (goal
being to avoid concluding every BSD-3-Clause with a different copyright holder name gets identified as a different license.)</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Hi, Jilayne, Phil-<br>
</div>
<div class="gmail_extra">What is the intended markup here? The matching guidelines seem useful, but it isn't clear to me what a license marked up that way would look like. Is there an example somewhere?<br>
<br>
Luis<br>
</div>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>