https://wiki.spdx.org/index.php?action=history&feed=atom&title=Technical_Team%2FMinutes%2F2020-01-28Technical Team/Minutes/2020-01-28 - Revision history2026-05-07T12:25:45ZRevision history for this page on the wikiMediaWiki 1.23.13https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2020-01-28&diff=4771&oldid=prevGoneall: Created page with "January 28, 2020 == Attendees == * Gary O’Neall * Rose Judge * Jim Hutchison * Nisha Kumar * Steve Winslow * Thomas Steenbergen ==2.2 Release== * Issue #173: TEST_OF relat..."2020-01-28T21:04:29Z<p>Created page with "January 28, 2020 == Attendees == * Gary O’Neall * Rose Judge * Jim Hutchison * Nisha Kumar * Steve Winslow * Thomas Steenbergen ==2.2 Release== * Issue #173: TEST_OF relat..."</p>
<p><b>New page</b></p><div>January 28, 2020<br />
== Attendees ==<br />
* Gary O’Neall <br />
* Rose Judge<br />
* Jim Hutchison<br />
* Nisha Kumar<br />
* Steve Winslow<br />
* Thomas Steenbergen<br />
<br />
==2.2 Release==<br />
* Issue #173: TEST_OF relatiohip type – reviewed wording - merged in the changes and closed the issue<br />
* Issue #155: Simplified tag/value syntax for enumerations - merged in the changes and closed the issue<br />
* Issue #188: How to include package, file and snippet information into JSON/YAML<br />
** YAML and JSON typically uses an array approach while XML typically uses a type approach<br />
** Agreed to use the arrays approach for YAML and JSON<br />
* Issue #189: How compact should the JSON/YAML versions of the SPDX document be?<br />
** Agreed machine readability for these formats was an important consideration<br />
** Steve raised the issue that any duplicate definitions of an SPDX item may lead to inconsistencies in the document<br />
** Compact version seems less prone to error and in some cases more efficient<br />
** Agreed to go with the compact version<br />
** Discussed allowing multiple options, but agreed that this would introduce more property names/complexity<br />
* Discussed the package hasFile property – should it be replaced by a contains relationship<br />
** Consensus that using the relationships would be more consistent<br />
** Discussed whether changing from hasFile would be a breaking change<br />
*** Possible to convert from hasFile to relationship, but converting back may not result in the same tag/value document<br />
** Agreed to keep the hasFile property in JSON and YAML for 2.2 and propose changing to relationships in 3.0<br />
<br />
[[Category:Technical|Minutes]]<br />
[[Category:Minutes]]</div>Goneall