-
Notifications
You must be signed in to change notification settings - Fork 2
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
image licensing #1711
base: develop
Are you sure you want to change the base?
image licensing #1711
Conversation
With ECCO, the image was supplied with the source data, as far as I remember. As for Dutch Annual Reports - I must've picked that from an image search for images in the open domain, but if that's not something we can reproduce, probably easier to go with a new image. Perhaps of the Amsterdam Zuidas, so it's more recognizably Dutch? DIOPTRA-L: I suspect that this image was produced by Alex back then, I'll check with Haidee if she knows. The image from JewishMigration / Inscriptions is from before my time. Again, I don't think anyone would be outraged if we picked a different (comparable) image here. For France, I think we can just go for any other image of the same room, too. |
Most image formats have built-in facilities for metadata. I know that in at least two cases (SVG and JPEG), this includes copyright and licensing information. You could use this instead of a separate |
Image metadata has its uses, but putting copyright/licence data exclusively in the metadata makes it kind of invisible in code repositories; github won't display it, nor will most code editors. The fact that such metadata even exists is obscure enough that you apparently felt you needed to explain this. (I guess I would too.) If you thought some of us might not know about this, would you expect that everyone viewing the repository does? The Creative Commons wiki says the same thing:
Many of these files have CC-BY and CC-BY-SA licences, so CC's recommened practices for attribution are relevant here. Though aside from any question of whether file metadata might be sufficient attribution to satisfy licence terms, I think it's also good professional courtesy to make sure attribution is clearly visible. |
I didn't mean to suggest that you should include the copyright and license information only in the metadata and nowhere else. You should definitely mention the fact that some images have separate licenses as well elsewhere, for example in the README (and in the corpus documentation as you suggested). This will alert people to whom it matters to look for those metadata. The metadata are just an alternative for the |
Okay, looking through CC's licence terms and documentation, it does seem to be legally permissible to do it like that, as long as you don't make any edits to the images that would need to be described. (No standard way to do that in metadata, as far as I know.) But even if this is technically and legally possible, why are you suggesting it in the first place? What is the problem with this format? |
More files more clutter. It's just a suggestion though, you can ignore it if you don't like it. |
Dutch Annual Reports: https://commons.wikimedia.org/wiki/File:RotterdamMaasNederland.jpg Would this be suitable replacements? |
Great, thanks for looking into this! I'll add them :) |
Co-Authored-By: Berit <11174072+BeritJanssen@users.noreply.github.com>
This aims to address a few copyright-related issues:
Solution:
*.license
file next to each image in the repository and mention this in the readme.I've added licence info for all corpora where I could find the source of the image. Here is an overview of ones I could not trace: