On Mon, May 18, 2015 at 08:16:05AM -0700, Gary O'Neall wrote: > Hi Bill, > > Responses inline below. > > Gary > > -----Original Message----- > > From: Bill Schineller [mailto:[email protected]] > > Sent: Monday, May 18, 2015 7:53 AM > > To: Kyle E. Mitchell; Gary O'Neall > > Cc: [email protected]; 'J Lovejoy' > > Subject: Re: JSON version of License List > > > > Hi Kyle, Gary - > > Thanks for collaborating on this. > > If I read correctly from the commit > > > > https://github.com/spdx/tools/commit/dadc9cb90208b1bac956f1c2733e4edcc7 > > ba6e > > 16#diff-f2031d6121946e8907abc588bc6cf800 > > > > > > Whereas the url of current live HTML page is: > > http://spdx.org/licenses/index.html > > > > > > The url of the JSON formatted document will be: > > http://spdx.org/licenses/licenses.json > > > > > > Do I have that correct? > [Gary] > [Gary] Yes - That's the thinking on the URL's.
It would be "cleaner" to do HTTP content negotiation to determine whether to serve HTML or JSON for the index, but frankly that's neither here nor there. I suppose we could serve from `/licenses.json` instead. "Speak now, or forever hold your peace", I suppose. > > I¹d love to get a sneak peek (I¹m too lazy at this moment to build, but > > if I mustŠ) and then if it looks fine (which I¹m sure it will) announce > > its availability. > > > [Gary] Be sure to use the develop branch - still waiting for one more 2.0 > contribution before merging back to master. Gary posted an excerpt from the output here if you'd like to size it up: https://github.com/spdx/tools/pull/2#issuecomment-102659566 > > What was the rationale for selecting just that subset of fields? > > - licenseId, licenseName, isOsiApproved > > > > (e.g. Why not the license text too?) > > Just wondering. Gary and I are both interested in publishing license text templates in JSON format. There is an issue open here: https://github.com/spdx/tools/issues/3 We may need to do some thinking about how best to express fill-in-the-blank fields in the licenses for JSON consumption, since I don't think anyone wants to implement a template parser in every consuming language. I've started a few experiments in that direction, such as this one: https://github.com/jslicense/jslicense-bsd-3-clause/blob/master/license.json Feedback is most welcome. > > > > - Bill > > > > > > On 5/16/15, 3:03 PM, "Kyle E. Mitchell" <[email protected]> wrote: > > > > >Gary, I'd like to take this opportunity to thank you on the list for > > >being so incredibly helpful and responsive this week. I know it was a > > >busy one for you even before I started pestering you on GitHub. > > Thanks! > > > > > >The group might also like to know that the patch for JSON publication > > >grew out of a proposal to bring license identifier validation to the > > >RubyGems package manager. The maintainers were very receptive to using > > >validation warnings to standardize license strings in their > > repository, > > >but wanted an automatic way to keep the list of valid identifiers > > >up-to-date. The new JSON license IDs list makes that trivial, and I'm > > >sure other open-source package managers, like npm, will also use it. > > > > > >I imagine these could seem like trivial steps, given how much more > > >there is to SPDX than the license list. (npm, for the record, is using > > >license expressions, too.) But I think the size and growth rates of > > the > > >repositories make identifier validation a particularly high-leverage > > >use of the team's hard work. > > > > > >Best, > > >Kyle > > > > > >On Sat, May 16, 2015 at 11:27:08AM -0700, Gary O'Neall wrote: > > >> Greetings all, > > >> > > >> Thanks to Kyle Mitchell, the SPDX tools now has the capability to > > >>publish a JSON version of the license list (something that has been > > >>requested for some time). > > >> > > >> Kyle's contribution has been merged into the tool and attached is > > the > > >> output. > > >> > > >> It contains a subset (but a valuable subset) of the license list > > >>properties > > >> - licenseId, licenseName, isOsiApproved. > > >> > > >> I would like to publish this on the spdx.org/licenses website if no > > >> one objects. > > >> > > >> Since this built into the tools, every release of the license list > > >> will automatically update the licenses.json file. > > >> > > >> We could do this "silently" if we want to give some time for > > feedback > > >>or we could make its availability more public if we are comfortable > > >>with the format (I'm in favor of the latter). > > >> > > >> Let me know what you think We can also discuss on Tuesday's call. > > >> > > >> Thanks, > > >> > > >> Gary > > >> > > >> ------------------------------------------------- > > >> Gary O'Neall > > >> Principal Consultant > > >> Source Auditor Inc. > > >> Mobile: 408.805.0586 > > >> Email: <mailto:[email protected]> [email protected] > > >> > > > > > >-- > > >Kyle Mitchell, attorney > > >San Francisco, California > > >+1 (415) 864 - 9913 > > >_______________________________________________ > > >Spdx-tech mailing list > > >[email protected] > > >https://lists.spdx.org/mailman/listinfo/spdx-tech > -- Kyle Mitchell, attorney San Francisco, California +1 (415) 864 - 9913 _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
