THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "Legal Team/Minutes/2011-01-14"

From SPDX Wiki
Jump to: navigation, search
Line 1: Line 1:
<p>&nbsp;</p><p><strong>Legal Worksteam Meeting Minutes - 20110114</strong></p><p>&nbsp;</p><p><strong>SPDX Legal Worksteam Meeting Minutes – 14-January-2011</strong></p><p>&nbsp;</p><p><strong>Attendees:</strong></p><p>Esteban Rockett (Motorola)
Kate Stewart (Canonical)</p><p>Kim Weins (OpenLogic)</p><p>Peter Williams (OpenLogic)</p><p>Scott Peterson (HP)</p><p>Jilayne Lovejoy (OpenLogic)</p><p>Tom Incorvia (Microfocus)</p><p>Michael Herzog (NexB)</p><p>Phil Odence (BlackDuck)</p><p>&nbsp;</p><p><strong>Minutes:</strong></p><p>&nbsp;</p><p>- This meeting was a continuation of "Item E" from the regular Legal Workstream Meeting of 12-Jan-2011.</p><p>- Subject to refining terminology (where attendees will email terminology/minor revisions or do so on Bugzilla), attendees agreed to the following:</p><p>&nbsp;</p><p>***</p><p>(minor edits consistent with meeting done below by Rockett)</p><p>&nbsp;</p><p>Proposal: &nbsp;section 5.3 (License(s)) of the spec will</p><p>become 3 fields:</p><p>&nbsp;</p><p>5.3a Asserted/Concluded License</p><p>&nbsp;</p><p>5.3a.1 Purpose: This field contains the license</p><p>governing the file if it can be determined. &nbsp;If no license</p><p>information can be determined, the license is denoted as</p><p>"Unknown". &nbsp; The licenses should use the standard short</p><p>form names. &nbsp; See Appendix I for standardized license short</p><p>forms. &nbsp;If a Asserted/Concluded License is not one of the</p><p>standardized license short forms, this field must contain a</p><p>reference to the full licenses text included in this SPDX</p><p>file in section 4. &nbsp;If more than one license is asserted/concluded in</p><p>the file, then each should be listed. &nbsp;If any of the</p><p>asserted/concluded licenses offer the recipient a choice of licenses,</p><p>then each of the choices will be declared as a "disjunctive"</p><p>license.</p><p>&nbsp;</p><p>5.3a.2 Intent: Here, the intent is to have a uniform</p><p>method to refer to the license that is determined to</p><p>represent the file with specificity to eliminate any license</p><p>confusion. &nbsp;For example, the 3 clause BSD would have a</p><p>different license identifier then the 4 clause BSD.</p><p>&nbsp;</p><p>5.3a.3 Cardinality: &nbsp;Mandatory, one.</p><p>&nbsp;</p><p>5.3a.4 Tag: "LicenseAsserted:"</p><p>&nbsp;</p><p>5.3a.5 RDF: TBD &nbsp;(include Disjunctive form here)</p><p>&nbsp;</p><p>5.3a.6 Data Format: &lt;short form identifier in</p><p>Appendix I&gt; | "FullLicense"-N</p><p>&nbsp;</p><p>5.3a.7 Example:</p><p>LicenseAsserted: GPL-2.0</p><p>&nbsp;</p><p>&nbsp;</p><p>5.3b Detected License(s)</p><p>&nbsp;</p><p>5.3b.1 Purpose: This field contains the license recited&nbsp;</p><p>in the file, if any. &nbsp;It will be explicit</p><p>from the file header or other information found in the</p><p>file's source code. &nbsp; &nbsp;If no license information is found</p><p>it should be denoted as "NotSpecified". &nbsp;If no license</p><p>information can be determined, the license is denoted as</p><p>"Unknown". &nbsp; The licenses should use the standard short</p><p>form names. &nbsp; See Appendix I for standardized license short</p><p>forms. &nbsp;If a Detected License is not one of the</p><p>standardized license short forms, this field must contain a</p><p>reference to the full licenses text included in this SPDX</p><p>file in section 4. &nbsp;If more than one license is detected in</p><p>the file, then each should be listed. &nbsp;If any of the</p><p>detected licenses offer the recipient a choice of licenses,</p><p>then each of the choices will be declared as a "disjunctive"</p><p>license.</p><p>&nbsp;</p><p>5.ba.2 Intent: Here, the intent is to have a uniform</p><p>method to refer to each license with specificity to</p><p>eliminate any license confusion. &nbsp;For example, the 3 clause</p><p>BSD would have a different license identifier then the 4</p><p>clause BSD.</p><p>&nbsp;</p><p>5.3b.3 Cardinality: &nbsp;Mandatory, one or many.</p><p>&nbsp;</p><p>5.3b.4 Tag: "LicenseDetected:"</p><p>&nbsp;</p><p>5.3b.5 RDF: TBD (not including disjunctive form, if</p><p>multiple many should be specified )</p><p>&nbsp;</p><p>5.3b.6 Data Format: &lt;short form identifier in</p><p>Appendix I&gt; | "FullLicense"-N</p><p>&nbsp;</p><p>5.3b.7 Example:</p><p>LicenseDetected: GPL-2.0</p><p>LicenseDetected: FullLicense-2</p><p>&nbsp;</p><p>&nbsp;</p><p>5.3c License Comments</p><p>&nbsp;</p><p>5.3c.1 Purpose: This field is a detailed description</p><p>of the analysis and any relevent background references that</p><p>went in to making the asserted license for a file, if the</p><p>asserted/concluded license does not match the detected license that</p><p>the person creating the SPDX file wants to share with the</p><p>reviewers.</p><p>&nbsp;</p><p>5.3c.2 Intent: &nbsp;Here, the intent is to provide</p><p>technical readers/reviewers with a detailed technical</p><p>explanation of how the asserted license was determined if it</p><p>does not match the detected license.</p><p>&nbsp;</p><p>5.3c.3 Cardinality: Optional, single instance</p><p>&nbsp;</p><p>5.3c.4 Tag: "LicenseComments:"</p><p>&nbsp;</p><p>5.3c.5 RDF: TBD</p><p>&nbsp;</p><p>5.3c.6 Data Format: free form text than can span</p><p>multiple lines, preceded with &lt;text&gt; and ending with</p><p>&lt;/text&gt;.</p><p>&nbsp;</p><p>5.3c.7 Example: LicenseComments: &lt;text&gt; The</p><p>asserted license was taken from the package level that the</p><p>file was included in. &nbsp;&lt;/text&gt;</p><p>***</p><p>&nbsp;</p>
+
<p>&nbsp;</p><p><strong>Legal Worksteam Meeting Minutes - 20110114</strong></p><p>&nbsp;</p><p><strong>SPDX Legal Worksteam Meeting Minutes – 14-January-2011</strong></p><p>&nbsp;</p><p><strong>Attendees:</strong></p><p>Esteban Rockett (Motorola)</p><p>
Kate Stewart (Canonical)</p><p>Kim Weins (OpenLogic)</p><p>Peter Williams (OpenLogic)</p><p>Scott Peterson (HP)</p><p>Jilayne Lovejoy (OpenLogic)</p><p>Tom Incorvia (Microfocus)</p><p>Michael Herzog (NexB)</p><p>Phil Odence (BlackDuck)</p><p>&nbsp;</p><p><strong>Minutes:</strong></p><p>&nbsp;</p><p>- This meeting was a continuation of "Item E" from the regular Legal Workstream Meeting of 12-Jan-2011.</p><p>- Subject to refining terminology (where attendees will email terminology/minor revisions or do so on Bugzilla), attendees agreed to the following:</p><p>&nbsp;</p><p>***</p><p>(minor edits consistent with meeting done below by Rockett)</p><p>&nbsp;</p><p>Proposal: &nbsp;section 5.3 (License(s)) of the spec will</p><p>become 3 fields:</p><p>&nbsp;</p><p>5.3a Asserted/Concluded License</p><p>&nbsp;</p><p>5.3a.1 Purpose: This field contains the license</p><p>governing the file if it can be determined. &nbsp;If no license</p><p>information can be determined, the license is denoted as</p><p>"Unknown". &nbsp; The licenses should use the standard short</p><p>form names. &nbsp; See Appendix I for standardized license short</p><p>forms. &nbsp;If a Asserted/Concluded License is not one of the</p><p>standardized license short forms, this field must contain a</p><p>reference to the full licenses text included in this SPDX</p><p>file in section 4. &nbsp;If more than one license is asserted/concluded in</p><p>the file, then each should be listed. &nbsp;If any of the</p><p>asserted/concluded licenses offer the recipient a choice of licenses,</p><p>then each of the choices will be declared as a "disjunctive"</p><p>license.</p><p>&nbsp;</p><p>5.3a.2 Intent: Here, the intent is to have a uniform</p><p>method to refer to the license that is determined to</p><p>represent the file with specificity to eliminate any license</p><p>confusion. &nbsp;For example, the 3 clause BSD would have a</p><p>different license identifier then the 4 clause BSD.</p><p>&nbsp;</p><p>5.3a.3 Cardinality: &nbsp;Mandatory, one.</p><p>&nbsp;</p><p>5.3a.4 Tag: "LicenseAsserted:"</p><p>&nbsp;</p><p>5.3a.5 RDF: TBD &nbsp;(include Disjunctive form here)</p><p>&nbsp;</p><p>5.3a.6 Data Format: &lt;short form identifier in</p><p>Appendix I&gt; | "FullLicense"-N</p><p>&nbsp;</p><p>5.3a.7 Example:</p><p>LicenseAsserted: GPL-2.0</p><p>&nbsp;</p><p>&nbsp;</p><p>5.3b Detected License(s)</p><p>&nbsp;</p><p>5.3b.1 Purpose: This field contains the license recited&nbsp;</p><p>in the file, if any. &nbsp;It will be explicit</p><p>from the file header or other information found in the</p><p>file's source code. &nbsp; &nbsp;If no license information is found</p><p>it should be denoted as "NotSpecified". &nbsp;If no license</p><p>information can be determined, the license is denoted as</p><p>"Unknown". &nbsp; The licenses should use the standard short</p><p>form names. &nbsp; See Appendix I for standardized license short</p><p>forms. &nbsp;If a Detected License is not one of the</p><p>standardized license short forms, this field must contain a</p><p>reference to the full licenses text included in this SPDX</p><p>file in section 4. &nbsp;If more than one license is detected in</p><p>the file, then each should be listed. &nbsp;If any of the</p><p>detected licenses offer the recipient a choice of licenses,</p><p>then each of the choices will be declared as a "disjunctive"</p><p>license.</p><p>&nbsp;</p><p>5.ba.2 Intent: Here, the intent is to have a uniform</p><p>method to refer to each license with specificity to</p><p>eliminate any license confusion. &nbsp;For example, the 3 clause</p><p>BSD would have a different license identifier then the 4</p><p>clause BSD.</p><p>&nbsp;</p><p>5.3b.3 Cardinality: &nbsp;Mandatory, one or many.</p><p>&nbsp;</p><p>5.3b.4 Tag: "LicenseDetected:"</p><p>&nbsp;</p><p>5.3b.5 RDF: TBD (not including disjunctive form, if</p><p>multiple many should be specified )</p><p>&nbsp;</p><p>5.3b.6 Data Format: &lt;short form identifier in</p><p>Appendix I&gt; | "FullLicense"-N</p><p>&nbsp;</p><p>5.3b.7 Example:</p><p>LicenseDetected: GPL-2.0</p><p>LicenseDetected: FullLicense-2</p><p>&nbsp;</p><p>&nbsp;</p><p>5.3c License Comments</p><p>&nbsp;</p><p>5.3c.1 Purpose: This field is a detailed description</p><p>of the analysis and any relevent background references that</p><p>went in to making the asserted license for a file, if the</p><p>asserted/concluded license does not match the detected license that</p><p>the person creating the SPDX file wants to share with the</p><p>reviewers.</p><p>&nbsp;</p><p>5.3c.2 Intent: &nbsp;Here, the intent is to provide</p><p>technical readers/reviewers with a detailed technical</p><p>explanation of how the asserted license was determined if it</p><p>does not match the detected license.</p><p>&nbsp;</p><p>5.3c.3 Cardinality: Optional, single instance</p><p>&nbsp;</p><p>5.3c.4 Tag: "LicenseComments:"</p><p>&nbsp;</p><p>5.3c.5 RDF: TBD</p><p>&nbsp;</p><p>5.3c.6 Data Format: free form text than can span</p><p>multiple lines, preceded with &lt;text&gt; and ending with</p><p>&lt;/text&gt;.</p><p>&nbsp;</p><p>5.3c.7 Example: LicenseComments: &lt;text&gt; The</p><p>asserted license was taken from the package level that the</p><p>file was included in. &nbsp;&lt;/text&gt;</p><p>***</p><p>&nbsp;</p>

