{
  "isDeprecatedLicenseId": false,
  "licenseText": "The TAPR Open Hardware License\nVersion 1.0 (May 25, 2007)\nCopyright 2007 TAPR - http://www.tapr.org/OHL\n\nPREAMBLE\n\nOpen Hardware is a thing - a physical artifact, either electrical or\nmechanical - whose design information is available to, and usable by,\nthe public in a way that allows anyone to make, modify, distribute, and\nuse that thing.  In this preface, design information is called\n\"documentation\" and things created from it are called \"products.\"\n\nThe TAPR Open Hardware License (\"OHL\") agreement provides a legal\nframework for Open Hardware projects.  It may be used for any kind of\nproduct, be it a hammer or a computer motherboard, and is TAPR\u0027s\ncontribution to the community; anyone may use the OHL for their Open\nHardware project.\n\nLike the GNU General Public License, the OHL is designed to guarantee\nyour freedom to share and to create.  It forbids anyone who receives\nrights under the OHL to deny any other licensee those same rights to\ncopy, modify, and distribute documentation, and to make, use and\ndistribute products based on that documentation.\n\nUnlike the GPL, the OHL is not primarily a copyright license.  While\ncopyright protects documentation from unauthorized copying, modification,\nand distribution, it has little to do with your right to make, distribute,\nor use a product based on that documentation.  For better or worse, patents\nplay a significant role in those activities.  Although it does not prohibit\nanyone from patenting inventions embodied in an Open Hardware design, and\nof course cannot prevent a third party from enforcing their patent rights,\nthose who benefit from an OHL design may not bring lawsuits claiming that\ndesign infringes their patents or other intellectual property.\n\nThe OHL addresses unique issues involved in the creation of tangible,\nphysical things, but does not cover software, firmware, or code loaded\ninto programmable devices.  A copyright-oriented license such as the GPL\nbetter suits these creations.\n\nHow can you use the OHL, or a design based upon it?  While the terms and\nconditions below take precedence over this preamble, here is a summary:\n\n*  You may modify the documentation and make products based upon it.\n\n*  You may use products for any legal purpose without limitation.\n\n*  You may distribute unmodified documentation, but you must include the\ncomplete package as you received it.\n\n*  You may distribute products you make to third parties, if you either\ninclude the documentation on which the product is based, or make it\navailable without charge for at least three years to anyone who requests\nit.\n\n*  You may distribute modified documentation or products based on it, if\nyou:\n    *  License your modifications under the OHL.\n    *  Include those modifications, following the requirements stated\n       below.\n    *  Attempt to send the modified documentation by email to any of the\n       developers who have provided their email address.  This is a good\n       faith obligation - if the email fails, you need do nothing more\n       and may go on with your distribution.\n\n*  If you create a design that you want to license under the OHL, you\nshould:\n    *  Include this document in a file named LICENSE (with the appropriate\n       extension) that is included in the documentation package.\n    *  If the file format allows, include a notice like \"Licensed under\n       the TAPR Open Hardware License (www.tapr.org/OHL)\" in each\n       documentation file.  While not required, you should also include\n       this notice on printed circuit board artwork and the product\n       itself; if space is limited the notice can be shortened or\n       abbreviated.\n    *  Include a copyright notice in each file and on printed circuit\n       board artwork.\n    *  If you wish to be notified of modifications that others may make,\n       include your email address in a file named \"CONTRIB.TXT\" or\n       something similar.\n\n*  Any time the OHL requires you to make documentation available to\nothers, you must include all the materials you received from the\nupstream licensors.  In addition, if you have modified the\ndocumentation:\n    *  You must identify the modifications in a text file (preferably\n       named \"CHANGES.TXT\") that you include with the documentation.\n       That file must also include a statement like \"These modifications\n       are licensed under the TAPR Open Hardware License.\"\n    *  You must include any new files you created, including any\n       manufacturing files (such as Gerber files) you create in the\n       course of making products.\n    *  You must include both \"before\" and \"after\" versions of all files\n       you modified.\n    *  You may include files in proprietary formats, but you must also\n       include open format versions (such as Gerber, ASCII, Postscript,\n       or PDF) if your tools can create them.\n\nTERMS AND CONDITIONS\n\n1.   Introduction\n1.1  This Agreement governs how you may use, copy, modify, and\ndistribute Documentation, and how you may make, have made, and\ndistribute Products based on that Documentation.  As used in this\nAgreement, to \"distribute\" Documentation means to directly or indirectly\nmake copies available to a third party, and to \"distribute\" Products\nmeans to directly or indirectly give, loan, sell or otherwise transfer\nthem to a third party.\n\n1.2  \"Documentation\" includes:\n     (a) schematic diagrams;\n     (b) circuit or circuit board layouts, including Gerber and other\n         data files used for manufacture;\n     (c) mechanical drawings, including CAD, CAM, and other data files\n         used for manufacture;\n     (d) flow charts and descriptive text; and\n     (e) other explanatory material.\nDocumentation may be in any tangible or intangible form of expression,\nincluding but not limited to computer files in open or proprietary\nformats and representations on paper, film, or other media.\n\n1.3  \"Products\" include:\n     (a) circuit boards, mechanical assemblies, and other physical parts\n         and components;\n     (b) assembled or partially assembled units (including components\n         and subassemblies); and\n     (c) parts and components combined into kits intended for assembly\n         by others;\nwhich are based in whole or in part on the Documentation.\n\n1.4  This Agreement applies to any Documentation which contains a\nnotice stating it is subject to the TAPR Open Hardware License, and to\nall Products based in whole or in part on that Documentation.  If\nDocumentation is distributed in an archive (such as a \"zip\" file) which\nincludes this document, all files in that archive are subject to this\nAgreement unless they are specifically excluded.  Each person who\ncontributes content to the Documentation is referred to in this\nAgreement as a \"Licensor.\"\n\n1.5  By (a) using, copying, modifying, or distributing the\nDocumentation, or (b) making or having Products made or distributing\nthem, you accept this Agreement, agree to comply with its terms, and\nbecome a \"Licensee.\"  Any activity inconsistent with this Agreement will\nautomatically terminate your rights under it (including the immunities\nfrom suit granted in Section 2), but the rights of others who have\nreceived Documentation, or have obtained Products, directly or\nindirectly from you will not be affected so long as they fully comply\nwith it themselves.\n\n1.6  This Agreement does not apply to software, firmware, or code\nloaded into programmable devices which may be used in conjunction with\nDocumentation or Products.  Such software is subject to the license\nterms established by its copyright holder(s).\n\n2.   Patents\n2.1  Each Licensor grants you, every other Licensee, and every\npossessor or user of Products a perpetual, worldwide, and royalty-free\nimmunity from suit under any patent, patent application, or other\nintellectual property right which he or she controls, to the extent\nnecessary to make, have made, possess, use, and distribute Products.\nThis immunity does not extend to infringement arising from modifications\nsubsequently made by others.\n\n2.2  If you make or have Products made, or distribute Documentation\nthat you have modified, you grant every Licensor, every other Licensee,\nand every possessor or user of Products a perpetual, worldwide, and\nroyalty-free immunity from suit under any patent, patent application, or\nother intellectual property right which you control, to the extent\nnecessary to make, have made, possess, use, and distribute Products.\nThis immunity does not extend to infringement arising from modifications\nsubsequently made by others.\n\n2.3  To avoid doubt, providing Documentation to a third party for the\nsole purpose of having that party make Products on your behalf is not\nconsidered \"distribution,\"\\\" and a third party\u0027s act of making Products\nsolely on your behalf does not cause that party to grant the immunity\ndescribed in the preceding paragraph.\n\n2.4  These grants of immunity are a material part of this Agreement,\nand form a portion of the consideration given by each party to the\nother.  If any court judgment or legal agreement prevents you from\ngranting the immunity required by this Section, your rights under this\nAgreement will terminate and you may no longer use, copy, modify or\ndistribute the Documentation, or make, have made, or distribute\nProducts.\n\n3.   Modifications\nYou may modify the Documentation, and those modifications will become\npart of the Documentation.  They are subject to this Agreement, as are\nProducts based in whole or in part on them.  If you distribute the\nmodified Documentation, or Products based in whole or in part upon it,\nyou must email the modified Documentation in a form compliant with\nSection 4 to each Licensor who has provided an email address with the\nDocumentation.  Attempting to send the email completes your obligations\nunder this Section and you need take no further action if any address\nfails.\n\n4.   Distributing Documentation\n4.1  You may distribute unmodified copies of the Documentation in its\nentirety in any medium, provided that you retain all copyright and other\nnotices (including references to this Agreement) included by each\nLicensor, and include an unaltered copy of this Agreement.\n4.2  You may distribute modified copies of the Documentation if you\ncomply with all the requirements of the preceding paragraph and:\n     (a) include a prominent notice in an ASCII or other open format\n         file identifying those elements of the Documentation that you\n         changed, and stating that the modifications are licensed under\n         the terms of this Agreement;\n     (b) include all new documentation files that you create, as well as\n         both the original and modified versions of each file you change\n         (files may be in your development tool\u0027s native file format,\n         but if reasonably possible, you must also include open format,\n         such as Gerber, ASCII, Postscript, or PDF, versions);\n     (c) do not change the terms of this Agreement with respect to\n         subsequent licensees; and\n     (d) if you make or have Products made, include in the Documentation\n         all elements reasonably required to permit others to make\n         Products, including Gerber, CAD/CAM and other files used for\n         manufacture.\n\n5.   Making Products\n5.1  You may use the Documentation to make or have Products made,\nprovided that each Product retains any notices included by the Licensor\n(including, but not limited to, copyright notices on circuit boards).\n5.2  You may distribute Products you make or have made, provided that\nyou include with each unit a copy of the Documentation in a form\nconsistent with Section 4.  Alternatively, you may include either (i) an\noffer valid for at least three years to provide that Documentation, at\nno charge other than the reasonable cost of media and postage, to any\nperson who requests it; or (ii) a URL where that Documentation may be\ndownloaded, available for at least three years after you last distribute\nthe Product.\n\n6.   NEW LICENSE VERSIONS\nTAPR may publish updated versions of the OHL which retain the same\ngeneral provisions as the present version, but differ in detail to\naddress new problems or concerns, and carry a distinguishing version\nnumber.  If the Documentation specifies a version number which applies\nto it and \"any later version\", you may choose either that version or any\nlater version published by TAPR.  If the Documentation does not specify\na version number, you may choose any version ever published by TAPR.\nTAPR owns the copyright to the OHL, but grants permission to any person\nto copy, distribute, and use it in unmodified form.\n\n7.   WARRANTY AND LIABILITY LIMITATIONS\n7.1  THE DOCUMENTATION IS PROVIDED ON AN\"AS-IS\" BASIS WITHOUT\nWARRANTY OF ANY KIND, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  ALL\nWARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY\nWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND\nTITLE, ARE HEREBY EXPRESSLY DISCLAIMED.\n7.2  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL ANY LICENSOR\nBE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT,\nINCIDENTAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES ARISING OUT OF\nTHE USE OF, OR INABILITY TO USE, THE DOCUMENTATION OR PRODUCTS,\nINCLUDING BUT NOT LIMITED TO CLAIMS OF INTELLECTUAL PROPERTY\nINFRINGEMENT OR LOSS OF DATA, EVEN IF THAT PARTY HAS BEEN ADVISED OF THE\nPOSSIBILITY OF SUCH DAMAGES.\n7.3  You agree that the foregoing limitations are reasonable due to\nthe non-financial nature of the transaction represented by this\nAgreement, and acknowledge that were it not for these limitations, the\nLicensor(s) would not be willing to make the Documentation available to\nyou.\n7.4  You agree to defend, indemnify, and hold each Licensor harmless\nfrom any claim brought by a third party alleging any defect in the\ndesign, manufacture, or operation of any Product which you make, have\nmade, or distribute pursuant to this Agreement.\n                                 ####\n",
  "standardLicenseTemplate": "\u003c\u003cbeginOptional\u003e\u003eThe TAPR Open Hardware License Version 1.0 (May 25, 2007)\u003c\u003cendOptional\u003e\u003e \u003c\u003cvar;name\u003d\"copyright\";original\u003d\"Copyright 2007 TAPR - http://www.tapr.org/OHL\";match\u003d\".{0,5000}\"\u003e\u003e\n\nPREAMBLE\n\nOpen Hardware is a thing - a physical artifact, either electrical or mechanical - whose design information is available to, and usable by, the public in a way that allows anyone to make, modify, distribute, and use that thing. In this preface, design information is called \"documentation\" and things created from it are called \"products.\"\n\nThe TAPR Open Hardware License (\"OHL\") agreement provides a legal framework for Open Hardware projects. It may be used for any kind of product, be it a hammer or a computer motherboard, and is TAPR\u0027s contribution to the community; anyone may use the OHL for their Open Hardware project.\n\nLike the GNU General Public License, the OHL is designed to guarantee your freedom to share and to create. It forbids anyone who receives rights under the OHL to deny any other licensee those same rights to copy, modify, and distribute documentation, and to make, use and distribute products based on that documentation.\n\nUnlike the GPL, the OHL is not primarily a copyright license. While copyright protects documentation from unauthorized copying, modification, and distribution, it has little to do with your right to make, distribute, or use a product based on that documentation. For better or worse, patents play a significant role in those activities. Although it does not prohibit anyone from patenting inventions embodied in an Open Hardware design, and of course cannot prevent a third party from enforcing their patent rights, those who benefit from an OHL design may not bring lawsuits claiming that design infringes their patents or other intellectual property.\n\nThe OHL addresses unique issues involved in the creation of tangible, physical things, but does not cover software, firmware, or code loaded into programmable devices. A copyright-oriented license such as the GPL better suits these creations.\n\nHow can you use the OHL, or a design based upon it? While the terms and conditions below take precedence over this preamble, here is a summary:\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You may modify the documentation and make products based upon it.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You may use products for any legal purpose without limitation.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You may distribute unmodified documentation, but you must include the complete package as you received it.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You may distribute products you make to third parties, if you either include the documentation on which the product is based, or make it available without charge for at least three years to anyone who requests it.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You may distribute modified documentation or products based on it, if you:\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e License your modifications under the OHL.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e Include those modifications, following the requirements stated below.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e Attempt to send the modified documentation by email to any of the developers who have provided their email address. This is a good faith obligation - if the email fails, you need do nothing more and may go on with your distribution.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e If you create a design that you want to license under the OHL, you should:\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e Include this document in a file named LICENSE (with the appropriate extension) that is included in the documentation package.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e If the file format allows, include a notice like \"Licensed under the TAPR Open Hardware License (www.tapr.org/OHL)\" in each documentation file. While not required, you should also include this notice on printed circuit board artwork and the product itself; if space is limited the notice can be shortened or abbreviated.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e Include a copyright notice in each file and on printed circuit board artwork.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e If you wish to be notified of modifications that others may make, include your email address in a file named \"CONTRIB.TXT\" or something similar.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e Any time the OHL requires you to make documentation available to others, you must include all the materials you received from the upstream licensors. In addition, if you have modified the documentation:\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You must identify the modifications in a text file (preferably named \"CHANGES.TXT\") that you include with the documentation. That file must also include a statement like \"These modifications are licensed under the TAPR Open Hardware License.\"\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You must include any new files you created, including any manufacturing files (such as Gerber files) you create in the course of making products.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You must include both \"before\" and \"after\" versions of all files you modified.\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"*\";match\u003d\".{0,20}\"\u003e\u003e You may include files in proprietary formats, but you must also include open format versions (such as Gerber, ASCII, Postscript, or PDF) if your tools can create them.\n\nTERMS AND CONDITIONS\n\n1. Introduction\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"1.1\";match\u003d\".{0,20}\"\u003e\u003e This Agreement governs how you may use, copy, modify, and distribute Documentation, and how you may make, have made, and distribute Products based on that Documentation. As used in this Agreement, to \"distribute\" Documentation means to directly or indirectly make copies available to a third party, and to \"distribute\" Products means to directly or indirectly give, loan, sell or otherwise transfer them to a third party.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"1.2\";match\u003d\".{0,20}\"\u003e\u003e \"Documentation\" includes:\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(a)\";match\u003d\".{0,20}\"\u003e\u003e schematic diagrams;\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(b)\";match\u003d\".{0,20}\"\u003e\u003e circuit or circuit board layouts, including Gerber and other data files used for manufacture;\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(c)\";match\u003d\".{0,20}\"\u003e\u003e mechanical drawings, including CAD, CAM, and other data files used for manufacture;\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(d)\";match\u003d\".{0,20}\"\u003e\u003e flow charts and descriptive text; and\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(e)\";match\u003d\".{0,20}\"\u003e\u003e other explanatory material.\n\n   Documentation may be in any tangible or intangible form of expression, including but not limited to computer files in open or proprietary formats and representations on paper, film, or other media.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"1.3\";match\u003d\".{0,20}\"\u003e\u003e \"Products\" include:\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(a)\";match\u003d\".{0,20}\"\u003e\u003e circuit boards, mechanical assemblies, and other physical parts and components;\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(b)\";match\u003d\".{0,20}\"\u003e\u003e assembled or partially assembled units (including components and subassemblies); and\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(c)\";match\u003d\".{0,20}\"\u003e\u003e parts and components combined into kits intended for assembly by others; which are based in whole or in part on the Documentation.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"1.4\";match\u003d\".{0,20}\"\u003e\u003e This Agreement applies to any Documentation which contains a notice stating it is subject to the TAPR Open Hardware License, and to all Products based in whole or in part on that Documentation. If Documentation is distributed in an archive (such as a \"zip\" file) which includes this document, all files in that archive are subject to this Agreement unless they are specifically excluded. Each person who contributes content to the Documentation is referred to in this Agreement as a \"Licensor.\"\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"1.5\";match\u003d\".{0,20}\"\u003e\u003e By (a) using, copying, modifying, or distributing the Documentation, or (b) making or having Products made or distributing them, you accept this Agreement, agree to comply with its terms, and become a \"Licensee.\" Any activity inconsistent with this Agreement will automatically terminate your rights under it (including the immunities from suit granted in Section 2), but the rights of others who have received Documentation, or have obtained Products, directly or indirectly from you will not be affected so long as they fully comply with it themselves.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"1.6\";match\u003d\".{0,20}\"\u003e\u003e This Agreement does not apply to software, firmware, or code loaded into programmable devices which may be used in conjunction with Documentation or Products. Such software is subject to the license terms established by its copyright holder(s).\n\n2. Patents\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"2.1\";match\u003d\".{0,20}\"\u003e\u003e Each Licensor grants you, every other Licensee, and every possessor or user of Products a perpetual, worldwide, and royalty-free immunity from suit under any patent, patent application, or other intellectual property right which he or she controls, to the extent necessary to make, have made, possess, use, and distribute Products. This immunity does not extend to infringement arising from modifications subsequently made by others.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"2.2\";match\u003d\".{0,20}\"\u003e\u003e If you make or have Products made, or distribute Documentation that you have modified, you grant every Licensor, every other Licensee, and every possessor or user of Products a perpetual, worldwide, and royalty-free immunity from suit under any patent, patent application, or other intellectual property right which you control, to the extent necessary to make, have made, possess, use, and distribute Products. This immunity does not extend to infringement arising from modifications subsequently made by others.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"2.3\";match\u003d\".{0,20}\"\u003e\u003e To avoid doubt, providing Documentation to a third party for the sole purpose of having that party make Products on your behalf is not considered \"distribution,\"\\\" and a third party\u0027s act of making Products solely on your behalf does not cause that party to grant the immunity described in the preceding paragraph.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"2.4\";match\u003d\".{0,20}\"\u003e\u003e These grants of immunity are a material part of this Agreement, and form a portion of the consideration given by each party to the other. If any court judgment or legal agreement prevents you from granting the immunity required by this Section, your rights under this Agreement will terminate and you may no longer use, copy, modify or distribute the Documentation, or make, have made, or distribute Products.\n\n3. Modifications\n\nYou may modify the Documentation, and those modifications will become part of the Documentation. They are subject to this Agreement, as are Products based in whole or in part on them. If you distribute the modified Documentation, or Products based in whole or in part upon it, you must email the modified Documentation in a form compliant with Section 4 to each Licensor who has provided an email address with the Documentation. Attempting to send the email completes your obligations under this Section and you need take no further action if any address fails.\n\n4. Distributing Documentation\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"4.1\";match\u003d\".{0,20}\"\u003e\u003e You may distribute unmodified copies of the Documentation in its entirety in any medium, provided that you retain all copyright and other notices (including references to this Agreement) included by each Licensor, and include an unaltered copy of this Agreement.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"4.2\";match\u003d\".{0,20}\"\u003e\u003e You may distribute modified copies of the Documentation if you comply with all the requirements of the preceding paragraph and:\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(a)\";match\u003d\".{0,20}\"\u003e\u003e include a prominent notice in an ASCII or other open format file identifying those elements of the Documentation that you changed, and stating that the modifications are licensed under the terms of this Agreement;\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(b)\";match\u003d\".{0,20}\"\u003e\u003e include all new documentation files that you create, as well as both the original and modified versions of each file you change (files may be in your development tool\u0027s native file format, but if reasonably possible, you must also include open format, such as Gerber, ASCII, Postscript, or PDF, versions);\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(c)\";match\u003d\".{0,20}\"\u003e\u003e do not change the terms of this Agreement with respect to subsequent licensees; and\n\n      \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"(d)\";match\u003d\".{0,20}\"\u003e\u003e if you make or have Products made, include in the Documentation all elements reasonably required to permit others to make Products, including Gerber, CAD/CAM and other files used for manufacture.\n\n5. Making Products\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"5.1\";match\u003d\".{0,20}\"\u003e\u003e You may use the Documentation to make or have Products made, provided that each Product retains any notices included by the Licensor (including, but not limited to, copyright notices on circuit boards).\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"5.2\";match\u003d\".{0,20}\"\u003e\u003e You may distribute Products you make or have made, provided that you include with each unit a copy of the Documentation in a form consistent with Section 4. Alternatively, you may include either (i) an offer valid for at least three years to provide that Documentation, at no charge other than the reasonable cost of media and postage, to any person who requests it; or (ii) a URL where that Documentation may be downloaded, available for at least three years after you last distribute the Product.\n\n6. NEW LICENSE VERSIONS\n\nTAPR may publish updated versions of the OHL which retain the same general provisions as the present version, but differ in detail to address new problems or concerns, and carry a distinguishing version number. If the Documentation specifies a version number which applies to it and \"any later version\", you may choose either that version or any later version published by TAPR. If the Documentation does not specify a version number, you may choose any version ever published by TAPR. TAPR owns the copyright to the OHL, but grants permission to any person to copy, distribute, and use it in unmodified form.\n\n7. WARRANTY AND LIABILITY LIMITATIONS\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"7.1\";match\u003d\".{0,20}\"\u003e\u003e THE DOCUMENTATION IS PROVIDED ON AN\"AS-IS\" BASIS WITHOUT WARRANTY OF ANY KIND, TO THE EXTENT PERMITTED BY APPLICABLE LAW. ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND TITLE, ARE HEREBY EXPRESSLY DISCLAIMED.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"7.2\";match\u003d\".{0,20}\"\u003e\u003e IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL ANY LICENSOR BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES ARISING OUT OF THE USE OF, OR INABILITY TO USE, THE DOCUMENTATION OR PRODUCTS, INCLUDING BUT NOT LIMITED TO CLAIMS OF INTELLECTUAL PROPERTY INFRINGEMENT OR LOSS OF DATA, EVEN IF THAT PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"7.3\";match\u003d\".{0,20}\"\u003e\u003e You agree that the foregoing limitations are reasonable due to the non-financial nature of the transaction represented by this Agreement, and acknowledge that were it not for these limitations, the Licensor(s) would not be willing to make the Documentation available to you.\n\n   \u003c\u003cvar;name\u003d\"bullet\";original\u003d\"7.4\";match\u003d\".{0,20}\"\u003e\u003e You agree to defend, indemnify, and hold each Licensor harmless from any claim brought by a third party alleging any defect in the design, manufacture, or operation of any Product which you make, have made, or distribute pursuant to this Agreement.\n\n####\n\n",
  "name": "TAPR Open Hardware License v1.0",
  "licenseId": "TAPR-OHL-1.0",
  "crossRef": [
    {
      "match": "false",
      "url": "https://www.tapr.org/OHL",
      "isValid": true,
      "isLive": true,
      "timestamp": "2024-08-19T17:38:39Z",
      "isWayBackLink": false,
      "order": 0
    }
  ],
  "seeAlso": [
    "https://www.tapr.org/OHL"
  ],
  "isOsiApproved": false,
  "licenseTextHtml": "\n            \u003cvar class\u003d\"optional-license-text\"\u003e The TAPR Open Hardware License\n                Version 1.0 (May 25, 2007)\u003c/var\u003e\n            \u003cvar class\u003d\"replaceable-license-text\"\u003e Copyright 2007 TAPR - http://www.tapr.org/OHL\u003c/var\u003e\n            \u003cp\u003ePREAMBLE\u003c/p\u003e\n\n            \u003cp\u003eOpen Hardware is a thing - a physical artifact, either electrical or\nmechanical - whose design information is available to, and usable by,\nthe public in a way that allows anyone to make, modify, distribute, and\nuse that thing.  In this preface, design information is called\n\u0026quot;documentation\u0026quot; and things created from it are called \u0026quot;products.\u0026quot;\u003c/p\u003e\n\n            \u003cp\u003e\nThe TAPR Open Hardware License (\u0026quot;OHL\u0026quot;) agreement provides a legal\nframework for Open Hardware projects.  It may be used for any kind of\nproduct, be it a hammer or a computer motherboard, and is TAPR\u0026apos;s\ncontribution to the community; anyone may use the OHL for their Open\nHardware project.\u003c/p\u003e\n\n            \u003cp\u003e\nLike the GNU General Public License, the OHL is designed to guarantee\nyour freedom to share and to create.  It forbids anyone who receives\nrights under the OHL to deny any other licensee those same rights to\ncopy, modify, and distribute documentation, and to make, use and\ndistribute products based on that documentation.\u003c/p\u003e\n\n            \u003cp\u003e\nUnlike the GPL, the OHL is not primarily a copyright license.  While\ncopyright protects documentation from unauthorized copying, modification,\nand distribution, it has little to do with your right to make, distribute,\nor use a product based on that documentation.  For better or worse, patents\nplay a significant role in those activities.  Although it does not prohibit\nanyone from patenting inventions embodied in an Open Hardware design, and\nof course cannot prevent a third party from enforcing their patent rights,\nthose who benefit from an OHL design may not bring lawsuits claiming that\ndesign infringes their patents or other intellectual property.\u003c/p\u003e\n\n            \u003cp\u003e\nThe OHL addresses unique issues involved in the creation of tangible,\nphysical things, but does not cover software, firmware, or code loaded\ninto programmable devices.  A copyright-oriented license such as the GPL\nbetter suits these creations.\u003c/p\u003e\n\n            \u003cp\u003e\nHow can you use the OHL, or a design based upon it?  While the terms and\nconditions below take precedence over this preamble, here is a summary:\u003c/p\u003e\n\n\u003cul style\u003d\"list-style:none\"\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  You may modify the documentation and make products based upon it.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  You may use products for any legal purpose without limitation.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  You may distribute unmodified documentation, but you must include the\ncomplete package as you received it.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  You may distribute products you make to third parties, if you either\ninclude the documentation on which the product is based, or make it\navailable without charge for at least three years to anyone who requests it.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  You may distribute modified documentation or products based on it, if\nyou:\n                    \n\u003cul style\u003d\"list-style:none\"\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  License your modifications under the OHL.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  Include those modifications, following the requirements stated\n       below.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  Attempt to send the modified documentation by email to any of the\ndevelopers who have provided their email address.  This is a good\n       faith obligation - if the email fails, you need do nothing more\n       and may go on with your distribution.\n                        \u003c/li\u003e\n                    \n\u003c/ul\u003e\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  If you create a design that you want to license under the OHL, you\nshould:\n                    \n\u003cul style\u003d\"list-style:none\"\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  Include this document in a file named LICENSE (with the appropriate\n       extension) that is included in the documentation package.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  If the file format allows, include a notice like \u0026quot;Licensed under\n       the TAPR Open Hardware License (www.tapr.org/OHL)\u0026quot; in each\n       documentation file.  While not required, you should also include\n       this notice on printed circuit board artwork and the product\n       itself; if space is limited the notice can be shortened or\n       abbreviated.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  Include a copyright notice in each file and on printed circuit\n       board artwork.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  If you wish to be notified of modifications that others may make,\n       include your email address in a file named \u0026quot;CONTRIB.TXT\u0026quot; or\n       something similar.\n                        \u003c/li\u003e\n                    \n\u003c/ul\u003e\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  Any time the OHL requires you to make documentation available to\nothers, you must include all the materials you received from the\nupstream licensors.  In addition, if you have modified the\ndocumentation:\n                    \n\u003cul style\u003d\"list-style:none\"\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e  You must identify the modifications in a text file (preferably\n       named \u0026quot;CHANGES.TXT\u0026quot;) that you include with the documentation.\n       That file must also include a statement like \u0026quot;These modifications\n       are licensed under the TAPR Open Hardware License.\u0026quot;\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e You must include any new files you created, including any\n       manufacturing files (such as Gerber files) you create in the\n       course of making products.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e You must include both \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; versions of all files\n       you modified.\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e *\u003c/var\u003e You may include files in proprietary formats, but you must also\n       include open format versions (such as Gerber, ASCII, Postscript,\n       or PDF) if your tools can create them.\n                        \u003c/li\u003e\n                    \n\u003c/ul\u003e\n                \u003c/li\u003e\n            \n\u003c/ul\u003e\n            \u003cp\u003e\nTERMS AND CONDITIONS\n            \u003c/p\u003e\n\n            \u003cp\u003e\n1.   Introduction\u003c/p\u003e\n\n\u003cul style\u003d\"list-style:none\"\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 1.1\u003c/var\u003e  This Agreement governs how you may use, copy, modify, and\ndistribute Documentation, and how you may make, have made, and\ndistribute Products based on that Documentation.  As used in this\nAgreement, to \u0026quot;distribute\u0026quot; Documentation means to directly or indirectly\nmake copies available to a third party, and to \u0026quot;distribute\u0026quot; Products\nmeans to directly or indirectly give, loan, sell or otherwise transfer\n                            them to a third party.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 1.2\u003c/var\u003e  \u0026quot;Documentation\u0026quot; includes:\n                    \n\u003cul style\u003d\"list-style:none\"\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (a)\u003c/var\u003e schematic diagrams;\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (b)\u003c/var\u003e circuit or circuit board layouts, including Gerber and other\n                data files used for manufacture;\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (c)\u003c/var\u003e mechanical drawings, including CAD, CAM, and other data files\n         used for manufacture;\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (d)\u003c/var\u003e flow charts and descriptive text; and\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (e)\u003c/var\u003e other explanatory material.\n                        \u003c/li\u003e\n                    \n\u003c/ul\u003e\n                    \u003cp\u003eDocumentation may be in any tangible or intangible form of expression,\nincluding but not limited to computer files in open or proprietary\n    formats and representations on paper, film, or other media.\u003c/p\u003e\n\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 1.3\u003c/var\u003e  \u0026quot;Products\u0026quot; include:\n                    \n\u003cul style\u003d\"list-style:none\"\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (a)\u003c/var\u003e circuit boards, mechanical assemblies, and other physical parts\n    and components;\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (b)\u003c/var\u003e assembled or partially assembled units (including components\n        and subassemblies); and\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (c)\u003c/var\u003e parts and components combined into kits intended for assembly\n        by others;\n                        \u003c/li\u003e\n                    \n\u003c/ul\u003e\n    which are based in whole or in part on the Documentation.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 1.4\u003c/var\u003e  This Agreement applies to any Documentation which contains a\nnotice stating it is subject to the TAPR Open Hardware License, and to\nall Products based in whole or in part on that Documentation.  If\nDocumentation is distributed in an archive (such as a \u0026quot;zip\u0026quot; file) which\nincludes this document, all files in that archive are subject to this\nAgreement unless they are specifically excluded.  Each person who\ncontributes content to the Documentation is referred to in this\n    Agreement as a \u0026quot;Licensor.\u0026quot;\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 1.5\u003c/var\u003e  By (a) using, copying, modifying, or distributing the\nDocumentation, or (b) making or having Products made or distributing\nthem, you accept this Agreement, agree to comply with its terms, and\nbecome a \u0026quot;Licensee.\u0026quot;  Any activity inconsistent with this Agreement will\nautomatically terminate your rights under it (including the immunities\nfrom suit granted in Section 2), but the rights of others who have\nreceived Documentation, or have obtained Products, directly or\nindirectly from you will not be affected so long as they fully comply\nwith it themselves.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 1.6\u003c/var\u003e  This Agreement does not apply to software, firmware, or code\nloaded into programmable devices which may be used in conjunction with\nDocumentation or Products.  Such software is subject to the license\nterms established by its copyright holder(s).\n                \u003c/li\u003e\n            \n\u003c/ul\u003e\n            \u003cp\u003e\n2.   Patents\u003c/p\u003e\n\n\u003cul style\u003d\"list-style:none\"\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 2.1\u003c/var\u003e  Each Licensor grants you, every other Licensee, and every\npossessor or user of Products a perpetual, worldwide, and royalty-free\nimmunity from suit under any patent, patent application, or other\nintellectual property right which he or she controls, to the extent\nnecessary to make, have made, possess, use, and distribute Products.\nThis immunity does not extend to infringement arising from modifications\nsubsequently made by others.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 2.2\u003c/var\u003e  If you make or have Products made, or distribute Documentation\nthat you have modified, you grant every Licensor, every other Licensee,\nand every possessor or user of Products a perpetual, worldwide, and\nroyalty-free immunity from suit under any patent, patent application, or\nother intellectual property right which you control, to the extent\nnecessary to make, have made, possess, use, and distribute Products.\nThis immunity does not extend to infringement arising from modifications\nsubsequently made by others.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 2.3\u003c/var\u003e  To avoid doubt, providing Documentation to a third party for the\nsole purpose of having that party make Products on your behalf is not\nconsidered \u0026quot;distribution,\u0026quot;\\\u0026quot; and a third party\u0026apos;s act of making Products\nsolely on your behalf does not cause that party to grant the immunity\ndescribed in the preceding paragraph.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 2.4\u003c/var\u003e  These grants of immunity are a material part of this Agreement,\nand form a portion of the consideration given by each party to the\nother.  If any court judgment or legal agreement prevents you from\ngranting the immunity required by this Section, your rights under this\nAgreement will terminate and you may no longer use, copy, modify or\ndistribute the Documentation, or make, have made, or distribute\nProducts.\n                \u003c/li\u003e\n            \n\u003c/ul\u003e\n            \u003cp\u003e\n3.   Modifications\u003c/p\u003e\n\n            \u003cp\u003eYou may modify the Documentation, and those modifications will become\npart of the Documentation.  They are subject to this Agreement, as are\nProducts based in whole or in part on them.  If you distribute the\nmodified Documentation, or Products based in whole or in part upon it,\nyou must email the modified Documentation in a form compliant with\nSection 4 to each Licensor who has provided an email address with the\nDocumentation.  Attempting to send the email completes your obligations\nunder this Section and you need take no further action if any address\nfails.\u003c/p\u003e\n\n            \u003cp\u003e\n4.   Distributing Documentation\u003c/p\u003e\n\n\u003cul style\u003d\"list-style:none\"\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 4.1\u003c/var\u003e  You may distribute unmodified copies of the Documentation in its\nentirety in any medium, provided that you retain all copyright and other\nnotices (including references to this Agreement) included by each\nLicensor, and include an unaltered copy of this Agreement.\n                \u003c/li\u003e\n                \n\u003cli\u003e\n                    \u003cvar class\u003d\"replaceable-license-text\"\u003e 4.2\u003c/var\u003e  You may distribute modified copies of the Documentation if you\ncomply with all the requirements of the preceding paragraph and:\n                    \n\u003cul style\u003d\"list-style:none\"\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (a)\u003c/var\u003e include a prominent notice in an ASCII or other open format\n         file identifying those elements of the Documentation that you\n         changed, and stating that the modifications are licensed under\n        the terms of this Agreement;\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (b)\u003c/var\u003e include all new documentation files that you create, as well as\n         both the original and modified versions of each file you change\n         (files may be in your development tool\u0026apos;s native file format,\n         but if reasonably possible, you must also include open format,\n         such as Gerber, ASCII, Postscript, or PDF, versions);\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (c)\u003c/var\u003e do not change the terms of this Agreement with respect to\n         subsequent licensees; and\n                        \u003c/li\u003e\n                        \n\u003cli\u003e\n                            \u003cvar class\u003d\"replaceable-license-text\"\u003e (d)\u003c/var\u003e if you make or have Products made, include in the Documentation\n         all elements reasonably required to permit others to make\n         Products, including Gerber, CAD/CAM and other files used for\n        manufacture.\n                        \u003c/li\u003e\n                    \n\u003c/ul\u003e\n                \u003c/li\u003e\n            \n\u003c/ul\u003e\n            \u003cp\u003e\n5.   Making Products\u003c/p\u003e\n\n\u003cul style\u003d\"list-style:none\"\u003e\n                    \n\u003cli\u003e\n                        \u003cvar class\u003d\"replaceable-license-text\"\u003e 5.1\u003c/var\u003e  You may use the Documentation to make or have Products made,\nprovided that each Product retains any notices included by the Licensor\n(including, but not limited to, copyright notices on circuit boards).\n                    \u003c/li\u003e\n                    \n\u003cli\u003e\n                        \u003cvar class\u003d\"replaceable-license-text\"\u003e 5.2\u003c/var\u003e  You may distribute Products you make or have made, provided that\nyou include with each unit a copy of the Documentation in a form\nconsistent with Section 4.  Alternatively, you may include either (i) an\noffer valid for at least three years to provide that Documentation, at\nno charge other than the reasonable cost of media and postage, to any\nperson who requests it; or (ii) a URL where that Documentation may be\ndownloaded, available for at least three years after you last distribute\nthe Product.\n                    \u003c/li\u003e\n                \n\u003c/ul\u003e\n                \u003cp\u003e\n6.   NEW LICENSE VERSIONS\u003c/p\u003e\n\n                \u003cp\u003e\nTAPR may publish updated versions of the OHL which retain the same\ngeneral provisions as the present version, but differ in detail to\naddress new problems or concerns, and carry a distinguishing version\nnumber.  If the Documentation specifies a version number which applies\nto it and \u0026quot;any later version\u0026quot;, you may choose either that version or any\nlater version published by TAPR.  If the Documentation does not specify\na version number, you may choose any version ever published by TAPR.\nTAPR owns the copyright to the OHL, but grants permission to any person\nto copy, distribute, and use it in unmodified form.\u003c/p\u003e\n\n                \u003cp\u003e\n7.   WARRANTY AND LIABILITY LIMITATIONS\u003c/p\u003e\n\n\u003cul style\u003d\"list-style:none\"\u003e\n                    \n\u003cli\u003e\n                        \u003cvar class\u003d\"replaceable-license-text\"\u003e 7.1\u003c/var\u003e  THE DOCUMENTATION IS PROVIDED ON AN\u0026quot;AS-IS\u0026quot; BASIS WITHOUT\nWARRANTY OF ANY KIND, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  ALL\nWARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY\nWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND\nTITLE, ARE HEREBY EXPRESSLY DISCLAIMED.\n                    \u003c/li\u003e\n                    \n\u003cli\u003e\n                        \u003cvar class\u003d\"replaceable-license-text\"\u003e 7.2\u003c/var\u003e IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL ANY LICENSOR\nBE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT,\nINCIDENTAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES ARISING OUT OF\nTHE USE OF, OR INABILITY TO USE, THE DOCUMENTATION OR PRODUCTS,\nINCLUDING BUT NOT LIMITED TO CLAIMS OF INTELLECTUAL PROPERTY\nINFRINGEMENT OR LOSS OF DATA, EVEN IF THAT PARTY HAS BEEN ADVISED OF THE\n    POSSIBILITY OF SUCH DAMAGES.\n                    \u003c/li\u003e\n                    \n\u003cli\u003e\n                        \u003cvar class\u003d\"replaceable-license-text\"\u003e 7.3\u003c/var\u003e You agree that the foregoing limitations are reasonable due to\nthe non-financial nature of the transaction represented by this\nAgreement, and acknowledge that were it not for these limitations, the\nLicensor(s) would not be willing to make the Documentation available to\nyou.\n                    \u003c/li\u003e\n                    \n\u003cli\u003e\n                        \u003cvar class\u003d\"replaceable-license-text\"\u003e 7.4\u003c/var\u003e  You agree to defend, indemnify, and hold each Licensor harmless\nfrom any claim brought by a third party alleging any defect in the\ndesign, manufacture, or operation of any Product which you make, have\nmade, or distribute pursuant to this Agreement.\n                    \u003c/li\u003e\n                \n\u003c/ul\u003e\n                \u003cp\u003e\n                                 ####\u003c/p\u003e\n\n            "
}