<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Open Source Daily Journal &#187; Star</title>
	<atom:link href="http://opensourcedailyjournal.com/author/star/feed/" rel="self" type="application/rss+xml" />
	<link>http://opensourcedailyjournal.com</link>
	<description></description>
	<lastBuildDate>Thu, 18 Aug 2011 14:28:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>10 Criterias  on Distribution Terms</title>
		<link>http://opensourcedailyjournal.com/open-source/10-criterias-on-distribution-terms/</link>
		<comments>http://opensourcedailyjournal.com/open-source/10-criterias-on-distribution-terms/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 06:59:57 +0000</pubDate>
		<dc:creator>Star</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://opensourcedailyjournal.com/open-source/10-criterias-on-distribution-terms/</guid>
		<description><![CDATA[1. Free Redistribution 2. Source Code 3. Derived Works 4. Integrity of the Author&#8217;s Source Code 5. No Discrimination against Person or Groups 6. No Discriminations on Fields of Endeavour 7.  The Distribution of License 8.  It Must not be specific to a Product 9.   It Must not restrict other Software 10.  It Must be [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.lawsocietyblog.com/archives/99"><img src="/wp-content/uploads/scraped/45.jpg"/></a>
<p>1. Free Redistribution</p>
<p>2. Source Code</p>
<p>3. Derived Works</p>
<p>4. Integrity of the Author&#8217;s Source Code</p>
<p>5. No Discrimination against Person or Groups</p>
<p>6. No Discriminations on Fields of Endeavour</p>
<p>7.  The Distribution of License</p>
<p>8.  It Must not be specific to a Product</p>
<p>9.   It Must not restrict other Software</p>
<p>10.  It Must be Technology Neutral</p>
<p>(Source: Opensource.org)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcedailyjournal.com/open-source/10-criterias-on-distribution-terms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Standards: Compliance</title>
		<link>http://opensourcedailyjournal.com/open-source/open-standards-compliance/</link>
		<comments>http://opensourcedailyjournal.com/open-source/open-standards-compliance/#comments</comments>
		<pubDate>Sat, 19 Sep 2009 06:40:50 +0000</pubDate>
		<dc:creator>Star</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://opensourcedailyjournal.com/open-source/open-standards-compliance/</guid>
		<description><![CDATA[A. Compliance Levels To support governments and other bodies in acknowledging and selecting standards that conform to this Requirement, the OSI defines two levels of compliance: 1. OSR Compatible This indicates that the owner of the standard has self-certified that their standard conforms with this Requirement, and all Compliance Criteria. Anyone may ask the OSI [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://robertogaloppini.net/2008/07/31/open-source-conference-open-source-world-conference-2008-malaga-20-22-october/"><img src="/wp-content/uploads/scraped/47.jpg"/></a>
<p>A. Compliance Levels</p>
<p>To support governments and other bodies in acknowledging and selecting<br />
standards that conform to this Requirement, the OSI defines two levels<br />
of compliance:</p>
<p>1. OSR Compatible</p>
<p>This indicates that the owner of the standard has <strong>self-certified</strong><br />
that their standard conforms with this Requirement, and all Compliance<br />
Criteria. Anyone may ask the OSI to review an OSR Compatible standard;<br />
if the OSI finds that the standard is incompatible, the owner must either<br />
modify the standard or stop using the OSR Compatible mark.</p>
<p>2. OSR Conformant</p>
<p>This indicates the OSI has reviewed a standard, as submitted by the owner,<br />
and certified that it fully conforms to the OSR. The OSI may charge a fee<br />
to balance the costs of this certification.</p>
<p>3. Versioning</p>
<p>The OSI may, at its sole discretion, update the Criteria from time to<br />
time to ensure they continue to fulfill the intent of the Requirement.<br />
These updates will include an explicit version number, and the most<br />
current version will always be available from</p>
<p>(Source:Opensource.org)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcedailyjournal.com/open-source/open-standards-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting a License</title>
		<link>http://opensourcedailyjournal.com/open-source/getting-a-license/</link>
		<comments>http://opensourcedailyjournal.com/open-source/getting-a-license/#comments</comments>
		<pubDate>Sat, 19 Apr 2008 07:45:49 +0000</pubDate>
		<dc:creator>Star</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://opensourcedailyjournal.com/open-source/getting-a-license/</guid>
		<description><![CDATA[The License Review Process: The ultimate goal of the OSI License Review Process is to guarantee that licenses and software labeled as &#8220;open source&#8221; adapts to existing community norms and expectations. For that reason, all licenses must go through a public review process described below. The OSI Board is glad to consult with entities in [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://ringsandromancehawaiiweddings.com/link_to_getting_a_license"><img src="/wp-content/uploads/scraped/50.jpg"/></a>
<p>The License Review Process:<br />
<!-- start main content -->             <!-- begin content --></p>
<p>The ultimate goal of the OSI License Review Process is to guarantee that licenses and software labeled as &#8220;open source&#8221; adapts to existing community norms and expectations. For that reason, all licenses must go through a public review process described below. The <a href="http://opensource.org/board">OSI Board</a> is glad to consult with entities in advance to help them navigate the process and improve their license, but formal approval requires going through license-review.</p>
<h2></h2>
<p>Purpose of the Process:</p>
<ul>
<li>Guarantee approved licenses compliesto the <a href="http://opensource.org/docs/osd">Open Source Definition</a></li>
<li>Identify appropriate <a href="https://osi.osuosl.org/wiki/help/proliferation">License Proliferation Category</a></li>
<li>Disapprove vanity and duplicative Licenses</li>
<li>Ensure a thorough, transparent, and timely review (e.g., within 60 days)</li>
<li>Provide <a href="https://osi.osuosl.org/report/9">current status</a> of license review request.</li>
</ul>
<p>(Source:Opensource.org)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcedailyjournal.com/open-source/getting-a-license/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Requirements for Software</title>
		<link>http://opensourcedailyjournal.com/general/requirements-for-software/</link>
		<comments>http://opensourcedailyjournal.com/general/requirements-for-software/#comments</comments>
		<pubDate>Sat, 19 Apr 2008 06:55:39 +0000</pubDate>
		<dc:creator>Star</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://opensourcedailyjournal.com/general/requirements-for-software/</guid>
		<description><![CDATA[Criteria: 1. No Intentional Secrets 2. Availability 3. Patents 4. No Agreements 5. No OSR Incompatible Dependencies (Source:Opensource.org)]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.ebookee.com/Discovering-Real-Business-Requirements-for-Software-Project-Success_177032.html"><img src="/wp-content/uploads/scraped/46.jpg"/></a>
<p>Criteria:</p>
<p>1. No Intentional Secrets</p>
<p>2. Availability</p>
<p>3. Patents</p>
<p>4.  No Agreements</p>
<p>5. No OSR Incompatible Dependencies</p>
<p>(Source:Opensource.org)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcedailyjournal.com/general/requirements-for-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Standard:Purpose</title>
		<link>http://opensourcedailyjournal.com/open-source/open-standardpurpose/</link>
		<comments>http://opensourcedailyjournal.com/open-source/open-standardpurpose/#comments</comments>
		<pubDate>Sat, 19 Apr 2008 05:31:18 +0000</pubDate>
		<dc:creator>Star</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://opensourcedailyjournal.com/open-source/open-standardpurpose/</guid>
		<description><![CDATA[The ultimate purpose of an open standard is to increase the market for a technology by having potential consumers or suppliers of that technology to spend in it without having to either pay monopoly rent or fear litigation on trade secret, copyright, patent, or trademark causes of action. No such standard can properly be described [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.dreamhost.com/category/business/"><img src="/wp-content/uploads/scraped/48.jpg"/></a>
<p> The ultimate purpose of an open standard is to increase the market for a technology by having potential consumers or suppliers of that technology to spend in it without having to either pay monopoly rent or fear litigation on trade secret, copyright, patent, or trademark causes of action. No such standard can properly be described as &#8220;open&#8221; except to the extent it achieves these goals. The industry has learned by previous experiences that the only software-related standards to fully meet these goals are those which not only permit but encourage open-source implementations. Open-source implementations are a quality and honesty check for any open standard that might be applied in software; whether an application programming interface, a hardware interface, a file format, a communication protocol, a specification of user interactions, or any other form of data interchange and program control. To support industry participants (suppliers, consumers, and regulators) identify and specify standards that permit open source implementations, the OSI has specified a minimal Open Standards Requirement (OSR). The OSI has also made a set of Criteria that can be used to judge whether a standard fully abides with that Requirement.</p>
<p>(Source:Opensource.org)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcedailyjournal.com/open-source/open-standardpurpose/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New &amp; Upcoming Open Source Softwares</title>
		<link>http://opensourcedailyjournal.com/open-source/new-upcoming-open-source-softwares/</link>
		<comments>http://opensourcedailyjournal.com/open-source/new-upcoming-open-source-softwares/#comments</comments>
		<pubDate>Sat, 19 Apr 2008 05:20:59 +0000</pubDate>
		<dc:creator>Star</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://opensourcedailyjournal.com/open-source/new-upcoming-open-source-softwares/</guid>
		<description><![CDATA[1. Fedora 9 2. Phoronix Test Suite 0.3.0 3. Ubuntu 8.04 4. Picasa 2.7 (Source:Lxer.com)]]></description>
			<content:encoded><![CDATA[<p><a href="http://symbian-applications.blogspot.com/2008_01_01_archive.html"><img src="/wp-content/uploads/scraped/49.jpg"/></a>
<p>1. Fedora 9</p>
<p>2. Phoronix Test Suite 0.3.0</p>
<p>3. Ubuntu 8.04</p>
<p>4. Picasa 2.7</p>
<p>(Source:Lxer.com)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcedailyjournal.com/open-source/new-upcoming-open-source-softwares/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

