Hi Gary, Thanks for your thoughtful analysis. I understand that we ought to hew as close to standards as possible and I agree with you that we should wait before implementing so we get it right the first time. I also agree that yet another format increases maintenance costs. Glad to hear that there is interest in JSON, I think a lot of developers reach for it nowadays, perhaps not in the 'enterprise' market but certainly on the web and I've seen it increasingly used in embedded. Enterprise applications move slowly and have a hard time I feel with agile processes, this may be my bias speaking but nonetheless I think the uses cases of SPDX point to a flexible data exchange like JSON provides.
Regards, Jeremiah On Fri, Dec 9, 2016 at 1:19 PM, <[email protected]> wrote: > Hi Jeremiah, > > > > I’ve heard quite a bit of interest in JSON format for SPDX. We currently > have the license information now available in JSON format (see > https://github.com/spdx/license-list-data/tree/master/json or on the > website https://spdx.org/licenses/licenses.json). > > > > I’m a bit torn as to whether we need to spec out the specifics of what > JSON SPDX would look like. On one hand, there is enough work maintaining > tag/value + RDF/XML. On the other hand, if every implementation comes up > with slightly different choices for names (or worse, structure), we will > not be able to use JSON to interoperate between implementations. > > > > It is tempting to implement a JSON converter for the Java SPDX tools (it > already converts spreadsheet, tag/value, RDF/XML and outputs HTML), but I > think I’ll wait to see how the standardization discussions go first. > > > > Gary > > > > *From:* [email protected] [mailto:spdx-tech-bounces@ > lists.spdx.org] *On Behalf Of *Jeremiah Foster > *Sent:* Thursday, December 8, 2016 11:27 AM > *To:* Schuberth, Sebastian > *Cc:* [email protected]; Steenbergen, Thomas > *Subject:* Re: SPDX Roadmap Ideas for 2017? > > > > > > > > On Mon, Dec 5, 2016 at 3:17 AM, Schuberth, Sebastian < > [email protected]> wrote: > > Hi Kate, > > > > One basic thing I’m missing is an official validator for the tag / value > (TV for short) format, supporting different versions of the spec. I know > there are tools [1] to convert TV to RDF which can be misused to “validate” > TV, but any errors then refer to the converted RDF instead of the original > TV. Also, these projects are somewhat heavyweight if all you want is to > validate TV. It would be nice to expose such a validator via a simple web > frontend, similar to how Travis CI does it for its “.travis.yml” files [2]. > > > > I'd like to see this too. My idea was to translate the tagged values into > a JSON data object and then produce a web page based on the object. This > gives me the opportunity to switch to RDF later, but its not what I'm > after. I want to be able to scan a large directory of source code > directories, like the Yocto project produces and be able to browse that > easily with a web browser. That data is ephemeral since we do lots of > builds and our CI is chugging along all the time, the RDF is just too > heavy-weight here. I've started work on something called SPDXL which is a > perl script to do what I've described. Perhaps there are other ways to do > this -- I don't want to reinvent the wheel. We can switch to shell or > python if that is preferred but we should find a way to get a tool like > this since I suspect more than just you and I will use this. > > > > > > Another more sophisticated tool that would be useful is a graphical TV > editor. Something that limits the “degrees of freedom” of plain text to > only valid choices, offers drop-downs for known licenses and DocumentRefs, > etc. Such a tool would be very useful e.g. for legal councils to add their > conclusions / comments to existing TV files without the risk to break the > syntax. > > > > Sorry, I'm addicted to emacs so can't help here. > > > > > > We’re currently thinking about implementing the TV validator. Anyone > interested in joining such an effort is welcome to contact me. > > > > I'm in. :-) > > > > > > [1] https://github.com/spdx/tools#spdx-format-converters > > [2] http://lint.travis-ci.org/ > > > > > > [image: Macintosh > HD:Users:jerchow:Downloads:Asset_Package_01_160721:HERE_Logo_2016:sRGB:PDF:HERE_Logo_2016_POS_sRGB.pdf] > > > > *Sebastian Schuberth* > > *Lead Engineer* > > *Open Source Governance, Chief Technology Office* > > > > HERE Berlin > > Invalidenstraße 116, 10115 Berlin > > *52° 31' 52" N 13° 23' 5" E* > > > > [image: > /Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMail_Signature/_Layout/_Images/20160726_HERE_EMail_Signature_360.gif] > <http://360.here.com/> [image: > /Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMail_Signature/_Layout/_Images/20160726_HERE_EMail_Signature_Twitter.gif] > <https://www.twitter.com/here> [image: > /Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMail_Signature/_Layout/_Images/20160726_HERE_EMail_Signature_FB.gif] > <https://www.facebook.com/here> [image: > /Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMail_Signature/_Layout/_Images/20160726_HERE_EMail_Signature_IN.gif] > <https://www.linkedin.com/company/heremaps> [image: > /Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMail_Signature/_Layout/_Images/20160726_HERE_EMail_Signature_Insta.gif] > <https://www.instagram.com/here/> > > > > HERE Deutschland GmbH, Place of Business: Invalidenstraße 116, 10115 > Berlin, Germany – Commercial Register: Amtsgericht Charlottenburg, HRB > 106443B - USt-IdNr.: DE 812 845 193 - Managing Directors: Michael Bültmann, > Robertus A.J. Houben > > > > This e-mail and any attachments hereto may contain information that is > privileged or confidential, and is intended for use only by the individual > or entity to which it is addressed. Any disclosure, copying or distribution > of the information by anyone else is strictly prohibited. If you have > received this document in error, please notify us promptly by responding to > this e-mail. Thank you. > > > > > > *From:* [email protected] [mailto:spdx-tech-bounces@ > lists.spdx.org] *On Behalf Of *Kate Stewart > *Sent:* Wednesday, November 30, 2016 22:08 > *To:* [email protected] > *Subject:* SPDX Roadmap Ideas for 2017? > > > > Hi, > > If you've got ideas for tools to help people use and adopt SPDX, > please > > feel free to send them out on this email list, or join the general meeting > > tomorrow (see attached). > > > > We've got some ideas, but would like to make sure we're going > > to be focusing on what will be most useful for the communities to > > encourage them to use SPDX. > > > > Thanks, Kate > > > > ---------- Forwarded message ---------- > From: *Phil Odence* <[email protected]> > Date: Tue, Nov 29, 2016 at 5:00 PM > Subject: Thursday SPDX General Meeting > To: "[email protected]" <[email protected]> > > Special Discussion, 2017 Goals- Please bring your thoughts about goals for > next year. After each update, team leads will facilitate some brainstorming > on this subject. The Core Team will finalize and announce formal goal at > the January 5 General Meeting. > > > > > > *GENERAL MEETING* > > > > *Meeting Time:* Thurs, Dec 1, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. > http://www.timeanddate.com/worldclock/converter.html > <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.timeanddate.com%2Fworldclock%2Fconverter.html&data=01%7C01%7C%7Cc238be5a4fb34202d5cc08d41965291b%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=SVO3OwofjT0DUuQ4nVFmirBvg1WCx6N2K3v88rtKLVs%3D&reserved=0> > > > *Conf call dial-in:* > > Join the call: https://www.uberconference.com/katestewart > <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.uberconference.com%2Fkatestewart&data=01%7C01%7C%7Cc238be5a4fb34202d5cc08d41965291b%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=U76TEX9QQLWQmSqaRHHwyqegRnAqZLQS1m%2BSgwNHa%2B0%3D&reserved=0> > > Optional dial in number: 877-297-7470 > > Alternate number: 512-910-4433 > > No PIN needed > > > > *Administrative Agenda* > > Attendance > > Minutes Approval http://wiki.spdx.org/view/General_Meeting/Minutes/2016- > 11-03 > <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.spdx.org%2Fview%2FGeneral_Meeting%2FMinutes%2F2016-11-03&data=01%7C01%7C%7Cc238be5a4fb34202d5cc08d41965291b%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=R7ks5ce4q67OR0Zks%2BS7K4veaqbamMsoDNYKRCAPaM0%3D&reserved=0> > > > > *Technical Team Report – *Kate/Gary > > > > *Legal Team Report* – Jilayne/Paul > > > > *Business Team Report* – Jack > > > > *Cross Functional Issues* – Phil > > > > > > > > > > > > > _______________________________________________ > Spdx mailing list > [email protected] > https://lists.spdx.org/mailman/listinfo/spdx > <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.spdx.org%2Fmailman%2Flistinfo%2Fspdx&data=01%7C01%7C%7Cc238be5a4fb34202d5cc08d41965291b%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=asLcb8jcB2%2BnKP5Rr8AlvQfVGh8uNw7ge1A5EfiSUjs%3D&reserved=0> > > > > > > -- > > Kate Stewart > > Sr. Director of Strategic Programs, The Linux Foundation > > Mobile: +1.512.657.3669 > > Email / Google Talk: [email protected] > > > _______________________________________________ > Spdx-tech mailing list > [email protected] > https://lists.spdx.org/mailman/listinfo/spdx-tech > > > > > > -- > > Jeremiah C. Foster > > GENIVI COMMUNITY MANAGER > > > > Pelagicore AB > > Ekelundsgatan 4, 6tr, SE-411 18 > Gothenburg, Sweden > > M: +1.860.772.9242 <+1%20860-772-9242> > > [email protected] > > -- Jeremiah C. Foster GENIVI COMMUNITY MANAGER Pelagicore AB Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden M: +1.860.772.9242 [email protected]
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
