THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Legal Team/Minutes/2016-02-18
Attendees
- Paul Madick
- Jilayne Lovejoy
- Kris Reeves
- Sam Ellis
- Eric Weddington
- Phil Odence
Agenda
1) Please see notes from joint call on the new proposal for improved license list matching markup and maintenance here: http://wiki.spdx.org/view/Technical_Team/Minutes/2016-02-09 we will go over summary of what was discussed and then focus on determining process for going forward.
- update/review from Kris on state of proposal and look at first pass output and looked at an example in light of meeting minutes from joint call
- comment that <body> tag doesn't include optional tags such as <title> or <copyright>; but <body> tag also allows to have variations?
- what about licenses that have different language translations that are considered equivalent? Sam has mapped translations to same identifier (for EUPL, and maybe CC licenses) - will need to discuss how to handle such situations as its own discussion
- list of equivalent words would still apply, but not illustrated in these files; those would be included in another iteration of the license file that is more computer-friendly. These master files are for denoting things humans are good to identify that computers are not good at identifying
- standard header uses a tag, which is missing in this pass; might be better to have it there with nothing in tag. header tag should not be included in tag that wraps the entire license
- use of <body> tag for text of actual license alone is helpful if you want to automate reproducing just the license text
- also discussed whether we would want to differentiate sub-sections within license text - value here could be in terms of compliance to reference specific sections and allowing traceability where compliance is not 100%, could identify where compliant
- tagging bullets to illustrate where they can be disregarded; could not mark some numbering if want to have those matching
- matching guidelines may change from, "you don't have to match bullets" to "you don't have to match on anything in this tag"
- these XML files are master files from which other iterations (e.g., HTML pages, plain text, etc.) are generated from
- decision point re: what to call tags and how to nest them and map this to current matching guidelines with beginning of revisions for matching guidelines - starting point
- better to not map on RDF
2) update on Collab Summit schedule
- who will be there: Jilayne, Paul, Kris, Phil - maybe, Eric and Sam
3) New license requests:
- Free Art License 1.3 (in Google doc)
- License Metadata Exception 1.0 - Kyle Mitchell see: http://lists.spdx.org/pipermail/spdx-legal/2015-December/001611.html
4) Proposal of process that Gary wrote: add comments there and we'll schedule time to discuss more thoroughly on upcoming call(s): https://docs.google.com/document/d/115Lis1SJV7Rp-XuNjIysU61urzFGjUOBPqEdVyGLsfI/edit (if time and in light of #1)