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

Difference between revisions of "Technical Team/Minutes/2013-04-16"

From SPDX Wiki
Jump to: navigation, search
(→‎Minutes)
(→‎Minutes)
Line 32: Line 32:
  
 
'''Reviewed Gary's model.'''
 
'''Reviewed Gary's model.'''
 +
< insert link>
 
* Decision to merge Document and Element.
 
* Decision to merge Document and Element.
−
* Decision to consider Document, Package, File as sub classes of Elements.
+
* Decision to consider Document, Package, File, Element as sub classes of Elements.
 
* Snippets: byte ranges as sub class of File - File subclass.  Multiple elements, overlap range.
 
* Snippets: byte ranges as sub class of File - File subclass.  Multiple elements, overlap range.
 
** Not require, but permit and support, as sub case of elements.  challenge is it a subcase of file or its own class?
 
** Not require, but permit and support, as sub case of elements.  challenge is it a subcase of file or its own class?
 
** File is 0..#(EOF byte).  
 
** File is 0..#(EOF byte).  
 +
** snippet is '''only''' valid if it has a relationship to a file.  "is part of".
 +
 +
'''SPDX Element'''
 +
* relationship: see Relationship Enumeration (w/Verification code of other element)
 +
* usage : see Element Usage Enumeration
 +
* license: see Licence classe
 +
* verification code
 +
* sub classes:
 +
** Document:
 +
** Package:
 +
** File:
 +
** Element:
 +
 +
'''Reviewer'''
 +
* property of a Document.
  
 
'''Relationship Enumeration'''
 
'''Relationship Enumeration'''
Line 43: Line 59:
 
* "generated from"
 
* "generated from"
 
* "generates"
 
* "generates"
 +
* "is same as" -- snippet discussion
 +
* "modifies"
 +
* "modified by"
 +
* "revision of" -- may want to evolove reviewer,  document, code, auditor, intent of modifier....
 +
 +
?? how represent a revision of an SPDX file?  provenance, adjustments??  derived from.
  
 
'''Elemenent Usage Enumeration'''
 
'''Elemenent Usage Enumeration'''
Line 53: Line 75:
 
* build tools
 
* build tools
 
* documentation (man, README, SPDX, DEP5, etc.)
 
* documentation (man, README, SPDX, DEP5, etc.)
 +
* reference implementation

Revision as of 18:53, 16 April 2013

Agenda for Technical Team meeting at Linux Collab 4/16

Participants

  • Gary O'Neall (Source Auditor)
  • Jack Manbeck (TI)
  • Kate Stewart (Linaro)
  • Dennis Clark (NexB)
  • Kirsten Newcomer (Blackduck)
  • Liang Cao (UNO)
  • Martin Michelmayer (HP)
  • Daniel German (UVic)
  • Norman Glaude (protecode)
  • Beth "Pidge" Flanagan (intel/yocto)
  • Michael Neuling (NexB)
  • Daniel Coley (Juniper)
  • Brandon (Cisco)

Agenda

  • Best Practices/Usage of SPEC document
    • get to outline and see who's interest in participaing in filling it in.
  • SPDX 2.0 planning
    • Review straw man model - Gary
    • Instance diagram review? - Jack/Bill
    • Distribution of packages use case
      • will straw man handle? - cross check with Yocto
      • reasonable abstraction of elements - consistent
    • Other key use cases want to cross check?

Minutes

Reviewed Gary's model. < insert link>

  • Decision to merge Document and Element.
  • Decision to consider Document, Package, File, Element as sub classes of Elements.
  • Snippets: byte ranges as sub class of File - File subclass. Multiple elements, overlap range.
    • Not require, but permit and support, as sub case of elements. challenge is it a subcase of file or its own class?
    • File is 0..#(EOF byte).
    • snippet is only valid if it has a relationship to a file. "is part of".

SPDX Element

  • relationship: see Relationship Enumeration (w/Verification code of other element)
  • usage : see Element Usage Enumeration
  • license: see Licence classe
  • verification code
  • sub classes:
    • Document:
    • Package:
    • File:
    • Element:

Reviewer

  • property of a Document.

Relationship Enumeration

  • "is part of"
  • "contains"
  • "generated from"
  • "generates"
  • "is same as" -- snippet discussion
  • "modifies"
  • "modified by"
  • "revision of" -- may want to evolove reviewer, document, code, auditor, intent of modifier....

?? how represent a revision of an SPDX file? provenance, adjustments?? derived from.

Elemenent Usage Enumeration

  • source
  • executable
  • dynamic library
  • static library
  • data files (image, audio, visuals, etc.)
  • test (data, frameworks)
  • build tools
  • documentation (man, README, SPDX, DEP5, etc.)
  • reference implementation
Retrieved from "https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2013-04-16&oldid=2425"