https://wiki.spdx.org/api.php?action=feedcontributions&feedformat=atom&user=SlamonsSPDX Wiki - User contributions [en]2026-05-07T11:48:36ZUser contributionsMediaWiki 1.23.13https://wiki.spdx.org/view/Technical_Team/SPDX_Meta_TagsTechnical Team/SPDX Meta Tags2013-11-08T01:13:34Z<p>Slamons: </p>
<hr />
<div><br />
'''SPDX Meta Tagging'''<br />
<br />
This is currently a DRAFT and work in progress.<br />
<br />
__TOC__<br />
<br />
Last Updated: 3 October 2013<br />
<br />
= Introduction =<br />
<br />
The need to identify the license for open source software is critical for both reporting purposes and license compliance. However, determining the license can be difficult due to a lack of information or ambiguous information. Even when licensing information is present, a lack of consistent notation for providing license information can make automating the task of license detection very difficult, thus requiring vast amounts of human effort.<br />
<br />
Meta Tagging is a proposal by the SPDX Work-group to use [http://spdx.org/licenses/ short license identifiers] from the SPDX License List to indicate license info at the file level. The advantages of doing this are numerous but include:<br />
<br />
* It is precise, there is no ambiguity due to variations in license header text.<br />
* It is language neutral.<br />
* It is easy to machine process.<br />
* It is concise<br />
* Leads to code that is easier to read. <br />
* The license travels with the file (as sometimes not entire projects are used or license files are removed).<br />
* It is simple and can be used without much cost in interpreted environments like java Script, etc.,.<br />
* It is a standard and can be universal. There is no need for all the variation.<br />
* The license list for SPDX is immutable and will never change.<br />
* It provides simple guidance for developer's who want to make sure the license for their code is respected.<br />
<br />
<br />
== History == <br />
Although discussed by SPDX for some time, with proposals by Windriver, the U-boot project was the first open source project to adopt (that we know about). This was the commit message by Wolfgang Denk the project maintainer:<br />
<br />
<code><br />
Like many other projects, U-Boot has a tradition of including big<br />
blocks of License headers in all files. This not only blows up the<br />
source code with mostly redundant information, but also makes it very<br />
difficult to generate License Clearing Reports. An additional problem<br />
is that even the same licenses are referred to by a number of<br />
slightly varying text blocks (full, abbreviated, different<br />
indentation, line wrapping and/or white space, with obsolete address<br />
information, ...) which makes automatic processing a nightmare.<br />
<br />
To make this easier, such license headers in the source files will be<br />
replaced with a single line reference to Unique Lincense Identifiers<br />
as defined by the Linux Foundation's SPDX project [1]. For example,<br />
in a source file the full "GPL v2.0 or later" header text will be<br />
replaced by a single line:<br />
<br />
SPDX-License-Identifier: GPL-2.0+<br />
</code><br />
<br />
= Meta Tags =<br />
<br />
The following Meta Tags are available for use.<br />
<br />
== SPDX-License-Identifier ==<br />
<br />
This tag declares the license the file is under and should be placed at or near the top of the file. To the extent that the file contains existing copyright and license information it is our general recommendation that the tag be used to supplement not replace that information especially for files with a long history of changes, multiple copyright holders, or complex licensing. Of course, this is the ultimate decision of the copyright holders of the file. <br />
<br />
Tag: SPDX-License-Identifier: <SPDX Short License Name><br />
<br />
Example: SPDX-License-Identifier: MIT<br />
<br />
For a license set, when there is a choice between licenses ("disjunctive license"), they should be separated with "or" and enclosed in parentheses. Similarly when multiple licenses need to be applied ("conjunctive license"), they should be separated with "and" and enclosed in parentheses.<br />
<br />
Example: SPDX-License-Identifier: (GPL-2.0 or MIT)<br />
<br />
What to do if your license is not on the list?<br />
<br />
<br />
= Examples =<br />
<br />
{| class="wikitable sortable" border="1"<br />
|+ Examples of Meta Tagging<br />
! align="left" width=12% | Entity<br />
! class="unsortable" | Link / Notes<br />
|-<br />
| U-boot<br />
| [http://git.denx.de/?p=u-boot.git;a=blob;f=post/post.c;h=4af5355fa5a20f9c2e763f37b269bea38d43e8ea;hb=6612ab33956ae09c5ba2fde9c1540b519625ba37]Using SPDX-License-Identifier in place of a license header in source.<br />
|-<br />
|}<br />
<br />
= Proposing New Meta Tags =<br />
<br />
To propose a new Meta Tag, send your proposal to the SPDX Technical Workgroup using their [https://lists.spdx.org/mailman/listinfo/spdx-tech/ mailing list].<br />
<br />
[[Category:Technical]]</div>Slamonshttps://wiki.spdx.org/view/User_talk:JlovejoyUser talk:Jlovejoy2013-10-03T18:26:22Z<p>Slamons: Created page with "I'm not convinced this leads to "code that easier to read""</p>
<hr />
<div>I'm not convinced this leads to "code that easier to read"</div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12013-08-30T14:09:39Z<p>Slamons: Added link to the SPDX 1.1 Press Release</p>
<hr />
<div>[http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&w=900&sidebar=yes&bg=no#sched-body-outer LinuxCon SPDX Panel Discussion]<br />
<br />
[http://www.spdx.org/content/press-release-announcing-spdx-10 SPDX 1.0 Press Release]<br />
<br />
[http://www.linuxfoundation.org/news-media/announcements/2012/08/linux-foundation%E2%80%99s-spdx%E2%84%A2-workgroup-releases-new-version-software SPDX 1.1 Press Release]<br />
<br />
Press Release Content<br />
<br />
The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.1 of its Software Package Data Exchange (SPDX™) standard.<br />
<br />
* Expanded license list -- 12new licenses added in the 1.1 release and we now have a process in place to accomodate new license requests.<br />
* OSI announces that is has adopted SPDX short identifiers (quote and pointer)<br />
* Based on feedback from the community the SPDX data license was changed from PddL to CC0. (get a quote from Karen C)<br />
* Summary of changes from 1.0 to 1.1. (Kate)<br />
* Talk about the availability of both commercial and open source tools that support SPDX.<br />
<br />
A key enabler to the adoption of SPDX is tooling to automate the production of SPDX files and we are pleased to see both commercial and open source projects stepping up to this challenge.<br />
<br />
Reach out to commercial vendors for quotes:<br />
<br />
* Antelink<br />
* Blackduck<br />
* OpenLogic<br />
* NexB<br />
* Palamida<br />
* Protecode<br />
<br />
Reach out to Open Source projects for quotes:<br />
<br />
* UNO Fossology project (Matt Germonprez)<br />
* Source Auditor (Gary ONeall)<br />
* University of Victoria (Daniel German)<br />
<br />
[[Category:Business]]<br />
[[Category:Archived]]</div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-03-13Business Team/Minutes/2012-03-132012-09-20T17:48:10Z<p>Slamons: </p>
<hr />
<div><p>Attendees:&nbsp; Jack, Scott, Michael, Jilayne Ibrahim</p><p>&nbsp;</p><p>Topics:</p><p>&nbsp;</p><p>1. Discussed survey on barriers to adoption.&nbsp;&nbsp; Michael volunteered Pierre to work with Jack on this.&nbsp;&nbsp; Scott will track down previous work from the SPDX end-user summit at Cisco.&nbsp;&nbsp; Publish the survey on the SPDX list and maybe other places like the LF Facebook page, FossBazaar, ect...&nbsp;&nbsp;&nbsp; </p><p>2.&nbsp; Ibrahim discussed some of his ideas on what we need to move SPDX forward including outreach to LF members. &nbsp; Need a more formal governance although he's willing to share want we have and gather feedback. If we're successful in recruiting companies then we need an onboarding process -- where do they focus resources they're committing.&nbsp;&nbsp;&nbsp;</p><p>3.&nbsp; Michael questioned if we need a system to track and coordinate our outreach to companies and projects.&nbsp; He's going to investigate some cloud based CRM type systems.</p><p>4. Jack's provided a update on the website.&nbsp;&nbsp; He's been doing a great job reorganizing and getting broken links fixes.&nbsp;&nbsp; Thanks Jack!</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/General_Meeting/Planning_for_Face_to_Face_meeting_in_September-October_2012General Meeting/Planning for Face to Face meeting in September-October 20122012-08-29T17:36:28Z<p>Slamons: </p>
<hr />
<div><p><span style="text-decoration: underline;"><strong>Introduction:</strong></span></p><p>The purpose of this wiki page is to host the planning information for the SPDX f2f we are targeting to hold in the bay area in Sept/Oct 2012. Please see the bottom of this page to indicate which dates works best with you.</p><p>I have a number of agenda items that can easily consume a full day worth of discussion. I divide the agenda items in two categories:&nbsp;Core agenda items are the primary reason to hold this f2f meeting, and secondary agenda items will be discussed given time availability.</p><p><span style="text-decoration: underline;"><strong>Core agenda items:</strong></span></p><p>For all these core items, I will have a proposal to present that will drive the discussion. The goal of this f2f is really to have an agreement on how to proceed with these items. The agreement on these will enable the WG to be on a better and faster path of success and it is critical to get to that point. Otherwise, 1) recruiting other companies into this WG will be a mission impossible challenge (How many new companies have joined SPDX recently?), 2) Maintaing current participants will also be challenge if we don't have a resolution on these items, and not to forget the 3) fading possibility of achieving the goal of making compliance easier to achieve via SPDX standard data exchnage format (across supply chains).&nbsp;</p><ol><li>Project Governance: I will propose a governance model and drive this discussion</li><li>WG Structure: Goes with the above item as part of governance</li><li>Roadmap for 2012-2013-2014: I have a proposal on setting up a roadmap that will initiate this discussion</li><li>Charter: Mission / Goals / Vision: Continue this discussion and get to a closure on it. &nbsp;</li><li>Recruitment: I have a proposal on this that covers companies to approach and how</li><li>SPDX web site &nbsp;</li></ol><div><div><span style="text-decoration: underline;"><strong>Secondary agenda items:</strong></span></div></div><div>&nbsp;</div><div>These items are not the reasons we're calling for this meeting. However, since a lot of folks are expected to attend, then it would make sense to add 1 more day to the meeting to cover these items.</div><ol><li>Review current state of affairs for each sub-team</li><li>Current challenges, what are we doing about it, and how can we do better</li><li>Review of what needs to be done to get to SPDX 2.0 (technical, legal and business)</li><li>2.0 Use Cases</li><li>2.0 Model design</li></ol><div>This is a working session where people driving the effort are expected to drive the discussions.&nbsp;For each of the above items,&nbsp;it would be fantastic if Team Leads/Chairs can prepare a presentation that covers&nbsp;</div><div><ul><li>What was achieved in your team since Jan 2012?</li><li>What are the challenges your team is facing? Any proposal on how to resolve these challenges? How can other teams or the Linux Foundation help you with these?</li><li>What is on your plate for the rest of the year and well into 2013?</li><li>What areas you need help to get you unlocked?</li><li>etc.</li></ul></div><div>Anyone who participated in program reviews in their companies will find this familiar. The goal is to have a better alignment between the various team, understand where the challenges are and identify how we can resolve them, plan for getting 2.0 out of the door, etc.&nbsp;</div><div>&nbsp;</div><div>This F2F is really the opportunity for SPDX to regroup and proceed with a strong momentum.&nbsp;</div><div>&nbsp;</div><p><span style="text-decoration: underline;"><strong>Suggested F2F Dates:</strong></span></p><ul><li>September 10-11:</li><ul><li>Gary O'Neall (traveling Sept 18th-7th)</li><li>Jack Manbeck</li><li>Pierre Lapointe</li><li>Michael Herzog</li><li>Ibrahim Haddad</li><li>Mark Gisi</li></ul><li>September 27-28:</li><ul><li>Kirsten Newcomer</li><li>Bill Schineller</li><li>Adam Cohn</li><li>Jason Buttura</li><li>Jack Manbeck</li><li>Pierre Lapointe</li><li>Michael Herzog</li><li>Kamyar Emami</li><li>Ibrahim Haddad</li><li>Mark Gisi</li></ul><li>October 1-2:</li><ul><li>Kirsten Newcomer</li><li>Bill Schineller</li><li>Adam Cohn</li><li>Jason Buttura</li><li>Jack Manbeck</li><li>Pierre Lapointe</li><li>Michael Herzog</li><li>Kamyar Emami</li><li>Ibrahim Haddad</li><li>Mark Gisi</li><li>Jilayne Lovejoy</li><li>Phil Odence/Boston - possibly</li></ul><li>October 2-3:</li><ul><li>Kirsten Newcomer</li><li>Bill Schineller</li><li>Adam Cohn</li><li>Jason Buttura</li><li>Pierre Lapointe</li><li>Michael Herzog</li><li>Kamyar Emami</li><li>Ibrahim Haddad</li><li>Mark Gisi</li><li>Jilayne Lovejoy</li><li>Phil Odence/Boston</li><li>Scott Lamons</li></ul></ul><p>Above are possible dates for the F2F. I chose these dates based on my availability as I have a significant amount of international travel for the rest of the year. Please sign your name next to the dates you can attend as a method to track who can attend which dates. I can attend all of these.&nbsp;</p><p><span style="text-decoration: underline;"><strong>Suggested Locations:</strong></span></p><p>Any SPDX participant companies in the bay area who can host? Please let us know.</p><ul><li>Jack Manbeck,&nbsp; Washington DC area or possibly Austin Texas or Dallas Texas (I would need to verify availablity for all sites once we have the day in mind.)</li><li>Scott Lamons.&nbsp; HP would be willing to host in Fort Collins, CO.&nbsp; I may also be able to arrange a meeting room in our Austin, TX facility.</li></ul><p>&nbsp;</p><p><span style="text-decoration: underline;"><strong>Notes:</strong></span></p><ol><li>Presenters at the F2F meeting (me included): it would be very helpful to plan to make available your material a week before the meeting to allow enough time for SPDX prticipants to review and be ready for dicussions.</li><li>I will detail the agenda items further as we approach the meeting dates based on how I will structure my presentations (for my part) and on feedback from participants on what they want to discuss.</li></ol></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-08-02Business Team/Minutes/2012-08-022012-08-16T17:38:57Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;"><strong>Attendees</strong></p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Jack Manbeck (host)</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Gary O'Neall</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Pierre Lapointe</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Michael Herzog</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Jilayne Lovejoy</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Steve Cropper</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Ibrahim Haddad</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">Adam Coehn</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;"><strong>Agenda/Notes</strong></p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">1. Press Release for 1.1</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">This is still being formulated so there was no real discussion on this item.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">2. Outreach Activities (Fossology, Open Compliance program, Other?)</p><p>&nbsp;</p><p>Talked with Ibrahim from the Linux Foundation. &nbsp;Ibrahim has been attending all the working group meetings and talking with members and non members about SPDX.<span style="mso-spacerun: yes;">&nbsp; </span>He has a number of recommendations that he would like to maker within the next few weeks (perhaps around the time of LinuxCon). One of his proposals will be on governance for SPDX.</p><p>&nbsp;</p><p>Ibrahim brought up that there will be an Open Compliance Summit by the LF in Tokyo Japan October 24 and 25. It would be good for members from SPDX to attend and possibly even give some talks. We should let him know.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto;">3. Web update.&nbsp;&nbsp;</p><p>&nbsp;</p><p>The site was switched over to the new format. Instead of waking through the pages with the business team, Jack volunteered to take a look at them and make sure everything looks okay.</p><p>&nbsp;</p><p>There was some discussion about the Roster page for the business team. There was general agreement that an active membership roster even at the SPDX level would be extremely useful. Jack brought up the technical team suggestion of having a self subscribing page. General consensus was that was a good way to do it and we would let the technical team take the lead on setting something up and then re-using it. Steve mentioned there may be a drupal widget to do something like this and would check with Martin.</p><p>&nbsp;</p><p>Jilayne mentioned that she thought the License List should be on the website Documentation Dropdown given its significance.</p><p>&nbsp;</p><p>Ibrahim brought up that we should use SPDX email names on the website instead of personal ones (because people move on, etc).</p><p>&nbsp;</p><p>There was discussion about the website Ibrahim posted in his comments email giving feedback on the new SPDX website. The team felt that having a more professional site like that would be a good thing and that it was difficult to achieve with just volunteers who are also not web developers. Ibrahim mention that they had contracted that work out and would get a quote to do something similar for SPDX. Steve will work with him on that. How to fund it is still TBD but the team felt getting a quote or general idea would still be a useful first step.</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-08-16Business Team/Minutes/2012-08-162012-08-16T16:19:56Z<p>Slamons: </p>
<hr />
<div><p>Attendees:&nbsp; Scott Lamons(host), Michael Herzog, Jack Manbeck, Gary ONeall, Steve Cropper, Ibrahim Hahdad, Karmir</p><p>&nbsp;</p><p>Topics:</p><p>Governance discussion -- can we continue to make progress with the volunteer based model or is a more active coorporate membership (fee based) model required in order to make progress on development, outreach, and adoption of the standard???</p><p>Adoption -- do we need to focus on a particular audience (e.g. corporate users or developers) or can we target both at the same time.&nbsp;&nbsp; </p><p>Do we really understand all the barriers to adoption?</p><p>Some of this was captured at the SPDX Summit hosted by Cisco after the Collaboration Summit.&nbsp;&nbsp;</p><p>Talked about doing a survery targetting open source projects, corporate users, and end-users&nbsp; to undercover the barriers to adoption.&nbsp; (Jack volunteered to work on this)</p><p>Add a feedback link to the website (e.g. feedback@spdx.org)</p><p>Use the Tuesday Linuxcon meeting to gather input from potential adopters</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12012-08-14T17:32:48Z<p>Slamons: </p>
<hr />
<div><p><a href="http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&amp;w=900&amp;sidebar=yes&amp;bg=no#sched-body-outer">LinuxCon SPDX Panel Discussion</a></p><p><a href="http://www.spdx.org/content/press-release-announcing-spdx-10">SPDX 1.0 Press Release</a></p><p>Press Release Content</p><p>The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.1 of its Software Package Data Exchange (SPDX™) standard.</p><p>-Expanded license list -- 12new licenses added in the 1.1 release and we now have a process in place to accomodate new license requests.</p><p>-OSI announces that is has adopted SPDX short identifiers (quote and pointer)</p><p>-Based on feedback from the community the SPDX data license was changed from PddL to CC0.&nbsp;&nbsp; (get a quote from Karen C)</p><p>-Summary of changes from 1.0 to 1.1. (Kate)</p><p>-Talk about the availability of both commercial and open source tools that support SPDX.</p><p>A key enabler to the adoption of SPDX is tooling to automate the production of SPDX files and we are pleased to see both commercial and open source projects stepping up to this challenge. &nbsp;</p><p>Reach out to commercial vendors for quotes:&nbsp;</p><p>Antelink</p><p>Blackduck</p><p>OpenLogic</p><p>NexB</p><p>Palamida</p><p>Protecode</p><p>&nbsp;</p><p>Reach out to Open Source projects for quotes:</p><p>UNO Fossology project (Matt Germonprez)</p><p>Source Auditor (Gary ONeall)</p><p>University of Victoria (Daniel German)</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12012-08-14T17:12:52Z<p>Slamons: </p>
<hr />
<div><p><a href="http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&amp;w=900&amp;sidebar=yes&amp;bg=no#sched-body-outer">LinuxCon SPDX Panel Discussion</a></p><p><a href="http://www.spdx.org/content/press-release-announcing-spdx-10">SPDX 1.0 Press Release</a></p><p>Press Release Content</p><p>The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.1 of its Software Package Data Exchange (SPDX™) standard.</p><p>-Expanded license list -- 12new licenses added in the 1.1 release and we now have a process in place to accomodate new license requests.</p><p>-OSI announces that is has adopted SPDX short identifiers (quote and pointer)</p><p>-Based on feedback from the community the SPDX data license was changed from PddL to CC0.&nbsp;&nbsp; (get a quote from Karen C)</p><p>-Summary of changes from 1.0 to 1.1. (Kate)</p><p>-Talk about the availability of both commercial and open source tools that support SPDX.</p><p>A key enabler to the adoption of SPDX is tooling to automate the production of SPDX files and we are pleased to see both commercial and open source projects stepping up to this challenge. &nbsp;</p><p>Reach out to commercial vendors for quotes:&nbsp;</p><p>Antelink</p><p>Blackduck</p><p>OpenLogic</p><p>Palamida</p><p>Protecode</p><p>&nbsp;</p><p>Reach out to Open Source projects for quotes:</p><p>UNO Fossology project (Matt Germonprez)</p><p>Source Auditor (Gary ONeall)</p><p>University of Victoria (Daniel German)</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12012-08-14T16:28:30Z<p>Slamons: </p>
<hr />
<div><p><a href="http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&amp;w=900&amp;sidebar=yes&amp;bg=no#sched-body-outer">LinuxCon SPDX Panel Discussion</a></p><p><a href="http://www.spdx.org/content/press-release-announcing-spdx-10">SPDX 1.0 Press Release</a></p><p>Press Release Content</p><p>The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.1 of its Software Package Data Exchange (SPDX™) standard.</p><p>-Expanded license list -- 12new licenses added in the 1.1 release and we now have a process in place to accomodate new license requests.</p><p>-OSI announces that is has adopted SPDX short identifiers (quote and pointer)</p><p>-Based on feedback from the community the SPDX data license was changed from PddL to CC0.&nbsp;&nbsp; (get a quote from Karen C)</p><p>-Summary of changes from 1.0 to 1.1. (Kate)</p><p>-Talk about the availability of commercial tools that support SPDX</p><p>-Open source tools&nbsp; (UNO Fossology project and Gary's tools)</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12012-08-09T15:13:00Z<p>Slamons: </p>
<hr />
<div><p><a href="http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&amp;w=900&amp;sidebar=yes&amp;bg=no#sched-body-outer">LinuxCon SPDX Panel Discussion</a></p><p>Press Release Content</p><p>The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.1 of its Software Package Data Exchange (SPDX™) standard.</p><p>-Expanded license list -- 12new licenses added in the 1.1 release and we now have a process in place to accomodate new license requests.</p><p>-OSI announces that is has adopted SPDX short identifiers (quote and pointer)</p><p>-Based on feedback from the community the SPDX data license was changed from PddL to CC0.&nbsp;&nbsp; (get a quote from Karen C)</p><p>-Summary of changes from 1.0 to 1.1. (Kate)</p><p>-Talk about the availability of commercial tools that support SPDX</p><p>-Open source tools&nbsp; (UNO Fossology project and Gary's tools)</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12012-08-09T14:58:43Z<p>Slamons: </p>
<hr />
<div><p><a href="http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&amp;w=900&amp;sidebar=yes&amp;bg=no#sched-body-outer">LinuxCon SPDX Panel Discussion</a></p><p>Press Release Content</p><p>The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.1 of its Software Package Data Exchange (SPDX™) standard.</p><p>-Expanded license list -- 12new licenses added in the 1.1 release and we now have a process in place to accomodate new license requests.</p><p>-OSI announces that is has adopted SPDX short identifiers (quote and pointer)</p><p>-Based on feedback from the community the SPDX data license was changed from PddL to CC0.&nbsp;&nbsp; (get a quote from Karen C)</p><p>-Spec updates (Kate)</p><p>-Talk about the availability of commercial tools that support SPDX</p><p>-Open source tools&nbsp; (UNO Fossology project and Gary's tools)</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.1Business Team/Launch/1.12012-07-30T15:41:29Z<p>Slamons: </p>
<hr />
<div><p><a href="http://lcna2012.sched.org/event/d6abd8bb5f87585c538181d3dce0825f?iframe=yes&amp;w=900&amp;sidebar=yes&amp;bg=no#sched-body-outer">LinuxCon SPDX Panel Discussion</a></p><p>Press Release Content</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Launch/1.0/SPDX_1.0_Press_ReleaseBusiness Team/Launch/1.0/SPDX 1.0 Press Release2012-07-30T15:29:10Z<p>Slamons: </p>
<hr />
<div><p><strong>SPDX Workgroup Releases Software Package Data Exchange Standard to Widespread Industry Support</strong></p><p>By Linux_Foundation - August 16, 2011 - 10:07pm</p><p>Standard format for communicating open source license and copyright information throughout supply chain ensures better, easier compliance</p><p>LINUXCON, Vancouver, B.C., August 17, 2011 – The SPDX workgroup, hosted by The Linux Foundation, today announced the release of version 1.0 of its Software Package Data Exchange (SPDX™) standard.</p><p>The SPDX standard helps facilitate compliance with free and open source software licenses by standardizing the way license information is shared across the software supply chain. SPDX reduces redundant work by providing a common format for companies and communities to share important data about software licenses and copyrights, thereby streamlining and improving compliance.</p><p>SPDX was developed with participation by a wide range of industry and open source community heavyweights, including: Alcatel-Lucent, Antelink, Black Duck Software, Canonical, HP, Micro Focus, Motorola Mobility, nexB Inc, OpenLogic, Palamida, Protecode, Source Auditor, Texas Instruments and Wind River. Participants in the SPDX beta program included Antelink, HP, Motorola Mobility, Texas Instruments and Wind River.</p><p>Click here to see <a href="http://www.linuxfoundation.org/news-media/announcements/2011/08/widespread-industry-support-spdx-10">comments in support of the SDPX 1.0 release</a>.</p><p>“The SPDX 1.0 standard is an example of how open compliance and collaboration can enable the advancement of Linux and open source software,” said Jim Zemlin, executive director of The Linux Foundation. “We applaud the SPDX workgroup for its important work on providing a consistent way to report and view license information for software technology components, making it even easier for companies to maximize their investments in free and open source software.”</p><p>Most technology products today are assembled from multiple components that contain free and open source software, as well as commercial software; these components are created, delivered, and received by companies throughout the supply chain. Because of the distributed nature and complexity of the global software supply chain, it has become cumbersome and time consuming for each organization to prepare the license information for these components in the multiple distinct formats prescribed by others in their supply chain.</p><p>By enabling communities and companies to provide license information in a common format that can be easily analyzed and shared, the SPDX standard helps to accelerate the adoption of Linux and other free and open source software across industries, including the consumer electronics marketplace, by easing the burden of compliance through transparent sharing of license information.</p><p>“Today we’re seeing collaboration among industry experts come to fruition in SPDX 1.0,” said Esteban Rockett, co-founder of SPDX and lead software counsel at Motorola Mobility (an SPDX beta participant). “Representatives from the community, vendors and companies that use open source have come together to deliver a standard, accompanied with tools, that will make it easier to determine and comply with license obligations in a software bill of materials. This reduces compliance anxiety and costs, and further accelerates the adoption of Linux and other free and open source software.”</p><p>“The announcement of the initial release of the SPDX standard is a welcome event, because SPDX is a crucial building block in an industry-wide system of automated license compliance administration,” said Eben Moglen, executive director of the Software Freedom Law Center. “The efforts of the SPDX workgroup will ultimately help to realize large cost savings for all parties making commercial use of embedded FOSS, as well as substantially increased assurance of license compliance for FOSS licensors.”</p><p>The SPDX standard defines a standard file format that lists detailed license and copyright information for a software package and each file it comprises. The SPDX community has also provided open source tools to convert SPDX files to and from spreadsheet formats.</p><p>Visit the SPDX website for more details on what is in the SPDX standard or to participate in the SPDX community: <a href="http://www.spdx.org">www.spdx.org</a>.</p><p>A video overview of SPDX is available at <a href="http://www.linuxfoundation.org/programs/legal/compliance/webinars/introduction-to-spdx">http://www.linuxfoundation.org/programs/legal/compliance/webinars/introduction-to-spdx</a>.</p><p>About SPDX<br /> The Software Package Data Exchange® (SPDX™) specification is a standard format for communicating the components, licenses and copyrights associated with a software package. This SPDX Community is a workgroup sponsored by The Linux Foundation and associated with FOSSBazaar. The specification has been adopted as one of the key elements of the Linux Foundation’s Open Compliance Program. Further, the SPDX naming conventions are now in use at the industry’s repository of record for open source licenses, maintained by the Open Source Initiative at <a href="http://opensource.org/licenses">http://opensource.org/licenses</a>. The SPDX specification itself is under the Creative Commons Attribution License 3.0. For more information about SPDX, please visit: <a href="http://spdx.org/about/spdx">http://spdx.org/about/spdx</a>.</p><p>About The Linux Foundation<br /> <a href="http://www.linuxfoundation.org">The Linux Foundation </a>is a nonprofit consortium dedicated to fostering the growth of Linux. Founded in 2000, the organization sponsors the work of Linux creator Linus Torvalds and promotes, protects and advances the Linux operating system by marshaling the resources of its members and the open source development community. The Linux Foundation provides a neutral forum for collaboration and education by hosting <a href="http://events.linuxfoundation.org">Linux conferences</a>, including <a href="http://events.linuxfoundation.org/events/linuxcon">LinuxCon</a>, and generating original <a href="http://www.linuxfoundation.org/publications">Linux research</a> and content that advances the understanding of the Linux platform. Its web properties, including <a href="http://www.linux.com">Linux.com</a>, reach approximately two million people per month. The organization also provides extensive <a href="http://training.linuxfoundation.org">Linux training</a> opportunities that feature the Linux kernel community’s leading experts as instructors. <a href="http://www.twitter.com/linuxfoundation">Follow The Linux Foundation on Twitter</a>.</p><p>###</p><p>Trademarks: The Linux Foundation and SPDX are trademarks of The Linux Foundation. Linux is a trademark of Linus Torvalds.</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-07-19Business Team/Minutes/2012-07-192012-07-20T15:17:57Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p class="MsoNormal">Attendees:<span style="mso-spacerun: yes;">&nbsp; </span></p><p>&nbsp;</p><p class="MsoNormal">Scott Lamons (host)</p><p class="MsoNormal">Gary O'Neall</p><p class="MsoNormal">Kamyar Emami</p><p class="MsoNormal">Phil Odence</p><p class="MsoNormal">Pierre Lapointe</p><p class="MsoNormal">Michael Herzog</p><p class="MsoNormal">Jilayne Lovejoy</p><p class="MsoNormal">Steve Cropper (joined later)</p><p>&nbsp;</p><p class="MsoNormal">Agenda/Notes</p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">1. Linuxcon (Panel, Working group meeting, 1.1 PR?)</span></p><p>&nbsp;</p><p><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">SPDX Business panel will be on Thursday at 10:25am -- Scott will moderate, Kate, Jilayne, and Jack will represent the tech, legal, and biz teams.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Scott will be setting up a meeting in the next couple weeks to start planning the content and flow.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp;</span></span></p><p><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Working group meeting on Tuesday from 1-6pm will focus on 2.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>The first hour will be reserved to provide an SPDX introduction and meet any new participants.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will work with LF to get this posted to the website.</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Press release for 1.1?<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Consensus was that it's a good thing to do.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Review previous release for 1.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will check with Amanda McPherson on logistics for putting this out via LF.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Things to include:<span style="mso-spacerun: yes;">&nbsp; </span>updates to the license list, matching guidelines, CCO in response to community input , tools?</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">2. Outreach Activities (Fossology, Open Compliance program, Other?) </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Matt Germonprez at the University of Nebraska Omaha (UNO) and team are in the process of standing up a public instance of Fossology and they are forming a project to add SPDX functionality to Fossology.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Scott and Bob Gobeille (Fossology architect) met with Matt to discuss their plans.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Bob is working with the team to resolve several issues.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Gary O'Neall and Kate Stewart offered their support as well.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p class="MsoNormal">&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">LF considering assigning a program/project manager to SPDX.<span style="mso-spacerun: yes;">&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;&nbsp;</span>FOSS barcode tracker (announced May 30) seems complementary to SPDX</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"><br /></span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Gary talked about target development/build tools such as Eclipse (e.g. an&nbsp;Eclipse plugin that wraps some of the existing tools).<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Gary looking for some commitment from the Eclipse foundation.<span style="mso-spacerun: yes;">&nbsp; </span>Michael to reach out to Phillip at Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp; </span>Apache uses Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">3. Web update.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Plan is to switch to the new website over the weekend of 7/28.&nbsp; Steve to send a message to the SPDX team as a heads up and coordintate with Martin.<span style="mso-spacerun: yes;">&nbsp; </span>If there are any major problems we can switch it back before Monday.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-07-19Business Team/Minutes/2012-07-192012-07-20T15:11:41Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p class="MsoNormal">Attendees:<span style="mso-spacerun: yes;">&nbsp; </span></p><p>&nbsp;</p><p class="MsoNormal">Scott Lamons (host)</p><p class="MsoNormal">Gary O'Neall</p><p class="MsoNormal">Kamyar Emami</p><p class="MsoNormal">Phil Odence</p><p class="MsoNormal">Pierre Lapointe</p><p class="MsoNormal">Michael Herzog</p><p class="MsoNormal">Jilayne Lovejoy</p><p class="MsoNormal">Steve Cropper (joined later)</p><p>&nbsp;</p><p class="MsoNormal">Agenda/Notes</p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">1. Linuxcon (Panel, Working group meeting, 1.1 PR?)</span></p><p>&nbsp;</p><p><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">SPDX Business panel will be on Thursday at 10:25am -- Scott will moderate, Kate, Jilayne, and Jack will represent the tech, legal, and biz teams.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Scott will be setting up a meeting in the next couple weeks to start planning the content and flow.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp;</span></span> </p><p><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Working group meeting on Tuesday from 1-6pm will focus on 2.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>The first hour will be reserved to provide an SPDX introduction and meet any new participants.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will work with LF to get this posted to the website.</span> </p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Press release for 1.1?<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Consensus was that it's a good thing to do.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Review previous release for 1.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will check with Amanda McPherson on logistics for putting this out via LF.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Things to include:<span style="mso-spacerun: yes;">&nbsp; </span>updates to the license list, matching guidelines, CCO in response to community input , tools?</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">2. Outreach Activities (Fossology, Open Compliance program, Other?) </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Matt Germonprez at the University of Nebraska Omaha (UNO) and team are in the process of standing up a public instance of Fossology and they are forming a project to add SPDX functionality to Fossology.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Scott and Bob Goebille (Fossology architect) met with Matt to discuss their plans.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Bob is working with the team to resolve several issues.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Gary O'Neall and Kate Stewart offered their support as well.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p class="MsoNormal">&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">LF considering assigning a program/project manager to SPDX.<span style="mso-spacerun: yes;">&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;&nbsp;</span>FOSS barcode tracker (announced May 30) seems complementary to SPDX</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"><br /></span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Gary talked about target development/build tools such as Eclipse (e.g. an&nbsp;Eclipse plugin that wraps some of the existing tools).<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Gary looking for some commitment from the Eclipse foundation.<span style="mso-spacerun: yes;">&nbsp; </span>Michael to reach out to Phillip at Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp; </span>Apache uses Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">3. Web update.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Plan is to switch to the new website over the weekend of 7/28.&nbsp; Steve to send a message to the SPDX team as a heads up and coordintate with Martin.<span style="mso-spacerun: yes;">&nbsp; </span>If there are any major problems we can switch it back before Monday.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-07-19Business Team/Minutes/2012-07-192012-07-20T14:32:45Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p class="MsoNormal">Attendees:<span style="mso-spacerun: yes;">&nbsp; </span></p><p>&nbsp;</p><p class="MsoNormal">Scott Lamons (host)</p><p class="MsoNormal">Gary O'Neall</p><p class="MsoNormal">Kamyar Emami</p><p class="MsoNormal">Phil Odence</p><p class="MsoNormal">Pierre Lapointe</p><p class="MsoNormal">Michael Herzog</p><p class="MsoNormal">Jilayne Lovejoy</p><p class="MsoNormal">Steve Cropper (joined later)</p><p>&nbsp;</p><p class="MsoNormal">Agenda/Notes</p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">1. Linuxcon (Panel, Working group meeting, 1.1 PR?)</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">SPDX Business panel will be on Thursday at 10:25am -- Scott will moderate, Kate, Jilayne, and Jack will represent the tech, legal, and biz teams.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Scott will be setting up a meeting in the next couple weeks to start planning the content and flow.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>He will also reach out to Matt Germonprez to gauge interest in participating to talk about the work they're planning around Fossology (see below). </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Working group meeting on Tuesday from 1-6pm will focus on 2.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>The first hour will be reserved to provide an SPDX introduction and meet any new participants.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will work with LF to get this posted to the website.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Press release for 1.1?<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Consensus was that it's a good thing to do.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Review previous release for 1.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will check with Amanda McPherson on logistics for putting this out via LF.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Things to include:<span style="mso-spacerun: yes;">&nbsp; </span>updates to the license list, matching guidelines, CCO in response to community input , tools?</span></p><p>&nbsp; </p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">2. Outreach Activities (Fossology, Open Compliance program, Other?) </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Matt Germonprez at the University of Nebraska Omaha (UNO) and team are in the process of standing up a public instance of Fossology and they are forming a project to add SPDX functionality to Fossology.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Scott and Bob Goebille (Fossology architect) met with Matt to discuss their plans.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Bob is working with the team to resolve several issues.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Gary O'Neall and Kate Stewart offered their support as well.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p class="MsoNormal">&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">LF considering assigning a program/project manager to SPDX.<span style="mso-spacerun: yes;">&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;&nbsp;</span>FOSS barcode tracker (announced May 30) seems complementary to SPDX</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"><br /></span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Gary talked about target development/build tools such as Eclipse (e.g. an&nbsp;Eclipse plugin that wraps some of the existing tools).<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Gary looking for some commitment from the Eclipse foundation.<span style="mso-spacerun: yes;">&nbsp; </span>Michael to reach out to Phillip at Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp; </span>Apache uses Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">3. Web update.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Plan is to switch to the new website over the weekend of 7/28.&nbsp; Steve to send a message to the SPDX team as a heads up and coordintate with Martin.<span style="mso-spacerun: yes;">&nbsp; </span>If there are any major problems we can switch it back before Monday.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-07-19Business Team/Minutes/2012-07-192012-07-20T14:29:43Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p class="MsoNormal">Attendees:<span style="mso-spacerun: yes;">&nbsp; </span></p><p>&nbsp;</p><p class="MsoNormal">Scott Lamons (host)</p><p class="MsoNormal">Gary O'Neall</p><p class="MsoNormal">Kamyar Emami</p><p class="MsoNormal">Phil Odence</p><p class="MsoNormal">Pierre Lapointe</p><p class="MsoNormal">Michael Herzog</p><p class="MsoNormal">Jilayne Lovejoy</p><p class="MsoNormal">Steve Cropper (joined later)</p><p>&nbsp;</p><p class="MsoNormal">Agenda/Notes</p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">1. Linuxcon (Panel, Working group meeting, 1.1 PR?)</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">SPDX Business panel will be on Thursday at 10:25am -- Scott will moderate, Kate, Jilayne, and Jack will represent the tech, legal, and biz teams.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Scott will be setting up a meeting in the next couple weeks to start planning the content and flow.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>He will also reach out to Matt Germonprez to gauge interest in participating to talk about the work they're planning around Fossology (see below). </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Working group meeting on Tuesday from 1-6pm will focus on 2.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>The first hour will be reserved to provide an SPDX introduction and meet any new participants.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will work with LF to get this posted to the website.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Press release for 1.1?<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Consensus was that it's a good thing to do.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Review previous release for 1.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will check with Amanda McPherson on logistics for putting this out via LF.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Things to include:<span style="mso-spacerun: yes;">&nbsp; </span>updates to the license list, matching guidelines, CCO in response to community input , tools?</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">2. Outreach Activities (Fossology, Open Compliance program, Other?) </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Matt Germonprez at the University of Nebraska Omaha (UNO) and team are in the process of standing up a public instance of Fossology and they are forming a project to add SPDX functionality to Fossology.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Scott and Bob Goebille (Fossology architect) met with Matt to discuss their plans.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Bob is working with the team to resolve several issues.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Gary O'Neall and Kate Stewart offered their support as well.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">LF considering assigning a program/project manager to SPDX.<span style="mso-spacerun: yes;">&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;&nbsp;</span>FOSS barcode tracker (announced May 30) seems complementary to SPDX</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"><br /></span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Gary talked about target development/build tools such as Eclipse (e.g. an&nbsp;Eclipse plugin that wraps some of the existing tools).<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Gary looking for some commitment from the Eclipse foundation.<span style="mso-spacerun: yes;">&nbsp; </span>Michael to reach out to Phillip at Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp; </span>Apache uses Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">3. Web update.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Plan is to switch to the new website over the weekend of 7/28 -- Steve to send a message to the SPDX team as a heads up and coordintate with Martin.<span style="mso-spacerun: yes;">&nbsp; </span>If there are any major problems we can switch it back before Monday.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-07-19Business Team/Minutes/2012-07-192012-07-20T14:27:31Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p class="MsoNormal">Attendees:<span style="mso-spacerun: yes;">&nbsp; </span></p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal">Scott Lamons (host)</p><p>&nbsp;</p><p class="MsoNormal">Gary O'Neall</p><p>&nbsp;</p><p class="MsoNormal">Kamyar Emami</p><p>&nbsp;</p><p class="MsoNormal">Phil Odence</p><p>&nbsp;</p><p class="MsoNormal">Pierre Lapointe</p><p>&nbsp;</p><p class="MsoNormal">Michael Herzog</p><p>&nbsp;</p><p class="MsoNormal">Jilayne Lovejoy</p><p>&nbsp;</p><p class="MsoNormal">Steve Cropper (joined later)</p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal">Agenda/Notes</p><p>&nbsp;</p><p class="MsoNormal">&nbsp;</p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">1. Linuxcon (Panel, Working group meeting, 1.1 PR?)</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">SPDX Business panel will be on Thursday at 10:25am -- Scott will moderate, Kate, Jilayne, and Jack will represent the tech, legal, and biz teams.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Scott will be setting up a meeting in the next couple weeks to start planning the content and flow.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>He will also reach out to Matt Germonprez to gauge interest in participating to talk about the work they're planning around Fossology (see below). </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Working group meeting on Tuesday from 1-6pm will focus on 2.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>The first hour will be reserved to provide an SPDX introduction and meet any new participants.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will work with LF to get this posted to the website.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Press release for 1.1?<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Consensus was that it's a good thing to do.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Review previous release for 1.0.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp; </span>Scott will check with Amanda McPherson on logistics for putting this out via LF.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Things to include:<span style="mso-spacerun: yes;">&nbsp; </span>updates to the license list, matching guidelines, CCO in response to community input , tools?</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">2. Outreach Activities (Fossology, Open Compliance program, Other?) </span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Matt Germonprez at the University of Nebraska Omaha (UNO) and team are in the process of standing up a public instance of Fossology and they are forming a project to add SPDX functionality to Fossology.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Scott and Bob Goebille (Fossology architect) met with Matt to discuss their plans.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Bob is working with the team to resolve several issues.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;</span>Gary O'Neall and Kate Stewart offered their support as well.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">LF considering assigning a program/project manager to SPDX.<span style="mso-spacerun: yes;">&nbsp; </span><span style="mso-spacerun: yes;">&nbsp;&nbsp;</span>FOSS barcode tracker (announced May 30) seems complementary to SPDX</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"><br /></span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Gary talked about target development/build tools such as Eclipse (e.g. an&nbsp;Eclipse plugin that wraps some of the existing tools).<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span>Gary looking for some commitment from the Eclipse foundation.<span style="mso-spacerun: yes;">&nbsp; </span>Michael to reach out to Phillip at Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp;&nbsp;&nbsp; </span>Apache uses Eclipse.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">3. Web update.<span style="mso-spacerun: yes;">&nbsp;&nbsp; </span></span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">Plan is to switch to the new website over the weekend of 7/28 -- Steve to send a message to the SPDX team as a heads up and coordintate with Martin.<span style="mso-spacerun: yes;">&nbsp; </span>If there are any major problems we can switch it back before Monday.</span></p><p>&nbsp;</p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">&nbsp;</span></p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Legal_Team/Decisions/SPDX_Metadata_License:_Rationale_for_CC0Legal Team/Decisions/SPDX Metadata License: Rationale for CC02012-06-29T20:05:42Z<p>Slamons: Added links to PDDL and CC0 1.0 licenses.</p>
<hr />
<div><h1><strong>Overview</strong></h1><p>SPDX files represent a summary of license information extracted from software source code. The SPDX Legal working group evaluated different licenses that can be used to cover the data contained in a SPDX file. One challenge was that the working group did not want to imply that the data contained in a SPDX file is potentially copyright protected. On the other hand, in some jurisdictions, data could be considered intellectual property. In those jurisdictions the working group stride to provide a license that mitigates the risk of someone obtaining controlling IP rights over SPDX data. The following were the core requirements driving the license evaluation process. We sought a license that:</p><ul><li>does not imply that SPDX data is intellectual property;</li><li>in jurisdictions that permit data to be intellectual property - prevents others from claiming controlling ownership over the data contained in a SPDX file;</li><li>will not hinder adoption of the SPDX format by the open source community;</li><li>minimizes further license proliferation in the open source community;</li><li>permits the exchange of SPDX files under confidentiality terms (potentially temporarily) for special situations that may require it.</li></ul><p>After careful consideration the Creative Commons Zero 1.0 Universal license was chosen. The rationale for each of the license candidates considered can be found below.</p><h1><strong>License Candidates:</strong></h1><p><strong><span style="text-decoration: underline;">Public Domain Dedication and License (PDDL)</span></strong></p><p>PDDL is the current designated license for SPDX files as required by the SPDX 1.0 specification. PDDL was initially chosen because it was a “data” license. That is, it was initially design to be used with data as opposed to software or other copyrightable works. The reception of PDDL as the SPDX file data license has been mixed and somewhat controversial at times.&nbsp; A copy of the PDDL license can be found here: http://opendatacommons.org/licenses/pddl/1.0/</p><ul><li>Pros<ul><li>Designed for licensing data.</li><li>Useful in jurisdictions where intellectual property rights are granted to data (bases).</li><li>Attempts to make data freely accessible (in a similar spirit that open source licenses do for software).</li><li>Permits the exchange of SPDX files under confidentiality terms.</li></ul></li></ul><p>&nbsp;</p><ul><li>Cons<ul><li>Lengthy license (6 pages) – will take time for people to review and understand.</li><li>Yet another new license for open source community to review, understand and accept. Would likely add friction to SPDX adoption.</li><li>A major open source foundation pointed out it would be hard to get PDDL approved by their organization as well as other foundations. This is especially true when considering a license that is not familiar to the community (as is the case with PDDL).</li><li>Use of the license implies that SPDX data is copyright protected.</li></ul></li></ul><p><strong><span style="text-decoration: underline;">MIT Style SPDX Draft</span></strong></p><p>The license text is based on the MIT open source license. A copy of the MIT Style license draft can be found in the appendix of this document.<strong></strong></p><ul><li>Pros<ul><li>Viewed more as a disclaimer notice than a data license. The intent is to view the SPDX file content as data as opposed to protected intellectual property.</li><li>Serves more as a license in jurisdictions where data is considered protectable intellectual property.</li><li>The license text is short and easy to understand.</li><li>The license is familiar to the open source community and would likely not add much friction to the adoption of SPDX.</li><li>Permits the exchange of SPDX files under confidentiality terms</li><li>Cons<ul><li>The license is based on the MIT open source license which was designed to be used with software as opposed to data.</li><li>Requires attribution. Many different SPDX files used in a project or supply chain may potentially require the publication of many different attribution notices.</li></ul></li></ul></li></ul><p>&nbsp;</p><p><strong><span style="text-decoration: underline;">CC0 1.0 - Universal Public Domain Dedication license </span></strong></p><p>Creative Commons (CC) is a non-profit organization devoted to expanding the range of creative works available for others to build upon legally and to share. &nbsp;The organization has released several copyright-licenses known as “Creative Commons” licenses, free of charge to the public. One such license is the CC0 1.0 which allows one to contribute their work to the public domain. A copy of the CC0 1.0 license can be found here: http://creativecommons.org/publicdomain/zero/1.0/</p><ul><li>Pros<ul><li>License text is short and easy to understand.</li><li>License is familiar to the open source community and therefore would likely not to add significant friction to the adoption of SPDX.</li><li>Achieves object of having the data be considered public domain in those jurisdictions where data can be protected as intellectual property.</li><li>Permits the exchange of SPDX files under confidentiality terms.</li><li>Cons<ul><li>License was not designed to be used with data.</li><li>Use of the license implies that SPDX data is copyright protected.</li></ul></li></ul></li></ul><p>&nbsp;</p><p><strong><span style="text-decoration: underline;">No License Provided</span></strong></p><p>One option is to take the position that no license applies.</p><ul><li>Pros<ul><li>Easy to understand. Does not add friction to adoption of SPDX.</li><li>Promotes the idea that the SPDX data is not intellectual property (e.g., not copyrightable).</li><li>Permits the exchange of SPDX files under confidentiality terms.</li><li>Cons</li></ul></li></ul><p>Does not prevent one from trying to obtain controlling rights in jurisdictions where data is potentially considered intellectual property.</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-04-26Business Team/Minutes/2012-04-262012-04-26T18:41:20Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p>Attendees</p><ul><li>Scott Lamons</li><li>Jilayne Lovejoy</li><li>Phil Odence</li><li>Mark Gisi</li><li>Gary O'Neall</li><li>Chuck Gadreaux</li><li>Michael Herzog</li><li>Jack Manbeck</li></ul><p>Agenda/Minutes</p><p>&nbsp;</p><ul><li>SPDX Forum follow-up</li><ul><li>Scott received the list of folks who registered for the Forum from Kim.</li><li>Phil O prepared a follow up email that he will send (bcc:) to folks who pre-registered.</li><li>Might have been a few attendees who didn't pre-register.&nbsp; Scott will ask Steve if we can get a copy of the sign-up sheet and add those folks to the spreadsheet and follow-up email.</li></ul><li>Outreach/Adoption</li><ul><li>Communities</li><ul><li>Jack is meeting with the Yacto project this morning</li><li>Scott is trying to setup some time with Jeremy Allison of the Samba project</li></ul><li>Companies</li><li>Tools</li></ul></ul><ul><li>SPDXv2 Discussion (what role should the business team play?)</li><ul><li>Some good work on use cases but we seem to be lacking a higher level business strategy, direction, and roadmap.</li><li>What are the high level problems we're trying to address and how do we prioritize these and decide which ones to focus on in 2.0, 3.0, ... &nbsp; e.g. upstream adoption or solving downstream problems</li><li>Can these be seperated?&nbsp;&nbsp; For example upstream adoption may not depend on new features and functionality in 2.0 (or maybe it does?? -- we're still early in the outreach process!).&nbsp; Should 2.0 be focused on solving the big downstream barriers to adoption by companies, thier suppliers, our their customers</li><li>Might make sense to circle back and confirm that everyone is still in sync with the high level vision and strategy originally layed out for SPDX (Phil&nbsp; to dig up some artifacts on that)</li><li>Micheal volunteered to get us started with a proposal or framework for how the business can&nbsp; help to uncover and/or clearify the strategy and prioriites for SPDX moving forward. &nbsp; He will circulate to the team next week and we will discuss further at our next meeting.</li></ul><li>Web site</li><ul><li>No update from web team</li><li>Scott will review bus team work on the new website to ID gaps prior to next meeting</li></ul><li>Others Topics</li><ul><li>Phil O reported that there is some emerging interest in SPDX from Japan and Korea</li><li>Some discussion about how to encourage participation for folks who can't attend during the normal business hours -- encourage more discussion/collaboration on the email list and website.&nbsp; </li></ul></ul><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-04-26Business Team/Minutes/2012-04-262012-04-26T17:40:42Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p>Attendees</p><ul><li>Scott Lamons</li><li>Jilayne Lovejoy</li><li>Phil Odence</li><li>Mark Gisi</li><li>Gary O'Neall</li><li>Chuck Gadreaux</li><li>Michael Herzog</li><li>Jack Manbeck</li></ul><p>Agenda/Minutes</p><p>&nbsp;</p><ul><li>SPDX Forum follow-up</li><ul><li>Scott received the list of folks who registered for the Forum from Kim.</li><li>Phil O prepared a follow up email that he will send (bcc:) to folks who pre-registered.</li><li>Might have been a few attendees who didn't pre-register.&nbsp; Scott will ask Steve if we can get a copy of the sign-up sheet and add those folks to the spreadsheet and follow-up email.</li></ul><li>Outreach/Adoption</li><ul><li>Communities</li><ul><li>Jack is meeting with the Yacto project this morning</li><li>Scott is trying to setup some time with Jeremy Allison of the Samba project</li></ul><li>Companies</li><li>Tools</li></ul></ul><ul><li>SPDXv2 Discussion (what role should the business team play?)</li><ul><li>Some good work on use cases but we seem to be lacking a higher level business strategy, direction, and roadmap.</li><li>What are the high level problems we're trying to address and how do we prioritize these and decide which ones to focus on in 2.0, 3.0, ... &nbsp; e.g. upstream adoption or solving downstream problems</li><li>Can these be seperated?&nbsp;&nbsp; For example upstream adoption may not depend on new features and functionality in 2.0 (or maybe it does?? -- we're still early in the outreach process!).&nbsp; Should 2.0 be focused on solving the big downstream barriers to adoption by companies, thier suppliers, our their customers</li><li>Might make sense to circle back and confirm that everyone is still in sync with the high level vision and strategy originally layed out for SPDX (Phil&nbsp; to dig up some artifacts on that)</li><li>Micheal volunteered to get us started with a proposal or framework for how the business can&nbsp; help to uncover and/or clearify the strategy and prioriites for SPDX moving forward. &nbsp; He will circulate to the team next week and we will discuss further at our next meeting.</li></ul><li>Web site</li><ul><li>No update from web team</li><li>Scott will review bus team work on the new website to ID gaps prior to next meeting</li></ul></ul><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-04-26Business Team/Minutes/2012-04-262012-04-26T17:39:50Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p>Attendees</p><ul><li>Scott Lamons</li><li>Jilayne Lovejoy</li><li>Phil Odence</li><li>Mark Gisi</li><li>Gary O'Neall</li><li>Chuck Gadreaux</li><li>Michael Herzog</li><li>Jack Manbeck</li></ul><p>Agenda/Minutes</p><p>&nbsp;</p><ul><li>SPDX Forum follow-up</li><ul><li>Scott received the list of folks who registered for the Forum from Kim.</li><li>Phil O prepared a follow up email that he will send (bcc:) to folks who pre-registered.</li><li>Might have been a few attendees who didn't pre-register.&nbsp; Scott will ask Steve if we can get a copy of the sign-up sheet and add those folks to the spreadsheet and follow-up email.</li></ul><li>Outreach/Adoption</li><ul><li>Communities</li><ul><li>Jack is meeting with the Yacto project this morning</li><li>Scott is trying to setup some time with Jeremy Allison of the Samba project</li></ul><li>Companies</li><li>Tools</li></ul></ul><ul><li>SPDXv2 Discussion (what role should the business team play?)</li><ul><li>Some good work on use cases but we seem to be lacking a higher level business strategy, direction, and roadmap.</li><li>What are the high level problems we're trying to address and how do we prioritize these and decide which ones to focus on in 2.0, 3.0, ... &nbsp; e.g. upstream adoption or solving downstream problems</li><li>Can these be seperated?&nbsp;&nbsp; For example upstream adoption may not depend on new features and functionality in 2.0 (or maybe it does?? -- we're still early in the outreach process!).&nbsp; Should 2.0 be focused on solving the big downstream barriers to adoption by companies, thier suppliers, our their customers</li><li>Might make sense to circle back and confirm that everyone is still in sync with the high level vision and strategy originally layed out for SPDX (Phil&nbsp; to dig up some artifacts on that)</li><li>Micheal volunteered to get us started with a proposal or framework for how the business can&nbsp; help to uncover and/or clearify the strategy and prioriites for SPDX moving forward. &nbsp; He will circulate to the team next week and we will discuss further at our next meeting.</li></ul><li>Web site</li><ul><li>No update from web team</li><li>Scott will review bus team work on the new website to ID gaps prior to next meeting</li></ul></ul><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-04-26Business Team/Minutes/2012-04-262012-04-26T14:50:14Z<p>Slamons: </p>
<hr />
<div><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-04-26Business Team/Minutes/2012-04-262012-04-26T14:01:37Z<p>Slamons: </p>
<hr />
<div><p>Attendees:</p><p>Scott Lamons (Host)</p><p>Agenda:</p><!--[if gte mso 9]><xml><br />
<w:WordDocument><br />
<w:View>Normal</w:View><br />
<w:Zoom>0</w:Zoom><br />
<w:TrackMoves/><br />
<w:TrackFormatting/><br />
<w:PunctuationKerning/><br />
<w:ValidateAgainstSchemas/><br />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
<w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
<w:DoNotPromoteQF/><br />
<w:LidThemeOther>EN-US</w:LidThemeOther><br />
<w:LidThemeAsian>X-NONE</w:LidThemeAsian><br />
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript><br />
<w:Compatibility><br />
<w:BreakWrappedTables/><br />
<w:SnapToGridInCell/><br />
<w:WrapTextWithPunct/><br />
<w:UseAsianBreakRules/><br />
<w:DontGrowAutofit/><br />
<w:SplitPgBreakAndParaMark/><br />
<w:DontVertAlignCellWithSp/><br />
<w:DontBreakConstrainedForcedTables/><br />
<w:DontVertAlignInTxbx/><br />
<w:Word11KerningPairs/><br />
<w:CachedColBalance/><br />
</w:Compatibility><br />
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel><br />
<m:mathPr><br />
<m:mathFont m:val="Cambria Math"/><br />
<m:brkBin m:val="before"/><br />
<m:brkBinSub m:val="&#45;-"/><br />
<m:smallFrac m:val="off"/><br />
<m:dispDef/><br />
<m:lMargin m:val="0"/><br />
<m:rMargin m:val="0"/><br />
<m:defJc m:val="centerGroup"/><br />
<m:wrapIndent m:val="1440"/><br />
<m:intLim m:val="subSup"/><br />
<m:naryLim m:val="undOvr"/><br />
</m:mathPr></w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"<br />
DefSemiHidden="true" DefQFormat="false" DefPriority="99"<br />
LatentStyleCount="267"><br />
<w:LsdException Locked="false" Priority="0" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Normal"/><br />
<w:LsdException Locked="false" Priority="9" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 1"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 2"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 3"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 4"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 5"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 6"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 7"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 8"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 9"/><br />
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/><br />
<w:LsdException Locked="false" Priority="10" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Title"/><br />
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/><br />
<w:LsdException Locked="false" Priority="11" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/><br />
<w:LsdException Locked="false" Priority="22" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Strong"/><br />
<w:LsdException Locked="false" Priority="20" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/><br />
<w:LsdException Locked="false" Priority="59" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Table Grid"/><br />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/><br />
<w:LsdException Locked="false" Priority="1" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 1"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 1"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 1"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/><br />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/><br />
<w:LsdException Locked="false" Priority="34" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/><br />
<w:LsdException Locked="false" Priority="29" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Quote"/><br />
<w:LsdException Locked="false" Priority="30" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 1"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 1"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 2"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 2"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 2"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 2"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 2"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 3"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 3"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 3"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 3"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 3"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 4"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 4"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 4"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 4"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 4"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 5"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 5"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 5"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 5"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 5"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 6"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 6"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 6"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 6"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 6"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/><br />
<w:LsdException Locked="false" Priority="19" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/><br />
<w:LsdException Locked="false" Priority="21" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/><br />
<w:LsdException Locked="false" Priority="31" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/><br />
<w:LsdException Locked="false" Priority="32" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/><br />
<w:LsdException Locked="false" Priority="33" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/><br />
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/><br />
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/><br />
</w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]><br />
<style><br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-priority:99;<br />
mso-style-qformat:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:11.0pt;<br />
font-family:"Calibri","sans-serif";<br />
mso-ascii-font-family:Calibri;<br />
mso-ascii-theme-font:minor-latin;<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-fareast-theme-font:minor-fareast;<br />
mso-hansi-font-family:Calibri;<br />
mso-hansi-theme-font:minor-latin;<br />
mso-bidi-font-family:"Times New Roman";<br />
mso-bidi-theme-font:minor-bidi;}<br />
</style><br />
<![endif]--><p><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">SPDX Forum follow-up</span><br /><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Adoption</span><br /><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">SPDX 2.0 (how should the biz team be involved)</span><br /><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Website status</span></p></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Minutes/2012-04-26Business Team/Minutes/2012-04-262012-04-26T14:00:11Z<p>Slamons: </p>
<hr />
<div><p>Attendees:</p><p>Scott Lamons (Host)</p><p>&nbsp;</p><p>Agenda:</p><!--[if gte mso 9]><xml><br />
<w:WordDocument><br />
<w:View>Normal</w:View><br />
<w:Zoom>0</w:Zoom><br />
<w:TrackMoves/><br />
<w:TrackFormatting/><br />
<w:PunctuationKerning/><br />
<w:ValidateAgainstSchemas/><br />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
<w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
<w:DoNotPromoteQF/><br />
<w:LidThemeOther>EN-US</w:LidThemeOther><br />
<w:LidThemeAsian>X-NONE</w:LidThemeAsian><br />
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript><br />
<w:Compatibility><br />
<w:BreakWrappedTables/><br />
<w:SnapToGridInCell/><br />
<w:WrapTextWithPunct/><br />
<w:UseAsianBreakRules/><br />
<w:DontGrowAutofit/><br />
<w:SplitPgBreakAndParaMark/><br />
<w:DontVertAlignCellWithSp/><br />
<w:DontBreakConstrainedForcedTables/><br />
<w:DontVertAlignInTxbx/><br />
<w:Word11KerningPairs/><br />
<w:CachedColBalance/><br />
</w:Compatibility><br />
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel><br />
<m:mathPr><br />
<m:mathFont m:val="Cambria Math"/><br />
<m:brkBin m:val="before"/><br />
<m:brkBinSub m:val="&#45;-"/><br />
<m:smallFrac m:val="off"/><br />
<m:dispDef/><br />
<m:lMargin m:val="0"/><br />
<m:rMargin m:val="0"/><br />
<m:defJc m:val="centerGroup"/><br />
<m:wrapIndent m:val="1440"/><br />
<m:intLim m:val="subSup"/><br />
<m:naryLim m:val="undOvr"/><br />
</m:mathPr></w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"<br />
DefSemiHidden="true" DefQFormat="false" DefPriority="99"<br />
LatentStyleCount="267"><br />
<w:LsdException Locked="false" Priority="0" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Normal"/><br />
<w:LsdException Locked="false" Priority="9" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/><br />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 1"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 2"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 3"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 4"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 5"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 6"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 7"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 8"/><br />
<w:LsdException Locked="false" Priority="39" Name="toc 9"/><br />
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/><br />
<w:LsdException Locked="false" Priority="10" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Title"/><br />
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/><br />
<w:LsdException Locked="false" Priority="11" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/><br />
<w:LsdException Locked="false" Priority="22" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Strong"/><br />
<w:LsdException Locked="false" Priority="20" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/><br />
<w:LsdException Locked="false" Priority="59" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Table Grid"/><br />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/><br />
<w:LsdException Locked="false" Priority="1" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 1"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 1"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 1"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/><br />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/><br />
<w:LsdException Locked="false" Priority="34" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/><br />
<w:LsdException Locked="false" Priority="29" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Quote"/><br />
<w:LsdException Locked="false" Priority="30" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 1"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 1"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 2"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 2"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 2"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 2"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 2"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 3"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 3"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 3"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 3"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 3"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 4"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 4"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 4"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 4"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 4"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 5"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 5"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 5"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 5"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 5"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/><br />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Shading Accent 6"/><br />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light List Accent 6"/><br />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Light Grid Accent 6"/><br />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/><br />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/><br />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/><br />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/><br />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/><br />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/><br />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/><br />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Dark List Accent 6"/><br />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/><br />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful List Accent 6"/><br />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"<br />
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/><br />
<w:LsdException Locked="false" Priority="19" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/><br />
<w:LsdException Locked="false" Priority="21" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/><br />
<w:LsdException Locked="false" Priority="31" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/><br />
<w:LsdException Locked="false" Priority="32" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/><br />
<w:LsdException Locked="false" Priority="33" SemiHidden="false"<br />
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/><br />
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/><br />
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/><br />
</w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]><br />
<style><br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-priority:99;<br />
mso-style-qformat:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:11.0pt;<br />
font-family:"Calibri","sans-serif";<br />
mso-ascii-font-family:Calibri;<br />
mso-ascii-theme-font:minor-latin;<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-fareast-theme-font:minor-fareast;<br />
mso-hansi-font-family:Calibri;<br />
mso-hansi-theme-font:minor-latin;<br />
mso-bidi-font-family:"Times New Roman";<br />
mso-bidi-theme-font:minor-bidi;}<br />
</style><br />
<![endif]--><p><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">SPDX Forum follow-up</span><br /><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Adoption</span><br /><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">SPDX 2.0 (how should the biz team be involved)</span><br /><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">Website status</span></p></div>Slamonshttps://wiki.spdx.org/view/Business_TeamBusiness Team2012-04-26T13:42:52Z<p>Slamons: </p>
<hr />
<div><ul><li><span style="font-size: 10.8px;">This is the working area for the Business Team. This team has primary responsibility for planning and coordinating the rollout of SPDX.</span></li><li><span style="font-size: 10.8px;">The Business Team meets every other Thursday at 11am eastern US time alternating weeks with the General Meeting.&nbsp;&nbsp; Dial-in # and other details will be posted to the team email list...</span></li><li><span style="font-size: 10.8px;">You can sign up for the <a href="http://lists.spdx.org/mailman/listinfo/spdx-biz">mailing list here</a>.</span></li></ul></div>Slamonshttps://wiki.spdx.org/view/Business_Team/Beta_Program/FeedbackBusiness Team/Beta Program/Feedback2011-07-07T14:47:27Z<p>Slamons: </p>
<hr />
<div><p>Add your Beta Feedback Here.&nbsp; Put your name &amp; company at the beginning of your feedback.</p><p>&nbsp;</p><p><strong>My Company -- My Name</strong></p><ol><li>feedback item 1</li><li>feedback item 2</li></ol><p>&nbsp;</p><hr /><p>HP - Scott Lamons</p><p><strong>How well did the SPDX format cover information you need to exchange?</strong></p><p>The most useful part for our review process is the higher level package information because we require product/project teams to enter information into our tracking system about the open source package they are using/distributing -- often these teams make mistakes or enter incomplete information.&nbsp; SPDX potentially provides a better and&nbsp; more trustworthy way for teams to enter this information into our system. </p><p><strong>What was effort involved in converting to/from SPDX format?</strong></p><p>Very straight forward using the tools that Gary provided although it might be helpful to have a GUI based tool for non-expert users.&nbsp;&nbsp; We did encounter a few bugs but I believe these have since been corrected.<strong>&nbsp;</strong></p><p><strong>Did the SPDX format help you understand what was in the software?</strong></p><p>Yes, the spreadsheet format is well organized and easy to follow.<strong><br /></strong></p><p><strong>How did the standard license information work for you?</strong></p><p><strong>Can you see how using SPDX could save your organization time/money?</strong></p><p><strong>Are any changes needed to make SPDX meet your needs?</strong></p><p>Separate package name and version fields would be helpful.&nbsp;&nbsp; Combining name and version into the PackageName field will require additional processing and interpretation which we would rather not do since our system has seperate fields for FOSS name and version.&nbsp;&nbsp; </p><p>Some corrections and comments in the specification are attached in MS Word format.</p><p>&nbsp;</p><p><br />
<br />
<br />
<span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px; font-weight: bold;">Antelink -- Freddy Munoz</span></p><br />
<br />
<p><span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px;">&nbsp;</span></p><ol><li style="font-weight: normal;"><strong>How well did the SPDX format cover information you need to exchange?<br /></strong>The format provides reliable information about licenses (based on human analysis) and the distinction between the licences who are declared by the package creator and those which are found in files.</li><li style="font-weight: normal;"><strong>What was effort involved in converting to/from SPDX format?<br /></strong>The conversion from the SPDX file format to an object model was easily made.</li><li style="font-weight: normal;"><strong>Did the SPDX format help you understand what was in the software?<br /></strong>The SPDX file format gives declarative fine scale information about the licenses and the origin of each file in the package.</li><li style="font-weight: normal;"><strong>How did the standard license information work for you?<br /></strong>For us the standard license information is very important because is much more precise and reliable than a simple declaration of the licence's name with no standard formatting.</li><li style="font-weight: normal;"><strong>Can you see how using SPDX could save your organization time/money?<br /></strong>When we collect information about open source projects, it would be easier to parse information if the licence information were completely machine readable. SPDX format provides this feature.</li><li style="font-weight: normal;"><strong>Are any changes needed to make SPDX meet your needs?<br /></strong>If any file's licence cannot be defined ("none") it would be better if the format allowed to use "none" as one of concluded licenses.<br />It's necessary to impose every concluded license to be the concluded license of at least one file, otherwise some licenses could be considered as concluded licenses of the package but we cannot know from which file (component) they come from.</li></ol><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/File:Spdx-draft20110605-spl.docFile:Spdx-draft20110605-spl.doc2011-07-07T14:46:29Z<p>Slamons: </p>
<hr />
<div>Scott Lamons corrections/comments on 6/5/11 spdx spec</div>Slamonshttps://wiki.spdx.org/view/Business_Team/Beta_Program/FeedbackBusiness Team/Beta Program/Feedback2011-07-07T14:27:58Z<p>Slamons: </p>
<hr />
<div><p>Add your Beta Feedback Here.&nbsp; Put your name &amp; company at the beginning of your feedback.</p><p>&nbsp;</p><p><strong>My Company -- My Name</strong></p><ol><li>feedback item 1</li><li>feedback item 2</li></ol><p>&nbsp;</p><hr /><p>HP - Scott Lamons</p><p><strong>How well did the SPDX format cover information you need to exchange?</strong></p><p>The most useful part for our review process is the higher level package information because we require product/project teams to enter information into our tracking system about the open source package they are using/distributing -- often these teams make mistakes or enter incomplete information.&nbsp; SPDX potentially provides a better and&nbsp; more trustworthy way for teams to enter this information into our system. </p><p><strong>What was effort involved in converting to/from SPDX format?</strong></p><p>Very straight forward using the tools that Gary provided although it might be helpful to have a GUI based tool for non-expert users.&nbsp;&nbsp; We did encounter a few bugs but I believe these have since been corrected.<strong>&nbsp;</strong></p><p><strong>Did the SPDX format help you understand what was in the software?</strong></p><p>Yes, the spreadsheet format is well organized and easy to follow.<strong><br /></strong></p><p><strong>How did the standard license information work for you?</strong></p><p><strong>Can you see how using SPDX could save your organization time/money?</strong></p><p><strong>Are any changes needed to make SPDX meet your needs?</strong></p><p>Separate package name and version fields would be helpful.&nbsp;&nbsp; Combining name and version into the PackageName field will require additional processing and interpretation which we would rather not do since our system has seperate fields for FOSS name and version.&nbsp;&nbsp; </p><p>Some corrections and comments in the specification are attached in MS Word format.</p><p>&nbsp;</p><p><br />
<br />
<br />
<span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px; font-weight: bold;">Antelink -- Freddy Munoz</span></p><br />
<br />
<p><span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px;">&nbsp;</span></p><ol><li style="font-weight: normal;"><strong>How well did the SPDX format cover information you need to exchange?<br /></strong>The format provides reliable information about licenses (based on human analysis) and the distinction between the licences who are declared by the package creator and those which are found in files.</li><li style="font-weight: normal;"><strong>What was effort involved in converting to/from SPDX format?<br /></strong>The conversion from the SPDX file format to an object model was easily made.</li><li style="font-weight: normal;"><strong>Did the SPDX format help you understand what was in the software?<br /></strong>The SPDX file format gives declarative fine scale information about the licenses and the origin of each file in the package.</li><li style="font-weight: normal;"><strong>How did the standard license information work for you?<br /></strong>For us the standard license information is very important because is much more precise and reliable than a simple declaration of the licence's name with no standard formatting.</li><li style="font-weight: normal;"><strong>Can you see how using SPDX could save your organization time/money?<br /></strong>When we collect information about open source projects, it would be easier to parse information if the licence information were completely machine readable. SPDX format provides this feature.</li><li style="font-weight: normal;"><strong>Are any changes needed to make SPDX meet your needs?<br /></strong>If any file's licence cannot be defined ("none") it would be better if the format allowed to use "none" as one of concluded licenses.<br />It's necessary to impose every concluded license to be the concluded license of at least one file, otherwise some licenses could be considered as concluded licenses of the package but we cannot know from which file (component) they come from.</li></ol><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p></div>Slamonshttps://wiki.spdx.org/view/Old/Linux_Collaboration_Summit_2011Old/Linux Collaboration Summit 20112011-03-28T20:37:07Z<p>Slamons: </p>
<hr />
<div><p>The <a href="http://events.linuxfoundation.org/events/collaboration-summit">Linux Collaboration Summit</a> is in San Francisco, April 6-8. The SPDX <a href="http://events.linuxfoundation.org/events/collaboration-summit/spdx-technical">Technical</a> and <a href="http://events.linuxfoundation.org/events/collaboration-summit/spdx-business">Business</a> teams will be holding face to face meetings. If you would like to participate, please <a href="http://www.regonline.com/Register/Checkin.aspx?EventID=923747">request an invitation</a> to the event from the Linux Foundation. If you alert Phil Koltun&nbsp;pkoltun@linuxfoundation.org that you have requested an invitation because you are interested in SPDX parrticipation, he can streamline the approval process.</p><p>&nbsp;</p><p>And, if you are coming, please edit your name into the RSVP list(s) below:</p><p>&nbsp;</p><p><strong>I'm coming to the SPDX Technical Team Face to Face</strong>:</p><ul><li>Kate Stewart, Canonical</li><li>Phil Odence, Black Duck Software</li><li>Phil Koltun, Linux Foundation</li><li>Peter Williams, OpenLogic</li><li>Michael Herzog, nexB</li><li>Gary O'Neall, Source Auditor</li><li>Kirsten Newcomer, Black Duck Software</li></ul><p><strong>I'm coming to the SPDX Business Team Face to Face:</strong></p><ul><li>Kim Weins, Open Logic</li><li>Phil Odence, Black Duck Software</li><li>Phil Koltun, Linux Foundation</li><li>Pierre Lapointe, nexB</li><li>Michael Herzog, nexB</li><li>Gary O'Neall, Source Auditor</li><li>Kate Stewart, Canonical</li><li>Kirsten Newcomer, Black Duck Software</li><li>Scott Lamons, HP Open Source Program Office</li></ul></div>Slamons