Now that the technical sub-group has initiated its work i think it would be worth having a issue tracking system. This would allow us to reliably track issues with the spec and to make sure nothing fa

Per discussion late meeting, agendas will be going out in bodies of emails and minutes will go out as links to archive at spdx.org. I'll strive to get minutes out a week in advance, though I'm behind

+2 for decoupling the spec from the licenses. We need to be able to update the spec and the license list on different cycles. We should also anticipate that many orgs may want to keep a local copy of

New proposed field for project that a file came from I would like to propose a new field in the file section. The field would be used to identify the OSS component/package that a file originated from.

Hello Edd (DOAP project owner), The SPDX (http://spdx.org) working group is involved in defining a standard format for communicating the components, licenses and copyrights associated with a software

SPDX Rollout - slides from call yesterday Hi everyone, Attached are the slides John Ellis and I put together to start to organize the tasks needed for the rollout of SPDX. We are going to be asking fo

Colleagues, Those interested in participating in the RDF track, please reconvene next Tuesday. Among other hot topics, we'd like to take a closer look at the ontology, which for collaborative review p

http://www.spdx.org/wiki/20100909-minutes International colleagues, While I am thinking of it, most countries shift from daylight time to regular time a few weeks before the US does on Nov 7. We'll ke

hi all, I read the specs and saw: 1.6. Format Requirements: 1.6.1. Must be in a human readable form. 1.6.2. Must be in a syntax that a software tool can read and write. In my experience these two are

This should have gone out sooner so we may want to reschedule to ensure better attendance. I propose to have a quick call for those who are expecting it. For those who this note is catching off guard,

Kim asked about Ninka. It is our license identification tool. It is really a research prototype, but it works. It is particularly good at not making mistakes, at the expense if not identifying the lic

First, some common equivalent words/phrases: ---------------------------------------------------------------------- license|licence distributable|licensed|released|made available can|may terms and con

Help Wanted for Successful Rollout of SPDX Hello Everyone, The SPDX team is hard at work on completing the spec and nailing down all of the license details. To make sure we are successful in getting S

Colleagues, Those interested in participating in the RDF track, please reconvene next Tuesday. Among other hot topics, we'd like to review in more detail the relationship between SPDX and other standa

Meeting Time: Sept 23, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC Conf call dial-in: Conference code: 7812589502 Toll-free dial-in number (U.S. and Canada): (877) 435-0230 International dial-in number

Issue: Not clear how to include SPDX author comments to the consumers of the SPDX file. For example, a SPDX author may like to include a disclaimer, assumptions made, context of the analysis performed

All: as discussed during today's call here are some pointers to Launchpad RDF: This is an example of a project page: https://launchpad.net/do and the matching RDF metadata: https://launchpad.net/do/+r

Hi, Following up from last week and from SPDX call today, we'll be having a special topic call tomorrow on the licenses. Here's the dial in information for the call tomorrow: US 866-740-1260 Look up i

Hello All, I am getting up to speed, have taken a close look at the current spec, and have some comments noted below. 3.4 Download URL COMMENT: We may want to have some guideline as to which page is t

All: this is most likely a known problem, but the draft web page for the spec at http://www.spdx.org/wiki/spdx/specification seems to be quite hard to read (many empty lines), the paragraph numbers ar