Revision as of 17:20, 7 February 2011

 

Legal Worksteam Meeting Minutes - 20110114

 

SPDX Legal Worksteam Meeting Minutes – 14-January-2011

 

Attendees:

Esteban Rockett (Motorola)


Kate Stewart (Canonical)

Kim Weins (OpenLogic)

Peter Williams (OpenLogic)

Scott Peterson (HP)

Jilayne Lovejoy (OpenLogic)

Tom Incorvia (Microfocus)

Michael Herzog (NexB)

Phil Odence (BlackDuck)

 

Minutes:

 

- This meeting was a continuation of "Item E" from the regular Legal Workstream Meeting of 12-Jan-2011.

- Subject to refining terminology (where attendees will email terminology/minor revisions or do so on Bugzilla), attendees agreed to the following:

 

***

(minor edits consistent with meeting done below by Rockett)

 

Proposal:  section 5.3 (License(s)) of the spec will

become 3 fields:

 

5.3a Asserted/Concluded License

 

5.3a.1 Purpose: This field contains the license

governing the file if it can be determined.  If no license

information can be determined, the license is denoted as

"Unknown".   The licenses should use the standard short

form names.   See Appendix I for standardized license short

forms.  If a Asserted/Concluded License is not one of the

standardized license short forms, this field must contain a

reference to the full licenses text included in this SPDX

file in section 4.  If more than one license is asserted/concluded in

the file, then each should be listed.  If any of the

asserted/concluded licenses offer the recipient a choice of licenses,

then each of the choices will be declared as a "disjunctive"

license.

 

5.3a.2 Intent: Here, the intent is to have a uniform

method to refer to the license that is determined to

represent the file with specificity to eliminate any license

confusion.  For example, the 3 clause BSD would have a

different license identifier then the 4 clause BSD.

 

5.3a.3 Cardinality:  Mandatory, one.

 

5.3a.4 Tag: "LicenseAsserted:"

 

5.3a.5 RDF: TBD  (include Disjunctive form here)

 

5.3a.6 Data Format: <short form identifier in

Appendix I> | "FullLicense"-N

 

5.3a.7 Example:

LicenseAsserted: GPL-2.0

 

 

5.3b Detected License(s)

 

5.3b.1 Purpose: This field contains the license recited 

in the file, if any.  It will be explicit

from the file header or other information found in the

file's source code.    If no license information is found

it should be denoted as "NotSpecified".  If no license

information can be determined, the license is denoted as

"Unknown".   The licenses should use the standard short

form names.   See Appendix I for standardized license short

forms.  If a Detected License is not one of the

standardized license short forms, this field must contain a

reference to the full licenses text included in this SPDX

file in section 4.  If more than one license is detected in

the file, then each should be listed.  If any of the

detected licenses offer the recipient a choice of licenses,

then each of the choices will be declared as a "disjunctive"

license.

 

5.ba.2 Intent: Here, the intent is to have a uniform

method to refer to each license with specificity to

eliminate any license confusion.  For example, the 3 clause

BSD would have a different license identifier then the 4

clause BSD.

 

5.3b.3 Cardinality:  Mandatory, one or many.

 

5.3b.4 Tag: "LicenseDetected:"

 

5.3b.5 RDF: TBD (not including disjunctive form, if

multiple many should be specified )

 

5.3b.6 Data Format: <short form identifier in

Appendix I> | "FullLicense"-N

 

5.3b.7 Example:

LicenseDetected: GPL-2.0

LicenseDetected: FullLicense-2

 

 

5.3c License Comments

 

5.3c.1 Purpose: This field is a detailed description

of the analysis and any relevent background references that

went in to making the asserted license for a file, if the

asserted/concluded license does not match the detected license that

the person creating the SPDX file wants to share with the

reviewers.

 

5.3c.2 Intent:  Here, the intent is to provide

technical readers/reviewers with a detailed technical

explanation of how the asserted license was determined if it

does not match the detected license.

 

5.3c.3 Cardinality: Optional, single instance

 

5.3c.4 Tag: "LicenseComments:"

 

5.3c.5 RDF: TBD

 

5.3c.6 Data Format: free form text than can span

multiple lines, preceded with <text> and ending with

</text>.

 

5.3c.7 Example: LicenseComments: <text> The

asserted license was taken from the package level that the

file was included in.  </text>

***