<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi Vaclav, all,</div>
<div> </div>
<div>I would advise to include both a CFF _and_ a Codemeta linked data json file.</div>
<div> </div>
<div>Reason: CFF is a front-end format, while codemeta-json is a back-end format. The linked data file can be automatically created from the initial CFF.</div>
<div> </div>
<div>CFF is the right format for the initial provision of the software citation metadata. In a follow up-step its content should be included as a codemeta.json file as linked data into the machine-actioned downstream citation workflow. This allows to translate the metadata into multiple software metadata dialects (https://codemeta.github.io/crosswalk/).</div>
<div>The codemeta.json will also be recognized and used by the Zenodo hooks as part of the DOI-publication process.</div>
<div> </div>
<div>The CFF should be created first (generator here: https://citation-file-format.github.io/cff-initializer-javascript/).</div>
<div>A codemeta.json file can be derived from the CCF by a converter: https://github.com/citation-file-format/cff-converter-python or https://pypi.org/project/cffconvert/</div>
<div> </div>
<div>For the DOI, I believe there should be (at least) one central DOI for the "general concept" of GRASS GIS. There can be additional GRASS-GIS-releated DOIs (later) for specific releases/versions. </div>
<div> </div>
<div>Best,</div>
<div>peter</div>
<div> </div>
<div> </div>
<div class="signature"><peter.loewe@gmx.de></div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Sonntag, 06. Juni 2021 um 05:33 Uhr<br/>
<b>Von:</b> "Vaclav Petras" <wenzeslaus@gmail.com><br/>
<b>An:</b> "Peter Löwe" <peter.loewe@gmx.de><br/>
<b>Cc:</b> "grass-dev@lists.osgeo.org" <grass-dev@lists.osgeo.org><br/>
<b>Betreff:</b> Re: Re: [release planning] Enable Zenodo before 7.8.6 and 8.0.0</div>
<div name="quoted-content">
<div>
<div>Hi Peter, all, thanks for the answers. I have more questions assuming that's okay.</div>
<div class="gmail_quote">
<div>On Fri, Jun 4, 2021 at 2:57 AM Peter Löwe <<a href="mailto:peter.loewe@gmx.de" onclick="parent.window.location.href='mailto:peter.loewe@gmx.de'; return false;" target="_blank">peter.loewe@gmx.de</a>> wrote:</div>
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0.0px 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div>
<div class="gmail_quote">
<div>==> the CodeMeta-Project is currenlty pushing software citation standards: <a href="https://codemeta.github.io/" target="_blank">https://codemeta.github.io/</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div> </div>
<div>Thanks. The roles there seem to be more clear. Any opinion on CodeMata versus CFF (see also below)?</div>
<div> </div>
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0.0px 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>BTW, ways to retro-provide DOI versioning for previous GRASS releases would be an rewarding topic to discuss with Data Cite (the DOI infrastructure community).</div>
</div>
</div>
</blockquote>
<div> </div>
<div>Any opinions on how useful this is? We want a good archive of old versions, but does someone need DOIs for old releases?</div>
<div> </div>
<div>==> This depends on wether the community wants to give due credit by citation to the persons which were involved in the previous releases.</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div> </div>
<div>Currently, the author list maintained in the source code is cumulative as far as I know, so old authors are still included as authors, so only use cases for that would be citing old releases in paper or by the new versions of software software. None seem likely to me. What do you think?</div>
<div> </div>
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0.0px 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div> </div>
</div>
</div>
</blockquote>
<div>Any suggestions on includings DOI into source code? It seems to me that you can only use the generic/concept one and tell people to get the recent one. I didn't figure out the DOI reservation for GitHub repos.</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div> </div>
<div>Rather than where to put it - although that's important, too - my question is about which DOI? The main one everywhere or somehow try to put there the version specific one if that's even possible. It seems to me that the main DOI is the only feasible option.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin: 0.0px 0.0px 0.0px 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0.0px 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div>
<div class="gmail_quote">
<div>==> A JSON file could be included. This way, the information is both readable for humans and automated access: <a href="https://codemeta.github.io/codemeta-generator/" target="_blank">https://codemeta.github.io/codemeta-generator/</a> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div> </div>
<div>I was thinking about the Citation File Format as I have seen it used quite a bit. Any opinions on that?</div>
<div> </div>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>