https://wiki.spdx.org/index.php?action=history&feed=atom&title=Technical_Team%2FMinutes%2F2018-02-05 2026-05-07T12:20:37Z Revision history for this page on the wiki MediaWiki 1.23.13 https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2018-02-05&diff=4678&oldid=prev 2019-02-06T18:19:58Z

<p>Created page with &quot;February 5, 2019 == Attendees == * Kate Stewart * Gary O&#039;Neall * Michael Herzog * Dennis Clark ==License Namespace Proposals== * We discussed the license namespace proposal M...&quot;</p> <p><b>New page</b></p><div>February 5, 2019<br /> == Attendees ==<br /> * Kate Stewart<br /> * Gary O'Neall<br /> * Michael Herzog<br /> * Dennis Clark<br /> <br /> ==License Namespace Proposals==<br /> * We discussed the license namespace proposal Mark Atwood circulated on the email distribution list<br /> * Since Mark was not on the call, we agreed to not finalize any proposal until we’ve had a larger review including Mark and the larger community<br /> * Those on the call reached consensus on the following items:<br /> ** We should separate the issues of referencing the license text / metadata from the issue of license list namespaced<br /> ** Solving the license list namespace was important<br /> * We discussed 3 different solutions to the namespace issue<br /> ** Mark’s proposal of using the DNS names<br /> ** Ad-hoc naming where any organization (e.g. LicenseRef-&lt;namespace&gt;-id) where any organization can use any namespace<br /> ** A registry of namespaces which contains additional metadata<br /> * We discussed a few potential issues with some of the approaches<br /> ** Uniqueness of the naming – We would like to make sure there are no name collisions<br /> ** Reability of the license ID’s – We would like the ID’s to be easily human readable and writeable<br /> ** Verifiable / secure – If we have an SPDX document references a license in a different namespace, we would like a mechanism to make sure the license hasn’t been changed<br /> ** Versioning – If the license list in a specific namespace changes (e.g. a license is removed or modified), we would like to be able to refer to the version used when creating the SPDX document<br /> * We tended to favor a registration approach<br /> ** Pro’s – can help solve the readability, uniqueness, versioning and security<br /> ** Con’s – would be slower than just using a well formed license ID since the registry would have to accept any contributions before it could be used<br /> ** Proposal to use Github as the repository for the namespace implementation<br /> ** Proposal to store the license information as an SPDX document containing the license ID’s themselves<br /> *** Alternative discussed was the Github repo would only contain a reference to an external document. This approach had issues with security and versioning.<br /> ** Directory structure could contain version information<br /> ** License ref syntax would allow mapping to a specific document<br /> ** Versioning would be optional<br /> ** Additions and updates to the namespaces would be pull requests<br /> *** We could automate the verification and possibly the acceptance of the PR’s using a build script<br /> ** Kate will propose more specifics<br /> <br /> <br /> [[Category:Technical|Minutes]]<br /> [[Category:Minutes]]</div>

Goneall