<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Artistic License 1.0	</title>
	<atom:link href="https://opensource.org/license/artistic-1-0/feed" rel="self" type="application/rss+xml" />
	<link>https://opensource.org/license/artistic-1-0</link>
	<description>The steward of the Open Source Definition, setting the foundation for the Open Source Software ecosystem.</description>
	<lastBuildDate>Tue, 27 Jun 2023 12:37:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/><atom:link rel="hub" href="https://websubhub.com/hub"/>	<item>
		<title>
		By: profesjonalna		</title>
		<link>https://opensource.org/license/artistic-1-0#comment-87</link>

		<dc:creator><![CDATA[profesjonalna]]></dc:creator>
		<pubDate>Mon, 16 Jul 2007 18:00:06 +0000</pubDate>
		<guid isPermaLink="false">https://opensource.org/artistic-1-0/#comment-87</guid>

					<description><![CDATA[&lt;strong&gt;Artistic License&lt;/strong&gt;&lt;br /&gt;The Artistic 2.0 notes walk you through the new license, but they  
don&#039;t specifically highlight the changes. This will make a nice  
addition to the FAQ.

Overall, the terms of the Artistic 2 are the same as the Artistic 1,  
though the language has been polished and reorganized to be more  
readable and more legally precise. The significant additions are  
sections 4(c)(ii) and 13.

Section 4(c)(ii) is what we call the &quot;relicensing&quot; clause, because it  
allows you to take a package you received under the Artistic License  
and use it under the terms of a copyleft license such as GPL, MPL, or  
Apache. This is a significant advantage for downstream licensing  
compatibility. If you want to include an Artistic licensed package  
in, for example, an MPL package, you can relicense the Artistic  
package under the MPL to include it in your package.

Section 13 minimizes the likelihood of patent litigation. We want to  
do what we can to promote our users&#039; freedoms, even though some  
people might try to take freedoms away from them by using software  
patents in unscrupulous ways.


My blog: &lt;a href=&quot;http://www.topblogposts.info&quot; target=&quot;_blank&quot;&gt;Tom&lt;/a&gt;]]></description>
			<content:encoded><![CDATA[<p><strong>Artistic License</strong><br />The Artistic 2.0 notes walk you through the new license, but they<br />
don&#8217;t specifically highlight the changes. This will make a nice<br />
addition to the FAQ.</p>
<p>Overall, the terms of the Artistic 2 are the same as the Artistic 1,<br />
though the language has been polished and reorganized to be more<br />
readable and more legally precise. The significant additions are<br />
sections 4(c)(ii) and 13.</p>
<p>Section 4(c)(ii) is what we call the &#8220;relicensing&#8221; clause, because it<br />
allows you to take a package you received under the Artistic License<br />
and use it under the terms of a copyleft license such as GPL, MPL, or<br />
Apache. This is a significant advantage for downstream licensing<br />
compatibility. If you want to include an Artistic licensed package<br />
in, for example, an MPL package, you can relicense the Artistic<br />
package under the MPL to include it in your package.</p>
<p>Section 13 minimizes the likelihood of patent litigation. We want to<br />
do what we can to promote our users&#8217; freedoms, even though some<br />
people might try to take freedoms away from them by using software<br />
patents in unscrupulous ways.</p>
<p>My blog: <a href="http://www.topblogposts.info" target="_blank">Tom</a></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
