<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Licensing and Redistribution in File Geodatabase API Questions</title>
    <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-gdb-api-licensing-and-redistribution/m-p/692955#M1107</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You probably want someone trained in legalese reading the documents and binding the company&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to abide by them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;While you shouldn't take it as fact from me, in my reading of the license, the restrictions on the &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;file geodatabase API are for *commercial redistribution* -- charging others for that which Esri &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;has given to you without charge. You are certainly free to distribute the *run-time* DLLs with &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;your binaries (royalty-free!), just not the include files and link libraries -- anyone who wants &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;them must agree to the same license (this is a common characteristic of most "open" license&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;agreements -- it levels the playing field and prevents Esri from becoming embroiled in squabbles&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;involving third or fourth parties). It probably isn't wise to assume the license terms will change&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;soon.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you wish to negotiate a different license (though it hardly seems necessary), you should&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;probably take that up with your local Esri marketing office, not with the good folks here in&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the User Forums. If your company's legal staff has interpretation questions, then the local&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;RO is still the best way to link them to Esri's contracts department.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 24 Mar 2012 00:23:39 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2012-03-24T00:23:39Z</dc:date>
    <item>
      <title>File GDB API Licensing and Redistribution</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-gdb-api-licensing-and-redistribution/m-p/692954#M1106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I work for a non-GIS software company.&amp;nbsp; Let's call it CompanyX.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am wondering whether ESRI's standard FileGDB API license agreement would permits CompanyX to redistribute the FileGDB API with CompanyX software.&amp;nbsp; If not, I am wondering whether CompanyX could sign a special license agreement and / or purchase the ability to permit this.&amp;nbsp; I am wondering whether a Business Partner agreement between CompanyX and ESRI could facilitate this. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have read ESRI's FileGDB API License Agreement, which seems to prohibit redistribution and for-profit use of the FileGDB API, but I have also read discussions on this topic in this Forum and other places which seem to make it possible, and / or suggest that the License Agreement is not written as the FileGDB Product Manager intended, and may change soon.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any assistance anyone can lend is most welcome.&amp;nbsp; You can call me at 4157101998.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you very much,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-Vince&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Mar 2012 20:47:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-gdb-api-licensing-and-redistribution/m-p/692954#M1106</guid>
      <dc:creator>VinceUlfig</dc:creator>
      <dc:date>2012-03-23T20:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing and Redistribution</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-gdb-api-licensing-and-redistribution/m-p/692955#M1107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You probably want someone trained in legalese reading the documents and binding the company&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to abide by them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;While you shouldn't take it as fact from me, in my reading of the license, the restrictions on the &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;file geodatabase API are for *commercial redistribution* -- charging others for that which Esri &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;has given to you without charge. You are certainly free to distribute the *run-time* DLLs with &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;your binaries (royalty-free!), just not the include files and link libraries -- anyone who wants &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;them must agree to the same license (this is a common characteristic of most "open" license&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;agreements -- it levels the playing field and prevents Esri from becoming embroiled in squabbles&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;involving third or fourth parties). It probably isn't wise to assume the license terms will change&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;soon.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you wish to negotiate a different license (though it hardly seems necessary), you should&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;probably take that up with your local Esri marketing office, not with the good folks here in&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the User Forums. If your company's legal staff has interpretation questions, then the local&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;RO is still the best way to link them to Esri's contracts department.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Mar 2012 00:23:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-gdb-api-licensing-and-redistribution/m-p/692955#M1107</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2012-03-24T00:23:39Z</dc:date>
    </item>
  </channel>
</rss>

