My understanding is that you create a local license identifier for the
non-standard license, not for the expression.
So, your LicenseRef-0 would be the fsf-unlimited (with its text), and the file
license would be "LicenseRef-0 OR GPL-2.0".
-- zvr
-Original Message-
From:
+1 for Markdown, and +2 for reStructuredText :-)
I would see the field list feature of rst to be useful when describing the
attributes.
-- zvr
-Original Message-
From: spdx-tech-boun...@lists.spdx.org
[mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Philippe Ombredanne
Sent:
Phil,
As it was explained in the bake-off: the disclaimer (second paragraph in the
license text shown in https://spdx.org/licenses/HPND.html) is all enclosed in
square brackets ("[...]"), and therefore was considered optional. The same
happens with some individual words ("and", "that", etc.)
I think the idea has always been that we would announce the new formats and all
content that is on Github as soon as they are ready.
-- zvr –
From: Steenbergen, Thomas [mailto:thomas.steenber...@here.com]
Sent: Friday, 12 May, 2017 09:32
To: Zavras, Alexios <alexios.zav...@intel.com>
Ah, so it’s not 18:00 on the hour that Central Europe currently has (which was
8 mins ago), but 19:00…
Because we’re in CEST – fun fun fun.
-- zvr –
From: spdx-tech-boun...@lists.spdx.org
[mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Kate Stewart
Sent: Monday, 8 May, 2017 19:08
To:
Hi all,
I would like to propose a property named FileAttributionText which will hold
the text that has to be reproduced.
It can be considered as a combination of information found in properties like
FileCopyrightText, LicenseInfoInFile, FileContributor, but it might not simply
the sum of these
