<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Hello Max, Matija,</p>
<p><br>
</p>
<p>from what I understand there will be further changes in SPDX 3.0 that will remove some of the mandatory stuff. I absolutely agree, that using SPDX should not add stuff not needed for the use case. And if this means that the SPDX file is not correct because
some mandatory stuff is not included, this is a good hint for the SPDX community to think about the need for a mandatory field for the information.</p>
<p><br>
</p>
<p>Saying that, my basic intention is, that a REUSE.yaml file should not define fields and structures, which have the same meaning but are defined differently from SPDX. This would improve readability and processability of the files.</p>
<p><br>
</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Arial,Helvetica,sans-serif,"EmojiFont","Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div><span style="font-size:10pt">Mit freundlichen Grüßen / Best regards </span><br>
<br>
<b><span style="font-size:10pt">Dr. Lars Geyer-Blaumeiser</span></b><br>
<br>
<span style="font-size:10pt">Project Delivery - Open Source Services (IOC/PDL4) </span>
<br>
<span style="font-size:10pt">Bosch.IO GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY |
</span><span style="font-size:10pt"></span><span style="font-size:10pt">www.bosch.io
</span><br>
<span style="font-size:10pt">Mobil +49 172 4815079 | lars.geyer-blaumeiser@bosch.io
</span><br>
<br>
<span style="font-size:8pt">Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B</span><br>
<span style="font-size:8pt">Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Dr. Aleksandar Mitrovic, Yvonne Reckling</span><br>
<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> REUSE <reuse-bounces@lists.fsfe.org> im Auftrag von Max Mehl <max.mehl@fsfe.org><br>
<b>Gesendet:</b> Donnerstag, 23. Juli 2020 15:04:02<br>
<b>An:</b> reuse@lists.fsfe.org<br>
<b>Betreff:</b> Re: [REUSE] REUSE.yaml</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">~ Matija Šuklje [2020-07-22 13:54 +0200]:<br>
> Die 21. 07. 20 et hora 08:44 Geyer-Blaumeiser Lars (IOC/PDL4) scripsit:<br>
>> I like the idea, but just a thought. There is the new yaml format in SPDX<br>
>> 2.2, and we are thinking around using this format to mark certain folders<br>
>> as open source component,<br>
> <br>
> That is a great idea.<br>
<br>
Yes, thanks for sharing this idea! Being compatible with other<br>
compliance projects is one of our core goals.<br>
<br>
> But you’d really go make a full SPDX valid file for that? How? There are <br>
> quite a few fields there that are obligatory.<br>
> <br>
> One potential issue might be the hash value. For marking 3rd party code that’s <br>
> a great boon, but for marking your own living code that might be a bit of a <br>
> issue, if you need to change the hash value every time the code changes.<br>
<br>
I see the same issues. Additionally, I am always having<br>
user-friendliness in mind which is another big goal of REUSE. The SPDX<br>
document seems to work with e.g. "licenseId", "licenseConcluded",<br>
"licenseDeclared". While these make sense in the SPDX radius, REUSE<br>
users are used to work with License-Identifier and FileCopyrightText.<br>
Just like with the snippets I am afraid of different "keys" for the same<br>
information.<br>
<br>
Best,<br>
Max<br>
<br>
-- <br>
Max Mehl - Programme Manager - Free Software Foundation Europe<br>
Contact and information: <a href="https://fsfe.org/about/mehl">https://fsfe.org/about/mehl</a> | @mxmehl<br>
Become a supporter of software freedom: <a href="https://fsfe.org/join">https://fsfe.org/join</a><br>
_______________________________________________<br>
REUSE mailing list<br>
REUSE@lists.fsfe.org<br>
<a href="https://lists.fsfe.org/mailman/listinfo/reuse">https://lists.fsfe.org/mailman/listinfo/reuse</a><br>
<br>
This mailing list is covered by the FSFE's Code of Conduct. All<br>
participants are kindly asked to be excellent to each other:<br>
<a href="https://fsfe.org/about/codeofconduct">https://fsfe.org/about/codeofconduct</a><br>
</div>
</span></font>
</body>
</html>