Nice tutorial! A couple of things stood out for me that may be worthy of more discussion:
"SPDX expressions are case-insensitive, but by convention the operation names should be capitalised." spdx-tools seems to only accept all upper-case operator names, and I had always assumed this was implied by the SPDX specification somehow. However, the specification describes the operators using ABNF syntax, and just reading about this now, it seems that literals in ABNF are case insensitive by default, and need to be prefixed by %s to make them sensitive (https://tools.ietf.org/html/rfc7405). So may be I have misunderstood things all along, and they are case insensitive after all. I think (along with the recent discussion about case sensitivity of license identifiers recently) it would be good to clarify the case sensitivity of operators too in the SPDX specification. And if case insensitivity is intended, then update spdx-tools to cope with this. "Conventionally a SPDX filename has the extension ".spdx" (in either XML or tag-value format)." Using .spdx for both rdf and tag formats makes it slightly harder for tools to tell which format a given file is in. I note that the examples in spdx-tools use extension .rdf for RDF files. I wonder if anyone else uses this .rdf extension too for their spdx files, in which case, is the convention .spdx for tag files and .rdf for RDF files? ________________________________________ From: [email protected] <[email protected]> on behalf of Wheeler, David A <[email protected]> Sent: 21 November 2015 23:57 To: [email protected] Subject: Proposed *SHORT* SPDX tutorial I have created a proposed SHORT tutorial about SPDX: https://github.com/david-a-wheeler/spdx-tutorial/blob/master/README.md It's released under CC-BY-3.0 (same as the SPDX specification). To be effective I think the tutorial needs to be in HTML and very obvious to new visitors to the SPDX website. Is there a conventional filename for package maintainers to use for SPDX files in tag-value format that describe their package? It looks like ".spdx" is a conventional suffix, but I'd like for there to be a single fixed name for a given project (and not "my_project_name.spdx"). Perhaps "LICENSE.spdx"? --- David A. Wheeler _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech ________________________________ -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
