THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Technical Team/Minutes/2015-06-01"
From SPDX Wiki
< Technical Team | Minutes
(Created page with "June 6, 2015 == Attendees == * Gary O'Neall * Jack Manbeck * Scott Sterling * Bill Schineller * Kate Stewart * Mark Gisi * Hassib Khanafer * Michael Herzog ==Announcements== *...") |
m (Update date) |
||
Line 1: | Line 1: | ||
− | June | + | June 2, 2015 |
== Attendees == | == Attendees == | ||
* Gary O'Neall | * Gary O'Neall |
Latest revision as of 16:55, 5 June 2015
June 2, 2015
Attendees
- Gary O'Neall
- Jack Manbeck
- Scott Sterling
- Bill Schineller
- Kate Stewart
- Mark Gisi
- Hassib Khanafer
- Michael Herzog
Announcements
- Joint call with legal team next week - Note this will be a different number
- Wiki page of upcoming topics - Kate will setup
Other topics
- Question on whether the ands and ors are case sensitive
Snippets
- Reviewed proposal on snippets (email: http://lists.spdx.org/pipermail/spdx-tech/2015-June/02696.html bug#1000)
- 2 proposals, separate tag "snippet" or have an optional byte range in the file to represent a snippet
- Snippet class is clearer
- optional byte range is easier to implement
- Is there any duplication in fields? Likely not since all the fields in the snippet should refer to the snippet code and not the file.
- Consensus forming on a separate Snippet class/section - Kate will write up a proposal for changes to the spec.
- Will look
- Is the relationship between snippets and files one to many or many to many?
- Seems like many to many, but the snippet is a byte range in a specific file, so it needs to be 1 file to many snippets
Future topics
- Continue Snippets discussion - June 9
- Joint meeting with Legal - June 16
- Discuss proposal for package naming (e.g. Maven GAV), discuss best practices - June 25