Skip to content

Publication statement: availability (i.e. licence and copyright) #462

Description

@danbalogh

Within the <publicationStmt> our files (or at least mine) now contain the following code:

            <availability>
               <licence target="https://creativecommons.org/licenses/by/4.0/">
                  <p>This work is licensed under the Creative Commons Attribution 4.0 Unported
              Licence. To view a copy of the licence, visit
              https://creativecommons.org/licenses/by/4.0/ or send a letter to
              Creative Commons, 444 Castro Street, Suite 900, Mountain View,
              California, 94041, USA.</p>
                  <p>Copyright (c) 2019-2025 by Dániel Balogh.</p>
               </licence>
            </availability>

In the Roles, responsibilities... GDoc we have reached the following consensus.

  • the above is to be replaced by <availability><licence target="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</licence></availability> (and nothing else), regardless of what text and what licence was specified in earlier files
  • instead of the hard-coded copyright line, which we discard, a "soft" copyright line shall be generated in the display of editions on dharmalekha

If the PIs are still unanimous on this, we need @michaelnmmeyer to batch replace the existing instances of <availability> as above.

No decision has been reached concerning the content and the manner of generation of the soft copyright line.
If the use of @key on <resp> is finalised (as agreed in the Roles... gdoc and summarised by me in #458), then generation should be quite straightforward: the copyright holders are all of the people listed with <resp key="creator"> in the file. There will always have to be at least one of these, and all of them are expected to have DHARMA id-s, which can be extracted from the file and linked to our participant list. The text could be simply "Copyright © 2019-2026 by {NAME#1}[, {NAME#2}, ... {NAME#n}]." If absolute beauty is desired, then "and" instead of a comma might be used before the last name when there is more than one name.
If the PIs agree on this and @michaelnmmeyer says it is doable, then it needs to be implemented. Otherwise, we need discussion.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions