Greetings legal and tech team,
Based on a discussion on the SPDX Spec Issue #46 <https://github.com/spdx/spdx-spec/issues/46> , I would like to bring a proposal from Bradlee to the mailing lists to name the property representing the FSF designation of a license as Free / Libra as isFsfLibre. The previous proposal was isFsfFree. Robin pointed out some ambiguity with the isFsfFree property name. You can review the conversation in the Issue link above. I've also included a forward of the original email to the tech team which provides more context and detail on the use of this term. This was discussed on the tech call and there was consensus on the call isFsfLibre is a better choice. Please let me know if there is any concern with the isFsfLibre term before Tuesday Oct. 31. Thanks, Gary From: Gary O'Neall [mailto:g...@sourceauditor.com] Sent: Friday, October 13, 2017 10:21 AM To: 'spdx-t...@lists.spdx.org' Cc: 'SPDX-legal' Subject: Issues added based on this weeks Legal Call Greetings tech team, There is a request by the FSF and approved by the legal team to add a property to the listed licenses isFsfFree to indicate if a license is identified by the Free Software Foundation as a Free / Libre license. This would be a simple Boolean type. I was going to add a pull request to the spec when I realized we don't really document other listed license properties which are used, so I added an issue to document the new property as well as the older fields already in use (e.g. isOsiApproved): https://github.com/spdx/spdx-spec/issues/46 Please let me know by Tuesday if you have any concerns about the new property name. You can either comment on the issue or reply to this thread. The field will be accessible in the JSON, RDFa, RDF/Turtle, RDF/XML, and RDFa formats of the license in addition to being exposed through the SPDX Tool Java libraries. There was also a discussion on the legal team distribution about use of parentheses in license expressions. The consensus on the thread was that the spec is not clear on the use of linefeeds, so I added two new issues to track the documentation updates. Trevor has volunteered to create a pull request for this as well as other improvements in the license expression documentation - please see the following issues for more detail: https://github.com/spdx/spdx-spec/issues/45 https://github.com/spdx/spdx-spec/issues/44 https://github.com/spdx/spdx-spec/pull/37 Gary ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: g...@sourceauditor.com
_______________________________________________ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
