Just to be clear – RDFa is only used to read the license list, which is published online in RDFa form (https://spdx.org/licenses/). It’s already an action item for 2017 to enable content negotiation to get the plain RDF, rather than RDFa (RDF embedded into HTML).
This will eliminate the need for the RDFa library. The nice thing about RDF is that it’s a W3C standard, which comes with tooling on all platforms and a W3C standard query language. There’s room for discussion on JSON representation, for instance, whether to go with JSON-LD or RDF/JSON<https://www.w3.org/TR/rdf-json/>. Because RDF/JSON is an exact mapping/serialization of RDF, it’s something we can produce at any moment with no new spec required. The same goes for the Turtle<https://www.w3.org/TeamSubmission/turtle/> format, which you may find even more readable than JSON and which has very broad support. Here’s<https://www.w3.org/2013/dwbp/wiki/RDF_AND_JSON-LD_UseCases#Differences_with_RDF> summary of the differences between the two. I’m slightly concerned that the use of JSON native types in JSON-LD could produce documents not convertible to RDF. From: <[email protected]> on behalf of "Schuberth, Sebastian" <[email protected]> Date: Monday, December 12, 2016 at 10:50 AM To: Gary O'Neall <[email protected]>, 'Jeremiah Foster' <[email protected]> Cc: "[email protected]" <[email protected]>, "Steenbergen, Thomas" <[email protected]> Subject: RE: SPDX Roadmap Ideas for 2017? FYI, Yev already seems to have put some effort into storing SPDX in JSON-LD [1]. Personally, I also find JSON much easier to read and parse than RDF. Also, the RDF-A library [2] used by the SPDX tooling seems to be pretty much a dead project. So maybe consider whether dropping RDF-A in favor of JSON-LD is an option? [1] https://github.com/yevster/spdxtra [2] https://github.com/shellac/java-rdfa/ Regards, Sebastian From: [email protected] [mailto:[email protected]] Sent: Friday, December 9, 2016 19:20 To: 'Jeremiah Foster' <[email protected]>; Schuberth, Sebastian <[email protected]> Cc: [email protected]; Steenbergen, Thomas <[email protected]> Subject: RE: SPDX Roadmap Ideas for 2017? 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<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspdx%2Flicense-list-data%2Ftree%2Fmaster%2Fjson&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=e5u6tLPXxDBg%2BkCjfcPM5vYNsD2B%2B9cqp%2Br5eHFJhfg%3D&reserved=0> or on the website https://spdx.org/licenses/licenses.json<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fspdx.org%2Flicenses%2Flicenses.json&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=S6RITzcNw90Bgs2rhkxgmXEAL%2Bf9Z8txKDnpwLQXEq8%3D&reserved=0>). 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:[email protected]> [mailto:[email protected]] On Behalf Of Jeremiah Foster Sent: Thursday, December 8, 2016 11:27 AM To: Schuberth, Sebastian Cc: [email protected]<mailto:[email protected]>; Steenbergen, Thomas Subject: Re: SPDX Roadmap Ideas for 2017? On Mon, Dec 5, 2016 at 3:17 AM, Schuberth, Sebastian <[email protected]<mailto:[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<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspdx%2Ftools%23spdx-format-converters&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=RJOPUVyYyTUN8tBAlQLyxxf%2F%2Bb%2B3Y4IwiaFu2G%2B7WVk%3D&reserved=0> [2] http://lint.travis-ci.org/<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flint.travis-ci.org%2F&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=il28XrjooF92G5xPNVNcXmyZpiwPtLxOovxPEW2siBI%3D&reserved=0> [acintosh HD:Users:jerchow:Downloads:Asset_Package_01_160721:HERE_Logo_2016:sR] 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 [Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMa]<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F360.here.com%2F&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=TK%2FJNy3%2B0nyDF8YvXIL%2FjpzVPzSJmKaLKkhCq9lASmk%3D&reserved=0> [Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMa] <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitter.com%2Fhere&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=Cfh9pk8KxT2qqTmv6maZMdYu70TkidHaxFDLcTFCUTs%3D&reserved=0> [Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMa] <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fhere&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=uhz1cnLwowXbc1FWEH61Cy3JC5ZK3dGhqGbFFOvWMTI%3D&reserved=0> [Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMa] <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fheremaps&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=xX8ArbYxQ1L%2BfyK5Pxv5HYi9aB1LX2DY3nw%2FRS%2FMvII%3D&reserved=0> [Users/nussbaum/_WORK/PROJECTS/20160726_HERE_EMa] <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.instagram.com%2Fhere%2F&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=jwFZ0tCBAn7jSwrOtZUqcgo%2FYwlGe51GYc7JF1hjTLI%3D&reserved=0> 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:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kate Stewart Sent: Wednesday, November 30, 2016 22:08 To: [email protected]<mailto:[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]<mailto:[email protected]>> Date: Tue, Nov 29, 2016 at 5:00 PM Subject: Thursday SPDX General Meeting To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[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<tel:877-297-7470> Alternate number: 512-910-4433<tel: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]<mailto:[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<tel:%2B1.512.657.3669> Email / Google Talk: [email protected]<mailto:[email protected]> _______________________________________________ Spdx-tech mailing list [email protected]<mailto:[email protected]> https://lists.spdx.org/mailman/listinfo/spdx-tech<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.spdx.org%2Fmailman%2Flistinfo%2Fspdx-tech&data=01%7C01%7C%7C77e4ab1267ee46e4069e08d420600101%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=PihqKWMcQU0ATQmE%2FccTn5WN7RWsPKaNazhqpxtXMas%3D&reserved=0> -- Jeremiah C. Foster GENIVI COMMUNITY MANAGER Pelagicore AB Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden M: +1.860.772.9242 [email protected]<mailto:[email protected]> [cid:[email protected]]
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
