For more explanation of why we designed this format, see the rationale.
Writing the labels page
use whatever path or filename is most convenient for you; others will
find it through links. The page must include one table marked with
id="jslicense-labels1". This name lets
automated tools find the table easily, and tells them what format to
expect. Each row of this table will contain three cells, providing
license, and how visitors can obtain its source code.
site. The cell must contain an anchor tag that links to that file,
script tags throughout the site do.
.tar.gz archive, or a
.zip archive. If a source archive includes
00-INDEX that lists the order in which individual source files
should be concatenated to produce a single file that's
served from the site, and linked from the first cell, is already in
source code form, link to the same URL again in this cell.
<table id="jslicense-labels1"> <tr> <td><a href="/js/jquery-1.7.min.js">jquery-1.7.min.js</a></td> <td><a href="//www.jclark.com/xml/copying.txt">Expat</a></td> <td><a href="/js/jquery-1.7.tar.gz">jquery-1.7.tar.gz</a></td> </tr> </table>
This page may include other text and markup, including your site's normal layout and navigation tools, but the table must be displayed prominently on it.
Links to the labels page
the labels page described above. Mark this link with the
rel="jslicense", so that automated tools can
find it. For example, your final link might look like this:
This link can be small, but it should be clearly visible to people who visit your site.
If you do these things, you will comply with the relevant conditions in the GNU software licenses, such as the GNU General Public License. They should also suffice to comply with many other free software licenses, but we can't say with certainty that they will comply with all of them. As always, please make sure you understand and follow the license conditions of any free software you distribute.