rel-jslicense: Difference between revisions
(added eff.org as site that is currently using rel=jslicense) |
(→Examples in the wild: add FSF.org, note use on a href) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
'''<dfn>rel=jslicense</dfn>''' is | '''<dfn>rel=jslicense</dfn>''' is a method for linking to a URL to both the license and source code for the JavaScript programs provided by a given page or site.''' | ||
== Publishers == | == Publishers == | ||
On a page that provides multiple JavaScript programs, a hyperlink to a page that provides information about those programs license and source code | On a page that provides multiple JavaScript programs, publishers should provide a visible hyperlink to a page that provides information about those programs's license and source code. | ||
For an example of how to provide such a page with licensing information (and some reasons why), see: ''[http://www.gnu.org/licenses/javascript-labels.html JavaScript License Web Label]''. | |||
=== Limitations === | === Limitations === | ||
The JavaScript Web Labels recommendation also allows for inline JavaScript; such JavaScript may not appear on the Web Labels page. | |||
== Consuming Code == | |||
Consuming code should parse for rel=jslicense per normal HTML5 parsing rules, and if present, provide a UI to the user summarizing/describing those licenses, e.g. it could tell the user if the JS on the page was all open source, a free software license, etc. | |||
== Issues == | == Issues == | ||
None currently. [[rel-jslicense-issues]] can be created if necessary, or add brief issues inline below. | |||
* ... | |||
* | == Examples in the wild == | ||
Examples of sites publishing rel=jslicense: | |||
* [https://www.eff.org/ EFF.org] (on <code>a href</code>) | |||
* [http://www.fsf.org FSF.org] (on <code>a href</code>) | |||
* ... | |||
== | == Implementations == | ||
Implementations of rel-jslicense, i.e. <span id="Consumers">consuming code</span>, UIs for publishing rel-jslicense etc. | |||
* [http://weblabels.fsf.org/defectivebydesign.org/CURRENT/ DefectiveByDesign.org javascript] | === LibreJS === | ||
While the links with rel=jslicense should link to human readable table of javascript license and source information, there is also a browser extension, [http://www.gnu.org/software/librejs/ LibreJS] designed to parse these pages and to check whether or not the JavaScript is provided under a free software license. | |||
== Research == | |||
=== Previous Examples === | |||
Examples of other various methods sites have used to markup and/or publish licenses for their javascript (provided here inline for convenience, could be moved to [[jslicense-examples]] for research archival if necessary) | |||
* [http://weblabels.fsf.org/defectivebydesign.org/CURRENT/ DefectiveByDesign.org javascript] | |||
** inline script tag in page with demarkers @licstart @licend inside /* */ JS comments | |||
** Table of rows of a link to a .js file and a link to its license | |||
* [http://h-node.org/static/licenses.html h-node.org javascript] | * [http://h-node.org/static/licenses.html h-node.org javascript] | ||
* | ** Table of rows of a link to a .js file and a link to its license | ||
== See Also == | == See Also == | ||
* | * http://www.gnu.org/software/librejs/ | ||
* http://www.gnu.org/licenses/javascript-labels.html | |||
== Related pages == | |||
* [[copyright]] | * [[copyright]] | ||
* [[rel-license]] | * [[rel-license]] | ||
{{rel-related-pages}} | |||
Latest revision as of 21:43, 2 July 2015
This article is a stub. You can help the microformats.org wiki by expanding it.
rel=jslicense is a method for linking to a URL to both the license and source code for the JavaScript programs provided by a given page or site.
Publishers
On a page that provides multiple JavaScript programs, publishers should provide a visible hyperlink to a page that provides information about those programs's license and source code.
For an example of how to provide such a page with licensing information (and some reasons why), see: JavaScript License Web Label.
Limitations
The JavaScript Web Labels recommendation also allows for inline JavaScript; such JavaScript may not appear on the Web Labels page.
Consuming Code
Consuming code should parse for rel=jslicense per normal HTML5 parsing rules, and if present, provide a UI to the user summarizing/describing those licenses, e.g. it could tell the user if the JS on the page was all open source, a free software license, etc.
Issues
None currently. rel-jslicense-issues can be created if necessary, or add brief issues inline below.
- ...
Examples in the wild
Examples of sites publishing rel=jslicense:
Implementations
Implementations of rel-jslicense, i.e. consuming code, UIs for publishing rel-jslicense etc.
LibreJS
While the links with rel=jslicense should link to human readable table of javascript license and source information, there is also a browser extension, LibreJS designed to parse these pages and to check whether or not the JavaScript is provided under a free software license.
Research
Previous Examples
Examples of other various methods sites have used to markup and/or publish licenses for their javascript (provided here inline for convenience, could be moved to jslicense-examples for research archival if necessary)
- DefectiveByDesign.org javascript
- inline script tag in page with demarkers @licstart @licend inside /* */ JS comments
- Table of rows of a link to a .js file and a link to its license
- h-node.org javascript
- Table of rows of a link to a .js file and a link to its license