Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

spec: Fix case of LicenseRef-proprietary in the spec #310

Merged
merged 1 commit into from Mar 8, 2021
Merged

spec: Fix case of LicenseRef-proprietary in the spec #310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 docs/xml/metainfo-component.xml
View file
Open in desktop
@@ -1037,14 +1037,14 @@
<listitem><para><literal>LGPL-3.0+ AND GPL-3.0+</literal></para></listitem>
<listitem><para><literal>MIT</literal></para></listitem>
<listitem><para><literal>CC-BY-SA-2.0</literal></para></listitem>
<listitem><para><literal>LicenseRef-Proprietary=https://example.com/mylicense.html</literal></para></listitem>
<listitem><para><literal>LicenseRef-proprietary=https://example.com/mylicense.html</literal></para></listitem>
</itemizedlist>
A full list of recognized licenses and their identifiers can be found at the
<ulink url="https://spdx.org/licenses/">SPDX OpenSource License Registry</ulink>.
</para>
<para>
Custom licenses which are not in the SPDX registry, like proprietary licenses, can be denoted using the <code>LicenseRef</code> notation.
<code>LicenseRef-Proprietary</code> can be used to denote a proprietary license, with an optional URL to the license text following after
<code>LicenseRef-proprietary</code> can be used to denote a proprietary license, with an optional URL to the license text following after
a <code>=</code> sign.
</para>
<para>