https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2011-01-25&feed=atom&action=historyTechnical Team/Minutes/2011-01-25 - Revision history2024-03-29T11:40:32ZRevision history for this page on the wikiMediaWiki 1.23.13https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2011-01-25&diff=887&oldid=prevMartinMichlmayr: Convert to MediaWiki syntax2013-03-06T12:56:51Z<p>Convert to MediaWiki syntax</p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 12:56, 6 March 2013</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"><p>Minutes 1/25/2011</p><p></del>Attendees<del class="diffchange diffchange-inline">:</p><p></del>Bill Schineller<del class="diffchange diffchange-inline"><br /></del>Gary O'Neall<del class="diffchange diffchange-inline"><br /></del>Peter Williams<del class="diffchange diffchange-inline"><br /></del>Kate Stewart<del class="diffchange diffchange-inline"></p><p></del>Summary of follow-up items from the call<del class="diffchange diffchange-inline">:</p><ul><li></del>License section - consider renaming non-standard licenses to embedded licenses - has implications on the short form names.<del class="diffchange diffchange-inline">&nbsp; </del>Todo: Kate to follow-up on the proposal.<del class="diffchange diffchange-inline">&nbsp; </li><li></del>Document and review the algorithm for creating the xor'd sha1's from the file list<del class="diffchange diffchange-inline"></li><li></del>Change the description in the source information field in the package section<del class="diffchange diffchange-inline"></li><li></del>Discuss/decide if the package level asserted license should be optional or mandatory<del class="diffchange diffchange-inline"></li><li></del>Rename "asserted license" to "asserted licensing"<del class="diffchange diffchange-inline"></li><li></del>Future topic- should there be additional optional fields for non-standard licenses?<del class="diffchange diffchange-inline"></li><li></del>Add a comment for the reviewer in the review section<del class="diffchange diffchange-inline"></li><li></del>Reconcile the tag names with the SPDX overview<del class="diffchange diffchange-inline"></li><li></del>consider a more consistent naming convention<del class="diffchange diffchange-inline"></li></ul><p></del>Minute details<del class="diffchange diffchange-inline">:</p><p></del>Review spdx overview slides sent by Kate - purpose to align on the current status of the spec:<del class="diffchange diffchange-inline"><br />&nbsp;</del>Section Headers in the spec - Reviewer information has been moved to a separate section at the end<del class="diffchange diffchange-inline"><br />&nbsp;</del>License section - consider renaming non-standard licenses to embedded licenses - has implications on the short form names.<del class="diffchange diffchange-inline">&nbsp; </del>Todo: Kate to follow-up on the proposal.<del class="diffchange diffchange-inline">&nbsp; </del>Note that embedded is somewhat ambiguous - used for "embedded in the package" as opposed to "embedded in the SPDX file"<del class="diffchange diffchange-inline"><br />&nbsp;</del>Identification section - Version of SPDX - does it make sense in the RDF spec?<del class="diffchange diffchange-inline">&nbsp; </del>Topic for future discussion.<del class="diffchange diffchange-inline"><br />&nbsp;</del>Identification section - Method of xor for all file sha's to generate overall checksum - need to publish and review the specific algorithm<del class="diffchange diffchange-inline"><br />&nbsp;</del>The package file sha is optional in case the spdx file is embedded<del class="diffchange diffchange-inline"><br />&nbsp;</del>Source information - change description to reflect additional information on the source rather than anomalies (e.g. the download URL is no longer available)<del class="diffchange diffchange-inline"><br />&nbsp;</del>Package level - agree to add asserted license<del class="diffchange diffchange-inline"><br />&nbsp;&nbsp;</del>Asserted may include logic (and/or disjunctive/etc)<del class="diffchange diffchange-inline"><br />&nbsp;&nbsp;</del>Seen licenses would just be a list<del class="diffchange diffchange-inline"><br />&nbsp;&nbsp;</del>Not clear if asserted license at the package level should be mandatory or optional - future discussion<del class="diffchange diffchange-inline"><br />&nbsp;</del>Copyright - just a string for release 1 of SPDX<del class="diffchange diffchange-inline"><br />&nbsp;<br />&nbsp;</del>Should there be additional optional tags in the non-standard license?<del class="diffchange diffchange-inline">&nbsp; </del>Topic for a future proposal.<del class="diffchange diffchange-inline"><br />&nbsp;</del>File - Asserted License <del class="diffchange diffchange-inline">-&gt; </del>Asserted Licensing (takes care of possibility of multiple licenses)<del class="diffchange diffchange-inline"><br />&nbsp;</del>File - Seen license - can be multiple licenses<del class="diffchange diffchange-inline"><br />&nbsp;&nbsp;</del>Cardinality - does it make sense to have a mandatory field that may contain 0 items<del class="diffchange diffchange-inline">&nbsp; </del>- yes since it confirms that "none were found"<del class="diffchange diffchange-inline"><br />&nbsp;</del>Reviews - should there be a comment for the reviewer?<del class="diffchange diffchange-inline">&nbsp; </del>Yes - add this as an optional field.<del class="diffchange diffchange-inline"></p><p></del>Todo: reconcile the tag names with the spdx overview<del class="diffchange diffchange-inline"><br /></del>Need a better naming convention - add to topic for next week's call - suggestion to invite the individual providing the feedback to the call.<del class="diffchange diffchange-inline"></p></del></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== </ins>Attendees <ins class="diffchange diffchange-inline">==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Bill Schineller</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Gary O'Neall</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Peter Williams</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Kate Stewart</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== </ins>Summary of follow-up items from the call <ins class="diffchange diffchange-inline">==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>License section - consider renaming non-standard licenses to embedded licenses - has implications on the short form names. Todo: Kate to follow-up on the proposal.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Document and review the algorithm for creating the xor'd sha1's from the file list</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Change the description in the source information field in the package section</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Discuss/decide if the package level asserted license should be optional or mandatory</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Rename "asserted license" to "asserted licensing"</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Future topic- should there be additional optional fields for non-standard licenses?</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Add a comment for the reviewer in the review section</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Reconcile the tag names with the SPDX overview</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>consider a more consistent naming convention</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== </ins>Minute details <ins class="diffchange diffchange-inline">==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Review spdx overview slides sent by Kate - purpose to align on the current status of the spec:</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Section Headers in the spec - Reviewer information has been moved to a separate section at the end</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>License section - consider renaming non-standard licenses to embedded licenses - has implications on the short form names. Todo: Kate to follow-up on the proposal. Note that embedded is somewhat ambiguous - used for "embedded in the package" as opposed to "embedded in the SPDX file"</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Identification section - Version of SPDX - does it make sense in the RDF spec? Topic for future discussion.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Identification section - Method of xor for all file sha's to generate overall checksum - need to publish and review the specific algorithm<ins class="diffchange diffchange-inline">.  </ins>The package file sha is optional in case the spdx file is embedded</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Source information - change description to reflect additional information on the source rather than anomalies (e.g. the download URL is no longer available)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Package level - agree to add asserted license<ins class="diffchange diffchange-inline">. </ins>Asserted may include logic (and/or disjunctive/etc)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>Seen licenses would just be a list</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>Not clear if asserted license at the package level should be mandatory or optional - future discussion</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Copyright - just a string for release 1 of SPDX</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Should there be additional optional tags in the non-standard license? Topic for a future proposal.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>File - Asserted License <ins class="diffchange diffchange-inline">→ </ins>Asserted Licensing (takes care of possibility of multiple licenses)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>File - Seen license - can be multiple licenses</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Cardinality - does it make sense to have a mandatory field that may contain 0 items - yes since it confirms that "none were found"</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Reviews - should there be a comment for the reviewer? Yes - add this as an optional field.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Todo: reconcile the tag names with the spdx overview</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Need a better naming convention - add to topic for next week's call - suggestion to invite the individual providing the feedback to the call.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[[Category:Technical|Minutes]]</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[[Category:Minutes]]</ins></div></td></tr>
</table>MartinMichlmayrhttps://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2011-01-25&diff=886&oldid=prevGoneall at 22:18, 25 January 20112011-01-25T22:18:36Z<p></p>
<p><b>New page</b></p><div><p>Minutes 1/25/2011</p><p>Attendees:</p><p>Bill Schineller<br />Gary O'Neall<br />Peter Williams<br />Kate Stewart</p><p>Summary of follow-up items from the call:</p><ul><li>License section - consider renaming non-standard licenses to embedded licenses - has implications on the short form names.&nbsp; Todo: Kate to follow-up on the proposal.&nbsp; </li><li>Document and review the algorithm for creating the xor'd sha1's from the file list</li><li>Change the description in the source information field in the package section</li><li>Discuss/decide if the package level asserted license should be optional or mandatory</li><li>Rename "asserted license" to "asserted licensing"</li><li>Future topic- should there be additional optional fields for non-standard licenses?</li><li>Add a comment for the reviewer in the review section</li><li>Reconcile the tag names with the SPDX overview</li><li>consider a more consistent naming convention</li></ul><p>Minute details:</p><p>Review spdx overview slides sent by Kate - purpose to align on the current status of the spec:<br />&nbsp;Section Headers in the spec - Reviewer information has been moved to a separate section at the end<br />&nbsp;License section - consider renaming non-standard licenses to embedded licenses - has implications on the short form names.&nbsp; Todo: Kate to follow-up on the proposal.&nbsp; Note that embedded is somewhat ambiguous - used for "embedded in the package" as opposed to "embedded in the SPDX file"<br />&nbsp;Identification section - Version of SPDX - does it make sense in the RDF spec?&nbsp; Topic for future discussion.<br />&nbsp;Identification section - Method of xor for all file sha's to generate overall checksum - need to publish and review the specific algorithm<br />&nbsp;The package file sha is optional in case the spdx file is embedded<br />&nbsp;Source information - change description to reflect additional information on the source rather than anomalies (e.g. the download URL is no longer available)<br />&nbsp;Package level - agree to add asserted license<br />&nbsp;&nbsp;Asserted may include logic (and/or disjunctive/etc)<br />&nbsp;&nbsp;Seen licenses would just be a list<br />&nbsp;&nbsp;Not clear if asserted license at the package level should be mandatory or optional - future discussion<br />&nbsp;Copyright - just a string for release 1 of SPDX<br />&nbsp;<br />&nbsp;Should there be additional optional tags in the non-standard license?&nbsp; Topic for a future proposal.<br />&nbsp;File - Asserted License -&gt; Asserted Licensing (takes care of possibility of multiple licenses)<br />&nbsp;File - Seen license - can be multiple licenses<br />&nbsp;&nbsp;Cardinality - does it make sense to have a mandatory field that may contain 0 items&nbsp; - yes since it confirms that "none were found"<br />&nbsp;Reviews - should there be a comment for the reviewer?&nbsp; Yes - add this as an optional field.</p><p>Todo: reconcile the tag names with the spdx overview<br />Need a better naming convention - add to topic for next week's call - suggestion to invite the individual providing the feedback to the call.</p></div>Goneall