Technical Team/Minutes/2011-03-08 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-06T12:56:51Z

Convert to MediaWiki syntax

Goneall at 19:18, 9 March 2011

2011-03-09T19:18:57Z

New page

Minutes 2/22/2011 Attendees: Ann ThortonKristin NewcomerBill SchinellerPeter WilliamsKate StewartGary O'Neall Agenda:Compare the models provided by Kate (attached) and the models from the email threadReview/discuss the SPDX Names spreadsheet provided by Kate (attached) Model discussion:  There were a lot of similarities between the proposed models. Two differences in the models were discussed:1.      Abstract License which subclasses a non-standard license and a standard license vs. a License object with one subclass for standard license.2.      Representing the license reference text – either as the text in the non-standard license or text in a LicenseInfo object. For #2 – The scope was discussed as to whether text for licenses not in the standard license list and not in the file itself.  The scenario discussed was if text was found in a file referencing a license which is not in the SPDX standard list of licenses, is there a way to represent the text of the license which is not in the file itself.  This was described as out of scope which raised some concerns.  Kate raised a concern that if this was in scope, there would be issues with the ID. We agreed that it was confusing to have the name of the referenced license text “Non-Standard License”.  Various names were discussed and we agreed to change name of Non-Standard License to “License Reference”. Kate to follow-up on updating the diagram based on the discussion.  Once that is done we can revisit the scope question and the need for Abstract License. Kate provided a spreadsheet that compared the names for the SPDX properties used by RDF/XML, Tag/Value and the spreadsheet. Peter agreed to fill in the RDF/XML column and update the git repository version of the spec with the resultant names.

← Older revision		Revision as of 12:56, 6 March 2013
Line 1:		Line 1:
−	~~<p class~~=~~"MsoNormal" style~~="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Minutes 2/22/2011</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Attendees~~:</span></p><p class~~=~~"MsoNormal" style~~="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Ann Thorton~~</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Kristin Newcomer~~</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Bill Schineller~~</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Peter Williams~~</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Kate Stewart~~</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Gary O'Neall~~</span></p><p class~~=~~"MsoNormal" style~~="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Agenda~~:</span></p><p class~~=~~"MsoNormal" style~~=~~"margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Compare the models provided by Kate (attached)~~ ~~and the models from the email thread~~</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">~~Review/discuss the SPDX Names spreadsheet provided by Kate (attached)</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Model discussion: </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">There were a lot of similarities between the proposed models.</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Two differences in the models were discussed:</span></p><p class="MsoListParagraphCxSpFirst" style="text-indent: -0.25in; margin: 0in 0in 0pt 0.5in; mso-list: l0 level1 lfo1;"><span style="font-family: Times New Roman;"><span style="mso-fareast-font-family: 'Times New Roman';"><span style="mso-list: Ignore;"><span style="font-size: small;">1.</span><span style="font: 7pt "Times New Roman";">      </span></span></span><span style="font-size: small;">Abstract License which subclasses a non-standard license and a standard license vs. a License object with one subclass for standard license.</span></span></p><p class="MsoListParagraphCxSpLast" style="text-indent: -0.25in; margin: 0in 0in 0pt 0.5in; mso-list: l0 level1 lfo1;"><span style="font-family: Times New Roman;"><span style="mso-fareast-font-family: 'Times New Roman';"><span style="mso-list: Ignore;"><span style="font-size: small;">2.</span><span style="font: 7pt "Times New Roman";">      </span></span></span><span style="font-size: small;">Representing the license reference text – either as the text in the non-standard license or text in a LicenseInfo object.</span></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">For #2 – The scope was discussed as to whether text for licenses not in the standard license list and not in the file itself.~~<span style="mso-spacerun: yes;">  </span>~~The scenario discussed was if text was found in a file referencing a license which is not in the SPDX standard list of licenses, is there a way to represent the text of the license which is not in the file itself.~~<span style="mso-spacerun: yes;">  </span>~~This was described as out of scope which raised some concerns.~~<span style="mso-spacerun: yes;">  </span>~~Kate raised a concern that if this was in scope, there would be issues with the ID.</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">We agreed that it was confusing to have the name of the referenced license text “Non-Standard License”.~~<span style="mso-spacerun: yes;">  </span>~~Various names were discussed and we agreed to change name of Non-Standard License to “License Reference”.</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Kate to follow-up on updating the diagram based on the discussion.~~<span style="mso-spacerun: yes;">  </span>~~Once that is done we can revisit the scope question and the need for Abstract License.</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Kate provided a spreadsheet that compared the names for the SPDX properties used by RDF/XML, Tag/Value and the spreadsheet.</span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;"> </span></p><p class="MsoNormal" style="margin: 0in 0in 0pt;"><span style="font-family: Times New Roman; font-size: small;">Peter agreed to fill in the RDF/XML column and update the git repository version of the spec with the resultant names.~~</span></p>~~	+	== Attendees ==
		+
		+	* Ann Thorton
		+	* Kristin Newcomer
		+	* Bill Schineller
		+	* Peter Williams
		+	* Kate Stewart
		+	* Gary O'Neall
		+
		+	== Agenda ==
		+
		+	Compare the models provided by Kate (attached) and the models from the email thread
		+
		+	Review/discuss the SPDX Names spreadsheet provided by Kate (attached)
		+
		+	Model discussion:
		+
		+	There were a lot of similarities between the proposed models.
		+
		+	Two differences in the models were discussed:
		+
		+	# Abstract License which subclasses a non-standard license and a standard license vs. a License object with one subclass for standard license.
		+	# Representing the license reference text – either as the text in the non-standard license or text in a LicenseInfo object.
		+
		+	For #2 – The scope was discussed as to whether text for licenses not in the standard license list and not in the file itself. The scenario discussed was if text was found in a file referencing a license which is not in the SPDX standard list of licenses, is there a way to represent the text of the license which is not in the file itself. This was described as out of scope which raised some concerns. Kate raised a concern that if this was in scope, there would be issues with the ID.
		+
		+	We agreed that it was confusing to have the name of the referenced license text “Non-Standard License”. Various names were discussed and we agreed to change name of Non-Standard License to “License Reference”.
		+
		+	Kate to follow-up on updating the diagram based on the discussion. Once that is done we can revisit the scope question and the need for Abstract License.
		+
		+	Kate provided a spreadsheet that compared the names for the SPDX properties used by RDF/XML, Tag/Value and the spreadsheet.
		+
		+	Peter agreed to fill in the RDF/XML column and update the git repository version of the spec with the resultant names.
		+
		+	[[Category:Technical\|Minutes]]
		+	[[Category:Minutes]]