[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DEP5 CANDIDATE parser/editor/validator/migrator is released in libconfig-model-perl



Le Sun, Jan 16, 2011 at 01:17:23PM +0100, Christoph Anton Mitterer a écrit :
> 
> I've also wondered whether it is allowed (or not), when having a Files
> paragraph, that contains the verbatim license (not referring to a
> standalone License tag), e.g.:
> >Files: *
> >License: FOO
> > This is my wonderful license.
> ...to omit the first line synopsis:
> >Files: *
> >License: 
> > This is my wonderful license.
> ... and if so, whether a " " should follow the "License:" or not.

Le Sun, Jan 16, 2011 at 01:19:40PM +0100, Christoph Anton Mitterer a écrit :
> Oh, and I've also would like to see the "X-" on personal license short
> names.

Dear Christoph,

licenses short names that are not specified in the DEP are considered private in
the scope of the document being parsed. This means that FOO, or X-FOO, is not
guaranteed to be the same license in two different copyright files. For that
reason, I think that an X- prefix is not useful.

Also, to reduce complexity of the parsing, it is required to pick a different
short name for each license that is documented in the copyright file. If you
encounter a license that is very rare and has no usual short name, pick one
name that makes sense to you. As explained above, this will not go beyond
the scope of your copyright file anyway.

Would the following change clarify the DEP in regard to your first question ?

--- a/dep5.mdwn
+++ b/dep5.mdwn
@@ -244,8 +244,9 @@ applies to all files and lists all applicable copyrights and licenses.
      alternatives (see *Short names* section for a list of standard 
      abbreviations). If there are licenses present
      in the package without a standard short name, an arbitrary short
-     name may be assigned for these licenses.  These arbitrary names
-     are only guaranteed to be unique within a single copyright file.
+     name must be assigned for these licenses.  These arbitrary names
+     are only guaranteed to refer to the same license within a single
+     copyright file.
    * Remaining lines: if left blank here, the file **must** include
      a stand-alone **`License`** paragraph matching each license short
      name listed on the first line (see the *Standalone License Paragraph*


Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


Reply to: