RE: license expression syntax for exceptions [was: Re: Network connection dropping....]
Hi Philippe, The difference is that an identifier is defined as starting with a letter or digit and this is specified for refs, id and an exception ids. Are you suggesting the current proposed grammar does not sufficiently represent the lexical definition of what a license-id, license-ref and an exception-id should be? At this stage It may be easier to understand what you believe the current proposed grammar does not properly represent and see if we can updated it to make it sufficient. Best, - Mark Mark Gisi | Wind River | Director, IP Open Source Tel (510) 749-2016 | Fax (510) 749-4552 -Original Message- From: spdx-tech-boun...@lists.spdx.org [mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Philippe Ombredanne Sent: Wednesday, April 22, 2015 6:04 AM To: kate.stew...@att.net Cc: spdx-tech@lists.spdx.org Subject: Re: license expression syntax for exceptions [was: Re: Network connection dropping] On Tue, Apr 21, 2015 at 7:12 PM, kate.stew...@att.net wrote: Here is the revised syntax for ABNF, please let us know if there are any concerns. license-id= short form license identifier in Appendix I.1 license-exception-id = short form license exception identifier in Appendix I.2 license-ref = LicenseRef-1*(ALPHA / DIGIT / - / . ) simple-expression = license-id / license-id+ / license-ref compound-expression = 1*(simple-expression / simple-expression WITH license-exception-id / compound-expression AND compound-expression / compound-expression OR compound-expression ) / ( compound-expression ) ) license-expression = 1*1(simple-expression / compound-expression) May I suggest this alternative and slightly different grammar: expression = license / and-expression / or-expression / ( expression ) and-expression = expression AND expression or-expression = expression OR expression license = license-id / license-ref / license-with-exception license-id = identifier[+] ; short form SPDX license identifier with optional + for or later license-ref = LicenseRef-identifier exception-id= identifier ; short form SPDX license exception identifier license-with-exception = (license-id / license-ref) WITH exception-id identifier = alphanum[*(aphanum / punct)] alphanum= ALPHA / DIGIT punct = - / . The difference is that an identifier is defined as starting with a letter or digit and this is specified for refs, id and an exception ids. -- Cordially Philippe Ombredanne ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
Re: license expression syntax for exceptions [was: Re: Network connection dropping....]
On Tue, Apr 21, 2015 at 7:12 PM, kate.stew...@att.net wrote: Here is the revised syntax for ABNF, please let us know if there are any concerns. license-id= short form license identifier in Appendix I.1 license-exception-id = short form license exception identifier in Appendix I.2 license-ref = LicenseRef-1*(ALPHA / DIGIT / - / . ) simple-expression = license-id / license-id+ / license-ref compound-expression = 1*(simple-expression / simple-expression WITH license-exception-id / compound-expression AND compound-expression / compound-expression OR compound-expression ) / ( compound-expression ) ) license-expression = 1*1(simple-expression / compound-expression) May I suggest this alternative and slightly different grammar: expression = license / and-expression / or-expression / ( expression ) and-expression = expression AND expression or-expression = expression OR expression license = license-id / license-ref / license-with-exception license-id = identifier[+] ; short form SPDX license identifier with optional + for or later license-ref = LicenseRef-identifier exception-id= identifier ; short form SPDX license exception identifier license-with-exception = (license-id / license-ref) WITH exception-id identifier = alphanum[*(aphanum / punct)] alphanum= ALPHA / DIGIT punct = - / . The difference is that an identifier is defined as starting with a letter or digit and this is specified for refs, id and an exception ids. -- Cordially Philippe Ombredanne ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
Re: license expression syntax for exceptions [was: Re: Network connection dropping....]
Hi Philippe (and others interested ;-) ) Here is the revised syntax for ABNF, please let us knowif there are any concerns. license-id = short form license identifier in Appendix I.1license-exception-id = short form license exception identifier in Appendix I.2license-ref = LicenseRef-1*(ALPHA / DIGIT / - / . ) simple-expression = license-id / license-id”+” / license-ref compound-expression = 1*(simple-expression / simple-expression WITH license-exception-id / compound-expression “AND compound-expression / compound-expression “OR compound-expression ) / “(“ compound-expression “)” ) license-expression = 1*1(simple-expression / compound-expression) Thanks, Kate On Wednesday, April 15, 2015 1:57 PM, kate.stew...@att.net kate.stew...@att.net wrote: Hi Phillipe, Discussion is around making the ( ) optional around the WITH. Not adding exception keyword - typo on my part there. ;-) Will post the revised version after Mark and I get together on Friday. Kate On Wednesday, April 15, 2015 1:37 PM, Philippe Ombredanne pombreda...@nexb.com wrote: On Tue, Apr 14, 2015 at 7:20 PM, kate.stew...@att.net wrote: Problem point is WITH I don't think we want to force (GPL-2.0+ with bison-exception) but rather GPL-2.0+ with bison exception Sorry if I jump the gun before you posted anything more detailed Did you mean making the parenthesis optional: I would say yes for sure, any expression that is not ambiguous should not require parenthesis. Or did you mean that we should add the word exception as a qualifier as in license-id with license-exception-id exception If so I am not sure this would be warranted. The id for an exception could be anything, but we could have the convention for SPDX-provided exceptions IDs to suffix them with -exception for clarity, though that would not be needed just a nice to have. IMHO adding the keyword exception would be redundant with the with keyword. -- Cordially Philippe Ombredanne ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
license expression syntax for exceptions [was: Re: Network connection dropping....]
On Tue, Apr 14, 2015 at 7:20 PM, kate.stew...@att.net wrote: Problem point is WITH I don't think we want to force (GPL-2.0+ with bison-exception) but rather GPL-2.0+ with bison exception Sorry if I jump the gun before you posted anything more detailed Did you mean making the parenthesis optional: I would say yes for sure, any expression that is not ambiguous should not require parenthesis. Or did you mean that we should add the word exception as a qualifier as in license-id with license-exception-id exception If so I am not sure this would be warranted. The id for an exception could be anything, but we could have the convention for SPDX-provided exceptions IDs to suffix them with -exception for clarity, though that would not be needed just a nice to have. IMHO adding the keyword exception would be redundant with the with keyword. -- Cordially Philippe Ombredanne ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
