Another planned change to the license generation
|
Die 13. 11. 20 et hora 09:19 Alexios Zavras scripsit:
We should emphasize the matching guidelines even more, because people mightIf I understand the thread correctly, I agree with Alexios and would add that esp. the plain text versions are used not just for tooling to match, but also as canonical(-ish) license texts, e.g. in REUSE. cheers, Matija -- gsm: tel:+386.41.849.552 www: https://matija.suklje.name xmpp: matija.suklje@... sip: matija_suklje@... |
|
|
|
Alexios Zavras
We should emphasize the matching guidelines even more, because people might get tempted to simply use complete text file matching…
Even better, we should promote the use of “standard” implementations of license matching 😉
-- zvr
From: Spdx-legal@... <Spdx-legal@...>
On Behalf Of Gary O'Neall
Sent: Friday, 13 November, 2020 07:17 To: spdx-legal@... Subject: Another planned change to the license generation
One of the most requested enhancements for the license list data is to retain the original formatting for the license text in the JSON and other data formats.
I plan to update the tools to use the license text verbatim from the text files used to compare the license XML rather than formatting the text from the license list XML document. Since most of these text files were verbatim copies from the original source with the original formatting, it should go quite a way to resolving this issue.
This will NOT affect the HTML pages, only the text field in the license list data files.
Please let me know if you see any issue with this approach or have any concerns.
------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: gary@... CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
Intel Deutschland GmbH |
|
|
|
Gary O'Neall
One of the most requested enhancements for the license list data is to retain the original formatting for the license text in the JSON and other data formats.
I plan to update the tools to use the license text verbatim from the text files used to compare the license XML rather than formatting the text from the license list XML document. Since most of these text files were verbatim copies from the original source with the original formatting, it should go quite a way to resolving this issue.
This will NOT affect the HTML pages, only the text field in the license list data files.
Please let me know if you see any issue with this approach or have any concerns.
------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: gary@... CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
|
|
|