<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Get your OOXML patent license at Microsoft Licensing</title>
		<link>http://www.noooxml.org/forum/t-71428/get-your-ooxml-patent-license-at-microsoft-licensing</link>
		<description>Posts in the discussion thread &quot;Get your OOXML patent license at Microsoft Licensing&quot; - If you don&#039;t trust the OSP (Open Specification Promise), ask for a patent licence at Microsoft. &quot;If you would prefer a written license, or if the formats are not covered by the OSP, patent licenses are available by contacting iplg@microsoft.com&quot; they say on their website.</description>
				<copyright></copyright>
		<lastBuildDate>Mon, 06 Sep 2010 15:34:11 +0000</lastBuildDate>
		
					<item>
				<guid>http://www.noooxml.org/forum/t-71428#post-211732</guid>
				<title>Get your patent licence at Microsoft Licensing</title>
				<link>http://www.noooxml.org/forum/t-71428/get-your-ooxml-patent-license-at-microsoft-licensing#post-211732</link>
				<description></description>
				<pubDate>Tue, 01 Jul 2008 13:14:48 +0000</pubDate>
				<wikidot:authorName>zoobab</wikidot:authorName>				<wikidot:authorUserId>2946</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>If you don't trust the OSP (Open Specification Promise), <a href="http://msdn.microsoft.com/en-us/library/cc313153.aspx">ask for a patent license</a> at Microsoft, this is for the "Word Binary File Format (.doc) Structure Specification":</p> <blockquote> <p><strong>Patents</strong>. Microsoft has patents that may cover your implementations of the formats. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, the formats may be covered by Microsoft's Open Specification Promise (available here: <a href="http://www.microsoft.com/interop/osp">http://www.microsoft.com/interop/osp</a>). <strong>If you would prefer a written license, or if the formats are not covered by the OSP, patent licenses are available by contacting <span class="wiki-email">moc.tfosorcim|glpi#moc.tfosorcim|glpi</span>.</strong></p> </blockquote> <p>Let's try to see if requesting a RAND patent license at this email address works. The first one who manages to obtain a copy will receive a present from us.</p> <p>I have sent a request to see the terms of the RAND license, let's see how long it takes to have a copy:</p> <blockquote> <p>Benjamin Henrion &lt;bhenrion at ffii.org&gt;<br /> to iplg at microsoft.com<br /> date Tue, Jul 1, 2008 at 3:23 PM<br /> subject <strong>Request for a written license for ECMA 376 implementation</strong></p> <p><br /> Dear Microsoft Licensing,</p> <p>I would be interested to receive a copy of the terms of the proposed<br /> written patent license that you propose for the standard ECMA 376, as<br /> mentioned by one Microsoft employee on the following page:</p> <p><a href="http://doyoulovems.com/archives/64#comment-58">http://doyoulovems.com/archives/64#comment-58</a></p> <p>"Microsoft has chosen to provide implementers with three different<br /> options from which they can choose. Some companies prefer to rely on a<br /> CNS or patent pledge. Some companies (sometimes that have a large<br /> commercial operation) prefer to enter into a bi-lateral license<br /> agreement as opposed to relying on a CNS or OSP-like promise. By<br /> offering all three choices, Microsoft has tried to accommodate the<br /> different preferences of different implementers that may be based in<br /> part on differing business models."</p> <p>According to several legal analyses, the OSP is not trustable and I<br /> would prefer to see if the proposed written patent license offers<br /> better guarantees for redistribution of implementations of the<br /> standard.</p> <p>Best regards,</p> <p>—<br /> Benjamin Henrion &lt;bhenrion at ffii.org&gt;<br /> FFII Brussels - +32-484-566109 - +32-2-4148403</p> </blockquote> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>