I do think we’ll want some sort of XML manifest; we need at least somewhere to define the synonyms, among other bits.

Hi Kris, Jilayne and legal team, I'm seeing a lot of activity on the XML licenses, so I started looking into expanding the tools that generate the website to support the new XML format. Here's

Hi All, meeting minutes are posted and copied here, as there were a couple things I added post-call. http://wiki.spdx.org/view/Legal_Team/Minutes/2016-05-12 Agenda[edit] 1) some general discussion

“SPDX Legal call” has been updated.

Reminder we have our regular call at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00 CT, 1:00PM ET). http://uberconference.com/SPDXTeam User PIN: 38633 or Call this number: (United States): +1-857-216-2871

Hi, I am new on SPDX legal list. I work at Kennisland, a think tank in the Netherlands and work on copyright and technology issues. Mostly on the open content aspects of licensing and hardly ever on

Hi Reza, Thank you for your proposal for a generic SPDX license to denote proprietary licenses. The SPDX-Legal team has considered your request and reviewed the examples you provided from npm along

For what it’s worth, pretty much everything is legal structure-wise; the structure of the final form of the XML will definitely be guided by any problems we need to solve that we encounter during

Thanks Kris for the good recap of where we are on error-correcting the XML representation of required, optional, and replaceable text. Of course it is no fun to manually edit XML, but I think I recall

Sam: They are definitely supposed to be nested. If you are seeing one like this than either the original template's spacing was equally flat (I could see it for one or two, but not many), or the

In the corrective pass I made to fix the repeated list problem, some step of the processing got a little overzealous in its escaping, and so things like “ are escaped too ("). You might also have

I have a lot of respect for what you are embarking in: I would not dare editing by hand 100 of such XML files: I find this rather confusing and error prone. And I am a programmer... But I think I

Hi, When reviewing the SPDX XML files, I see many licenses that contain nested lists such as: 1) some text… a) some text… And these are converted to XML like this: <list> <li>

Hi, I would like to resolve some queries in the SPDX XML files in relation to the strange text such as ’. The characters < and > and & are used in the structure of XML files, for example in the

Big thanks to Sam Ellis for going through a bunch of licenses and cleaning up the erroneously auto-generated <list> tags and such. A note: the ones with weird indenting and ‘undefined’ seem to

Hi Kris, Did I do this correctly? I fixed a <list> tag issue and created a PR for your repo rather than for the SPDX repo. Is that right? Thanks, Brad -- Brad Edmondson, Esq. 512-673-8782 |

If you need to get ahold of me, email kris@... or kris.re@... – you can also get me on Skype at ‘myndzi’

Hi All, This is a reminder that we have a special call Thursday at 9am Pacific / 10am Mtn / noon Eastern (after the SPDX General call) for the purpose of going over how to review the XML files for the

opensource@... has invited you to the event: SPDX Legal call for XML files review, scheduled for May 5, 2016 at 10:00 AM (America/Denver). To accept or decline this invitation, click the link below.

The goal of this call will be to go over the process for reviewing the XML license files together and then decide how to divvy up the review process. Before the May 5th call, please: - watch the