Hello Kate, It's done. Bugs 1040 and 1041. Best regards, Marc-Etienne -- Marc-Etienne Vargenau Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE +33 (0)1 30 77 28 33,

Hello Marc-Etienne, Good catch. Looks like you've got two bugs there, one against the translation tool, and one against the spec. Please file the bugs from https://bugs.linuxfoundation.org,

Hello, I have questions regarding the syntax of comments in an SPDX file in tag format. From the examples, it seems that ## starts a comment. For example: ## Creation Information But I do not see

Arrgggh. Sorry for the volume. In my earlier note, I provided the wrong link for the Biz Team work looking to be reviewed. Use this one: http://spdx.org/wiki/spdx-vision-mission From: Michael Herzog

Please take the time to review Legal Team description and License List description as well as Mission/Vision work from Business Team. Attendance: 10 May 17 minutes approved Legal Team Report

Hello, I suggest the following improvements in the SPDX examples. They could be included in the final 1.1 spec. In 4.1.6 replace <name>glibc 2.11.1</name> with <name>glibc</name> In

All, I neglected to include the minutes from the last meeting in my reminder email. First order of business is to approve. http://www.spdx.org/wiki/20120517-general-meeting-minutes Phil

> Excuse the late notice. I am traveling. Normal time/ normal agenda today. > > Sent from my iPhone

Excuse the late notice. I am traveling. Normal time/ normal agenda today.

Thanks Marc - I corrected the tools page per your message below. In terms of case sensitive - I don't recall any discussion on this relative to the entire file. I know that some of the specific

Hello Gary, Thank you for your quick answer. Responses inline also. I had overlooked this page. In page http://spdx.org/tools I would replace "Rdf to XMLversion 0.9.6" by "Rdf to HTMLversion

Hi Marc-Etienne, Responses inline below Gary

Hello, I am trying to understand the SPDX 1.0 spec so that I can export our FOSS database in SPDX format. I have the following questions: The are two formats, one in text and one in XML/RDF. 1) Is

Hi, Just a reminder to get any use cases you want considered for 2.0 to be added to the wiki pages this week [1]. Template example to be filled out can be found in those with active links, for

I don't always send out minutes (generally include link in next meeting reminders), but there are some important discussions in play, so I thought it would make sense to get them out sooner and not

Thanks Jilayne. I may need to miss the legal workstream due to mandatory day-job meeting, but will try to dial in late. Regarding the SPDX License List description: in the sentence, “The SPDX

Well, better late than never :) Wednesday, 16 May Legal Work Group call, 8am PST / 11am EST Dial-in: 1.866.740.1260 Access: 240 4545 Agenda: (from last call's meeting minutes) 1. SPDX total vision:

Meeting Time: May 17, 8am PST / 10 am CST / 11am EST / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: Conference code: 7812589502 Toll-free dial-in

Folks: Here is a resend of the Web update message that was originally sent by Kim in February. Pierre, Martin and I worked on a status page today which is here:

Thanks Jilayne. A large, well-vetted, standardized and generally accepted license list is our foundation. I volunteer to assist in timely review of the new license submissions, whether as part of