<?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>TimburyDotOrg &#187; Open standard</title>
	<atom:link href="http://timbury.org/tag/open-standard/feed/" rel="self" type="application/rss+xml" />
	<link>http://timbury.org</link>
	<description>Linux and Open Source Stuff</description>
	<lastBuildDate>Tue, 07 Sep 2010 23:10:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Lead OGG Dev Responds to Jobs&#8217; Jabs</title>
		<link>http://feedproxy.google.com/~r/IBeenToUbuntu/~3/fK3TfgLXoqQ/lead-ogg-dev-responds-to-jobs-jibes.html</link>
		<comments>http://feedproxy.google.com/~r/IBeenToUbuntu/~3/fK3TfgLXoqQ/lead-ogg-dev-responds-to-jobs-jibes.html#comments</comments>
		<pubDate>Sun, 02 May 2010 03:53:00 +0000</pubDate>
		<dc:creator>Daengbo</dc:creator>
				<category><![CDATA[syndicated]]></category>
		<category><![CDATA[Open standard]]></category>
		<category><![CDATA[Theora]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Image via CrunchBaseXiph's Gregory Maxwell, the designer and lead dev of the OGG container and the Vorbis audio and Theora video codecs, had a few choice words for Steve Jobs over his recent suggestion that OGG Theora would soon be in court over patent...]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img" style="display: block; float: right; margin-bottom: 1em; margin-left: 1em; margin-right: 1em; margin-top: 1em; width: 260px;"><a href="http://www.crunchbase.com/person/steve-jobs" rel="nofollow"><img alt="Image representing Steve Jobs as depicted in C..." height="250" src="http://www.crunchbase.com/assets/images/resized/0001/0974/10974v3-max-250x250.jpg" style="border: none; display: block;" width="250" /></a><span class="zemanta-img-attribution">Image via <a href="http://www.crunchbase.com/">CrunchBase</a></span></div>Xiph's Gregory Maxwell, the designer and lead dev of the OGG container and the <a class="zem_slink" href="http://en.wikipedia.org/wiki/Vorbis" rel="wikipedia nofollow" title="Vorbis">Vorbis</a> audio and <a class="zem_slink" href="http://en.wikipedia.org/wiki/Theora" rel="wikipedia nofollow" title="Theora">Theora</a> video codecs, had a few choice words for <a class="zem_slink" href="http://en.wikipedia.org/wiki/Steve_Jobs" rel="wikipedia nofollow" title="Steve Jobs">Steve Jobs</a> over his recent suggestion that OGG Theora would soon be in court over <a class="zem_slink" href="http://en.wikipedia.org/wiki/Patent_infringement" rel="wikipedia nofollow" title="Patent infringement">patent infringement</a>. What did Steve say, exactly?<br />
<blockquote><blockquote>&nbsp;"All video codecs are covered by patents. A patent pool is being assembled to go after Theora and other “open source” codecs now.&nbsp;Unfortunately, just because something is open source, it doesn’t mean&nbsp;or guarantee that it doesn’t infringe on others patents. An <a class="zem_slink" href="http://en.wikipedia.org/wiki/Open_standard" rel="wikipedia nofollow" title="Open standard">open&nbsp;standard</a> is different from being royalty free or open source.&nbsp;</blockquote></blockquote><blockquote><blockquote>Sent from my <a class="zem_slink" href="http://www.apple.com/ipad/" rel="homepage nofollow" title="iPad">iPad</a>"</blockquote></blockquote>Sigh. You've got to love <a class="zem_slink" href="http://www.apple.com/" rel="homepage nofollow" title="Apple">Apple</a>'s self promotion. Gregory had <a href="http://lists.xiph.org/pipermail/theora/2010-April/003766.html">this response</a> on the Theora mailing list:<br />
<blockquote>It would seem both surprising and remarkably underhanded, even&nbsp;considering the probable involved parties, to undertake constructing a&nbsp;patent pool for some product without ever consulting the vendor of&nbsp;that product: Surely no good faith effort to construct a valid and&nbsp;usable patent pool for a codec could be undertaken without contacting&nbsp;the developers of the codec.</blockquote><blockquote>In particular— according to the US Department of Justice "A licensing&nbsp;scheme premised on invalid or expired <a class="zem_slink" href="http://en.wikipedia.org/wiki/Intellectual_property" rel="wikipedia nofollow" title="Intellectual property">intellectual property rights</a>&nbsp;will not withstand antitrust scrutiny." So, even though it is apparent&nbsp;that the <a class="zem_slink" href="http://www.xiph.org/" rel="homepage nofollow" title="Xiph.Org Foundation">Xiph.org</a> or its participants would have no interest in&nbsp;receiving royalties from such a pool a failure to contact the&nbsp;developers in an effort to determine the validity of any potential&nbsp;patent claim would be unconscionable.</blockquote><blockquote>Since the developers of Theora have received no such contact, I can&nbsp;only conclude that no such effort is being undertaken and that the&nbsp;quoted statement is either a forgery, the result of a&nbsp;misunderstanding, or that the statement may be indicative of a&nbsp;dishonest and anti-competitive collusion by Apple and other H.264&nbsp;patent holders to interfere which the development, promotion, and&nbsp;utilization of unencumbered media standards.</blockquote>If you've read Gregory's <s>dissertation</s> response to accusations that OGG is a technically inferior <a class="zem_slink" href="http://en.wikipedia.org/wiki/Container_format_%28digital%29" rel="wikipedia nofollow" title="Container format (digital)">container format</a>, you'll know that he is both&nbsp;eloquent&nbsp;and confident. He goes on to say in <a href="http://lists.xiph.org/pipermail/theora/2010-April/003769.html">another e-mail from the list</a>:<br />
<blockquote>The specific standards process used to develop the MPEG codecs creates patent minefields that royalty-free codecs don't generally face. Because many knowledgeable people have heard of the problems faced by these patent-soup standards, they may extrapolate these risk to codecs developed under a different process where these problems are less considerable. This is a mistake, and I'll explain why here.&nbsp;</blockquote><blockquote>Recently there have been a number of prominent statements along the lines of "all video codecs are covered by patents" and "virtually all codecs are based on patented technology".&nbsp;</blockquote><blockquote>These statements are carefully engineered FUD spread by the license holders of competing formats in order to discourage the use of unencumbered alternatives. They are careful to avoid naming WHO owns these supposed patents or WHAT is actually patented, because such specific statements would allow the victims of this FUD to petition a court for a declaratory judgment of non-infringement.</blockquote><blockquote>This FUD is particularly effective because there _is_ a widespread misconception that media codecs are a patent minefield to a greater extent than other areas of software.&nbsp;</blockquote><blockquote>Certainly this is the case for the MPEG codecs, but it is not a universal truth. To understand why, you must understand a little about the process used to build these international standards.&nbsp;</blockquote><blockquote>The reason the MPEG formats are so thoroughly encumbered by patents is that the process used to build the formats is designed to be "blind" to patent considerations: all the participants have agreed that any patents they hold will be licensed under "Reasonable And Non-Discriminatory" terms, a term of art which few normal people would actually describe as all that reasonable or all that non-discriminatory, as RAND often means "quite expensive". With only that assurance in hand, they go about constructing their formats through an extensively political tournament process where proposals are made and encouraged to be combined.&nbsp;</blockquote><blockquote>So no effort is made to avoid patents, but it gets worse:&nbsp;</blockquote><blockquote>If you're a participant in this process, it is very important that some of your patented technology make it into the result: if it doesn't you'll end up having to pay the same royalties as the rest of the world, but if it does you can cross-license your patents with the other "winners" and completely avoid paying to use the resulting format.&nbsp;</blockquote><blockquote>So even if you're not looking to make a profit from your participation, you'll be sure to get some patents into the result so that you don't have to _pay_ for the result of your own labors.&nbsp;</blockquote><blockquote>As a result these formats end up rife with inconsequential or even detrimental patented techniques which could have _easily_ been avoided, as essential elements.&nbsp;</blockquote><blockquote>—— and this is the outcome when all of the parties are playing by the rules. For an in-depth analysis of the mess that patents are making of standardization, see: <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1134000">http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1134000</a>&nbsp;</blockquote><blockquote>It doesn't have to be this way. Most media coding patents are exceptionally narrow, as it's much cheaper and easier to obtain a very narrow patent. The fact that a patent can be trivially avoided— often by something as simple as changing the order of a process— isn't a problem for patents designed to read on standards, since the standard mandates doing it "just so".&nbsp;</blockquote><blockquote>By starting out with the premise that you want things to be royalty-free and not merely RAND, you remove the incentive structure that encourages the creation of minefields. By being cognizant of the risk and sticking close to the known safe prior art, rather than the willful patent entanglement of the MPEG process, the risk of surprise claims by third parties is also reduced.&nbsp;</blockquote><blockquote>The problem of patents isn't eliminated— they are still a costly burden on the developer of any standard, but the environment surrounding the MPEG patents is simply not a good indication of the real difficulty.&nbsp;</blockquote><blockquote>The process used by MPEG is ultimately counterproductive. By being "blind", what they are actually doing is encouraging a kind of patent cold war. At the end, even the inventors and fully paid-up licensees of those formats end up in court—fallout from playing with these dangerous toys. This can only be avoided by rejecting the taint of encumbered technology, and accepting the challenges and compromises that come from doing so. Or, in other words, the only way to win is not to play.</blockquote>Well, we certainly know where he stands on this matter. I hope he is correct, but I've got little faith in the patent system and even less in east Texas, where this fight will almost certainly be fought.<br />
<div class="zemanta-pixie" style="height: 15px; margin-top: 10px;"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/476c1336-f3c0-4d07-aca4-854aec2d2e48/" title="Reblog this post [with Zemanta]"><img alt="Reblog this post [with Zemanta]" class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=476c1336-f3c0-4d07-aca4-854aec2d2e48" style="border: none; float: right;" /></a><span class="zem-script more-related pretty-attribution"><script defer="defer" src="http://static.zemanta.com/readside/loader.js" type="text/javascript">
</script></span></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/117578413372837062-3825047704386200703?l=blog.ibeentoubuntu.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/l3yscjFUlUHeXTMNN_ygKT9FvDg/0/da"><img src="http://feedads.g.doubleclick.net/~a/l3yscjFUlUHeXTMNN_ygKT9FvDg/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/l3yscjFUlUHeXTMNN_ygKT9FvDg/1/da"><img src="http://feedads.g.doubleclick.net/~a/l3yscjFUlUHeXTMNN_ygKT9FvDg/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=fK3TfgLXoqQ:V37gTfnBXAI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=fK3TfgLXoqQ:V37gTfnBXAI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?i=fK3TfgLXoqQ:V37gTfnBXAI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=fK3TfgLXoqQ:V37gTfnBXAI:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/IBeenToUbuntu/~4/fK3TfgLXoqQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://timbury.org/2010/05/01/lead-ogg-dev-responds-to-jobs-jabs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Proposed &#8220;Ten Commandments&#8221; are very Open Source Friendly</title>
		<link>http://feedproxy.google.com/~r/IBeenToUbuntu/~3/lf5UzwrFlVc/proposed-ten-commandments-are-very-open.html</link>
		<comments>http://feedproxy.google.com/~r/IBeenToUbuntu/~3/lf5UzwrFlVc/proposed-ten-commandments-are-very-open.html#comments</comments>
		<pubDate>Tue, 24 Nov 2009 05:35:00 +0000</pubDate>
		<dc:creator>Daengbo</dc:creator>
				<category><![CDATA[syndicated]]></category>
		<category><![CDATA[Advocacy]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Open standard]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[<div class="zemanta-img" style="float: right;margin-bottom: 1em;margin-left: 1em;margin-right: 1em;margin-top: 1em;width: 310px"><a href="http://en.wikipedia.org/wiki/Image:Free_Software_and_Open_Source_Software_Composite_Logo.svg"><img alt="A composite of the GNU logo and the OSI logo, ..." height="291" src="http://upload.wikimedia.org/wikipedia/en/thumb/f/ff/Free_Software_and_Open_Source_Software_Composite_Logo.svg/300px-Free_Software_and_Open_Source_Software_Composite_Logo.svg.png" style="border: none" width="300" /></a><span class="zemanta-img-attribution">Image via <a href="http://en.wikipedia.org/wiki/Image:Free_Software_and_Open_Source_Software_Composite_Logo.svg">Wikipedia</a></span><br />
</div>Ars Technica has a short article on the UN-backed Internet Governance Forum 2009 and its <a href="http://arstechnica.com/tech-policy/news/2009/11/god-did-it-why-cant-we-un-ponders-net-10-commandments.ars?utm_source=rss&#38;utm_medium=rss&#38;utm_campaign=rss">discussion of new rules for the computing world</a>. Unsurprisingly, these proposed rules are quite FOSS-friendly since they are modeled on the early years of computing and the Internet, when <a class="zem_slink" href="http://en.wikipedia.org/wiki/Request_for_Comments" rel="wikipedia" title="Request for Comments">RFCs</a> were the norm if you wanted your tech to take off. Take a look:<br />
<span class="Apple-style-span" style="color: #333333;font-family: Arial, sans-serif;font-size: 13px;line-height: 18px"><ol><li>Independence of applications</li>
<li>New applications can be added anytime that’s a core value</li>
<li>Permissionless innovation</li>
<li>Open standards</li>
<li>Accessible and globally inclusive—anyone can use it</li>
<li>User choice—I can choose what applications I use and where I go to with them</li>
<li>Ease of use—I can use it in my language, I can use it in a device I’m familiar with</li>
<li><a class="zem_slink" href="http://en.wikipedia.org/wiki/Freedom_of_speech" rel="wikipedia" title="Freedom of speech">Freedom of expression</a></li>
<li>The ability to change rapidly</li>
<li>Trustworthy and reliable is one we have to work on; it’s got to be a core value.</li>
</ol>Your hardware should be unlocked and you should be able to add applications you want to use. Those applications shouldn't lock you into an upgrade cycle and you should be able to change whenever you want.</span><div><span class="Apple-style-span" style="color: #333333;font-family: Arial, sans-serif;font-size: 13px;line-height: 18px"><br />
</span></div><div><span class="Apple-style-span" style="color: #333333;font-family: Arial, sans-serif;font-size: 13px;line-height: 18px">It looks to me like <a class="zem_slink" href="http://en.wikipedia.org/wiki/Open_source_software" rel="wikipedia" title="Open source software">Open Source Software</a> is already there. The closed-source world is the one that needs to catch up.</span></div><div><span class="Apple-style-span" style="color: #333333;font-family: Arial, sans-serif;font-size: 13px;line-height: 18px"><br />
</span></div><div><span class="Apple-style-span" style="color: #333333;font-family: Arial, sans-serif;font-size: 13px;line-height: 18px"><br />
</span></div><div class="zemanta-pixie" style="height: 15px;margin-top: 10px"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/dd05b1ea-d2b6-4034-afdc-5cd82a2a3026/" title="Reblog this post [with Zemanta]"><img alt="Reblog this post [with Zemanta]" class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=dd05b1ea-d2b6-4034-afdc-5cd82a2a3026" style="border: none;float: right" /></a><span class="zem-script more-related pretty-attribution">
</span></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/117578413372837062-4486409541386138685?l=blog.ibeentoubuntu.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/0/da"><img src="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/0/di" border="0"></img></a><br />
<a href="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/1/da"><img src="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/1/di" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=lf5UzwrFlVc:ZtafAEcKk-E:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=lf5UzwrFlVc:ZtafAEcKk-E:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?i=lf5UzwrFlVc:ZtafAEcKk-E:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=lf5UzwrFlVc:ZtafAEcKk-E:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/IBeenToUbuntu/~4/lf5UzwrFlVc" height="1">]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img" style="display: block; float: right; margin-bottom: 1em; margin-left: 1em; margin-right: 1em; margin-top: 1em; width: 310px;"><a href="http://en.wikipedia.org/wiki/Image:Free_Software_and_Open_Source_Software_Composite_Logo.svg"><img alt="A composite of the GNU logo and the OSI logo, ..." height="291" src="http://upload.wikimedia.org/wikipedia/en/thumb/f/ff/Free_Software_and_Open_Source_Software_Composite_Logo.svg/300px-Free_Software_and_Open_Source_Software_Composite_Logo.svg.png" style="border: none; display: block;" width="300" /></a><span class="zemanta-img-attribution">Image via <a href="http://en.wikipedia.org/wiki/Image:Free_Software_and_Open_Source_Software_Composite_Logo.svg">Wikipedia</a></span><br />
</div>Ars Technica has a short article on the UN-backed Internet Governance Forum 2009 and its <a href="http://arstechnica.com/tech-policy/news/2009/11/god-did-it-why-cant-we-un-ponders-net-10-commandments.ars?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=rss">discussion of new rules for the computing world</a>. Unsurprisingly, these proposed rules are quite FOSS-friendly since they are modeled on the early years of computing and the Internet, when <a class="zem_slink" href="http://en.wikipedia.org/wiki/Request_for_Comments" rel="wikipedia" title="Request for Comments">RFCs</a> were the norm if you wanted your tech to take off. Take a look:<br />
<span class="Apple-style-span" style="color: #333333; font-family: Arial, sans-serif; font-size: 13px; line-height: 18px;"><ol><li>Independence of applications</li>
<li>New applications can be added anytime that’s a core value</li>
<li>Permissionless innovation</li>
<li>Open standards</li>
<li>Accessible and globally inclusive—anyone can use it</li>
<li>User choice—I can choose what applications I use and where I go to with them</li>
<li>Ease of use—I can use it in my language, I can use it in a device I’m familiar with</li>
<li><a class="zem_slink" href="http://en.wikipedia.org/wiki/Freedom_of_speech" rel="wikipedia" title="Freedom of speech">Freedom of expression</a></li>
<li>The ability to change rapidly</li>
<li>Trustworthy and reliable is one we have to work on; it’s got to be a core value.</li>
</ol>Your hardware should be unlocked and you should be able to add applications you want to use. Those applications shouldn't lock you into an upgrade cycle and you should be able to change whenever you want.</span><div><span class="Apple-style-span" style="color: #333333; font-family: Arial, sans-serif; font-size: 13px; line-height: 18px;"><br />
</span></div><div><span class="Apple-style-span" style="color: #333333; font-family: Arial, sans-serif; font-size: 13px; line-height: 18px;">It looks to me like <a class="zem_slink" href="http://en.wikipedia.org/wiki/Open_source_software" rel="wikipedia" title="Open source software">Open Source Software</a> is already there. The closed-source world is the one that needs to catch up.</span></div><div><span class="Apple-style-span" style="color: #333333; font-family: Arial, sans-serif; font-size: 13px; line-height: 18px;"><br />
</span></div><div><span class="Apple-style-span" style="color: #333333; font-family: Arial, sans-serif; font-size: 13px; line-height: 18px;"><br />
</span></div><div class="zemanta-pixie" style="height: 15px; margin-top: 10px;"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/dd05b1ea-d2b6-4034-afdc-5cd82a2a3026/" title="Reblog this post [with Zemanta]"><img alt="Reblog this post [with Zemanta]" class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=dd05b1ea-d2b6-4034-afdc-5cd82a2a3026" style="border: none; float: right;" /></a><span class="zem-script more-related pretty-attribution"><script defer="defer" src="http://static.zemanta.com/readside/loader.js" type="text/javascript">
</script></span></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/117578413372837062-4486409541386138685?l=blog.ibeentoubuntu.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/0/da"><img src="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/1/da"><img src="http://feedads.g.doubleclick.net/~a/0AoaW6lZ33i6L1E2cPBgU9Jad9k/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=lf5UzwrFlVc:ZtafAEcKk-E:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=lf5UzwrFlVc:ZtafAEcKk-E:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?i=lf5UzwrFlVc:ZtafAEcKk-E:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/IBeenToUbuntu?a=lf5UzwrFlVc:ZtafAEcKk-E:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/IBeenToUbuntu?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/IBeenToUbuntu/~4/lf5UzwrFlVc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://timbury.org/2009/11/24/proposed-ten-commandments-are-very-open-source-friendly/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
