Hi All Minutes are now available. http://www.spdx.org/wiki/business-team-meeting-agendaminutes-20110106 We spent most of the call talking about the Beta program. We are targeting Feb 3rd to have an

Hi SPDX Team, Most of the links on the SPDSX site are not working – I was trying to get to the license list. Tom Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mobile:

This was caused by a Drupal upgrade I did earlier today. The issue has not been fixed yet (<http://drupal.org/node/1019788>) so I downgraded to the previous version. * Tom Incorvia

more details » SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT Happy New Year to all. This calendar appointment is for our regular bi-weekly SPDX Legal Workstream call. Many

This event has been changed. more details » Changed: SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT Happy New Year to all. This calendar appointment is for our regular bi-weekly SPDX Legal

This event has been changed. more details » SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT Changed: All: - Please note, proposed minutes from our last meeting are posted on the SPDX Wiki under

Meeting Time: Dec 2, 8am PDT / 10 am CDT / 11am EDT / 16:00 UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: Conference code: 7812589502 Toll-free dial-in number

There has been a bit of discussion in the technical working group about the role of judgments in spdx. It has been suggested that information that is the result of human, or automated

Note: I realize that the link I sent our for the webshare has an older date embedded in it. Please ignore and use it anyway. Thanks, Phil L. Philip Odence Vice President of Business Development Black

Based on discussions on the SPDX call today, I think we are closing in on the following proposal for the file level to address the concerns raised by Open Logic. There will be a special call tomorrow

What about naming the field that represents the actual license of a file/package "License". In the current spec File already has such a property so all that would have to be done is adjust the

Kate: Thank you for sending. Agree 100%. All: This issue has been a continually thought of all founders since the origins of SPDX. The below is consistent with the original intent of SPDX, and

I think the concept is sound and, as Rockett says, consistent. Minor stuff: - I agree with Peter that we may want to tweak the names and the descriptions. - Description under Asserted still says

Kate and Peter -- I am trying to understand the meaning and value of "detected" and/or "declared" as distinguished from "your best guess", i.e., "asserted". What would be the value of the detected

<scott.k.peterson@...> wrote: I don't know about this one. Would this statement be representable in a declared license file? It requires multiple facts and deduction based on those facts to

Hi Everybody, is there a place where the abbreviations (as to be used in the SPDX document) are listed? This page only lists the full names. http://www.spdx.org/licenses/ -- -- Daniel M. German

Daniel, The license list spreadsheet is located here: http://spdx.org/wiki/working-version-license-list The most recent version is 1.4 and will have a column with the short names therein. The

Thanks Jylayne, one thing that would be useful (for those of us wanting to identify the license of a file) is to have examples of the use of each license (not the license itself, but how it is used).

What kind of example did you have in mind? Do you mean an example of a particular software package that uses a particular license? Sent from J's iPhone

<Jlovejoy@...> wrote: A file that contains it. For example, this is the usage of the GPL-2.0+ (excerpted from a Bison file): usage is very different from the text of the license