-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
template v3 and v4 for encoding inscriptions #227
Comments
I suggest that the copyright holder should be the same as the intellectual author of the edition indicated in the
I'm not sure what we should do about translations. In our current setup, the identity of the translator is indicated by a |
has this been completed? i.e., do we have a usable v4 now? I suppose not, since EGD v2 doesn't exist yet. so I am reopening this. |
This issue concerns the general issue of whether we can finally move from using v3 to using v4. (I think the move was delayed because developing v2 of EGD has taken much more time than Axelle foresaw when she created v4.)
A more specific issue is the attribution of copyright.
The current template (v3) states in line 44 of v3:
<!-- replace year and name, use format "Forename1 Surname1 & Forename2 Surname2" or "Forename1 Surname1, Forename2 Surname2 & Forename3 Surname3" if necessary — the copyright is that of the encoder(s) -->
The same is currently still found in line 45 of the unreleased draft of v4.
I have not been following the rule that only the encoder claims copyright, There are many inscriptions mainly encoded by team members X though the editing/translating has been done by X and Y. In such cases, I have myself claimed copyright for X and Y and recommended team members to to the same.
If everyone agrees that it should not always be (only) the encoder who claims copyright, then we need to furnish some suggestions for how else to go about filling in these lines of code. We specifically need to address the question of when the author of a printed edition should be mentioned in the copyright statement.
The text was updated successfully, but these errors were encountered: