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

Difference between revisions of "Technical Team/Minutes/2012-01-17"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
<p><span style="font-family: Calibri; font-size: medium;">Minutes 1/17/2012</span></p><p><span style="font-family: Calibri; font-size: medium;">Attendees:</span></p><ul><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Gary O’Neall</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Bill Schineller</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Kirsten Newcomer</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Ed Warnicke</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Brandon Robinson</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Peter William</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Rana Rahal</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Jack Manbeck</span></li></ul><p><span style="font-family: Calibri; font-size: medium;">Agenda:</span></p><ul><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Update on tools</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Discuss proposal for hierarchical supply chain (bug 818)</span></li></ul><p><span style="font-family: Calibri; font-size: medium;">&nbsp;</span></p><p><span style="font-family: Calibri; font-size: medium;">Update on tools:</span></p><ul><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Discussed using XSLT to produce HTML form an RDF/XML file including some of the challenges with order not being guarenteed</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Jack offered to help with the HTML and .css on the RDF to HTML tools</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Agreed to add SPDX examples to the git repo (bug 988 assigned to Gary)</span></li></ul><p><span style="font-family: Calibri; font-size: medium;">Hierarchical supply chain:</span></p><ul><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Agreed that UML would be a good way to describe and discuss the proposal</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Ed drafted a class diagram</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Discussion on the need to discuss more concrete classes vs. modeling higher levels of abstraction – agreed that we need to do both simultaneously</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Discussion on relationship between SPDX element and current model, will pick up the discussion with more concrete examples</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Example of a file – proposal would be a URI and Checksum reference to a file (under specifier)</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Referential nodes - are referenced nodes things that must be referenced or can be referenced?&nbsp; Proposal that it would be “best if referenced”</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri;"><span style="font-size: medium;">Do referential nodes introduce an unnecessary complexity?&nbsp; </span></span><ul><li><span style="font-size: medium;">o</span>&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">This may be required for signing the references.</span></li><li><span style="font-size: medium;">o</span>&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Alternative proposal to signing – archive structure where the files are copied</span></li><li><span style="font-size: medium;">o</span>&nbsp;&nbsp; <span style="font-family: Calibri;"><span style="font-size: medium;">Do references need to be resolved for the SPDX specification to work?&nbsp; Problem with requiring references to be resolved is the SPDX doc could not be read without access to those references.&nbsp; </span></span></li><li><span style="font-size: medium;">o</span>&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Having a reference model would make it easier for certain use cases and scenarios (e.g. packager of a WAR file containing many copyrighted elements).</span></li></ul></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">Ed will send out the class diagram once complete</span></li><li><span style="font-size: medium;">·</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-family: Calibri; font-size: medium;">We will pick up the discussion next week</span></li></ul>
+
== Attendees ==
 +
 
 +
* Gary O’Neall
 +
* Bill Schineller
 +
* Kirsten Newcomer
 +
* Ed Warnicke
 +
* Brandon Robinson
 +
* Peter William
 +
* Rana Rahal
 +
* Jack Manbeck
 +
 
 +
== Agenda: ==
 +
 
 +
* Update on tools
 +
* Discuss proposal for hierarchical supply chain (bug 818)
 +
 
 +
== Update on tools ==
 +
 
 +
* Discussed using XSLT to produce HTML form an RDF/XML file including some of the challenges with order not being guarenteed
 +
* Jack offered to help with the HTML and .css on the RDF to HTML tools
 +
* Agreed to add SPDX examples to the git repo (bug 988 assigned to Gary)
 +
 
 +
== Hierarchical supply chain ==
 +
 
 +
* Agreed that UML would be a good way to describe and discuss the proposal
 +
* Ed drafted a class diagram
 +
* Discussion on the need to discuss more concrete classes vs. modeling higher levels of abstraction – agreed that we need to do both simultaneously
 +
* Discussion on relationship between SPDX element and current model, will pick up the discussion with more concrete examples
 +
* Example of a file – proposal would be a URI and Checksum reference to a file (under specifier)
 +
* Referential nodes - are referenced nodes things that must be referenced or can be referenced? Proposal that it would be “best if referenced”
 +
* Do referential nodes introduce an unnecessary complexity?
 +
** This may be required for signing the references.
 +
** Alternative proposal to signing – archive structure where the files are copied
 +
** Do references need to be resolved for the SPDX specification to work? Problem with requiring references to be resolved is the SPDX doc could not be read without access to those references.
 +
** Having a reference model would make it easier for certain use cases and scenarios (e.g. packager of a WAR file containing many copyrighted elements).
 +
* Ed will send out the class diagram once complete
 +
* We will pick up the discussion next week
 +
 
 +
[[Category:Technical|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 13:22, 6 March 2013

Attendees

  • Gary O’Neall
  • Bill Schineller
  • Kirsten Newcomer
  • Ed Warnicke
  • Brandon Robinson
  • Peter William
  • Rana Rahal
  • Jack Manbeck

Agenda:

  • Update on tools
  • Discuss proposal for hierarchical supply chain (bug 818)

Update on tools

  • Discussed using XSLT to produce HTML form an RDF/XML file including some of the challenges with order not being guarenteed
  • Jack offered to help with the HTML and .css on the RDF to HTML tools
  • Agreed to add SPDX examples to the git repo (bug 988 assigned to Gary)

Hierarchical supply chain

  • Agreed that UML would be a good way to describe and discuss the proposal
  • Ed drafted a class diagram
  • Discussion on the need to discuss more concrete classes vs. modeling higher levels of abstraction – agreed that we need to do both simultaneously
  • Discussion on relationship between SPDX element and current model, will pick up the discussion with more concrete examples
  • Example of a file – proposal would be a URI and Checksum reference to a file (under specifier)
  • Referential nodes - are referenced nodes things that must be referenced or can be referenced? Proposal that it would be “best if referenced”
  • Do referential nodes introduce an unnecessary complexity?
    • This may be required for signing the references.
    • Alternative proposal to signing – archive structure where the files are copied
    • Do references need to be resolved for the SPDX specification to work? Problem with requiring references to be resolved is the SPDX doc could not be read without access to those references.
    • Having a reference model would make it easier for certain use cases and scenarios (e.g. packager of a WAR file containing many copyrighted elements).
  • Ed will send out the class diagram once complete
  • We will pick up the discussion next week