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

Technical Team/Minutes/2013-10-22

From SPDX Wiki
< Technical Team‎ | Minutes
Revision as of 16:45, 23 October 2013 by Goneall (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Oct. 22, 2013

Attendees

  • Bill Schineller
  • Gary O’Neall
  • Mark Gisi
  • Michael Herzog
  • Kirsten Newcomer
  • Scott Sterling
  • Jack Manbeck
  • Russ Herrold
  • Kate Stewart

Agenda

  • RDF terms organization on the web page
  • Best practices approach update from business team
  • SPDX 2.0

RDF Terms Organization

  • Overview of Jack’s proposal for archiving old version of RDF terms
    • Under specifications/old versions can be referenced
    • Current version is always at spdx.org/rdf/terms
  • Agreed to Jacks proposal
  • Note: We do not have the turtle and xml versions of the terms for 1.0 to archive. If anyone has a copy, please send to Jack otherwise we will just go with the HTML version for 1.0.
  • Discussion on using git for the spec repository or should we use wiki.
  • Agree to have the wiki point to the main website

Business Team proposal for best practices/tech reports

  • Business group discussing how to foster more best practices and best practice documentation
  • Tech reports would publish something and it would later be promoted to a best practice to the main website
  • Email mark.gisi@windriver.com if interested in reviewing the web pages for the tech reports

SPDX 2.0

  • Creating an overview of 2.0 page on the wiki
  • Contains a milestone list
    • Add acceptance test milestone
    • Add migration plan (1.2 to 2.0) – mapping between features/interoperability between 1.2 and 2.0
    • Add initial terms definition
  • Requirement document
    • Currently missing
    • Missing a document describing use cases we actually plan to support in 2.0
    • Desire a succinct statement of what 2.0 will do
    • Proposal that Key Success Factors could provide such a statement
    • Concern raised that the data model is driving the requirements