Commons:Village pump/Copyright

From Wikimedia Commons, the free media repository
Jump to: navigation, search


  Welcome to Commons   Community Portal   Help Desk
Upload help
  Village Pump
copyright • proposals
  Administrators' Noticeboard
vandalism • user problems • blocks and protections
 
↓ Skip to table of contents ↓       ↓ Skip to discussions ↓
Shortcut: COM:VPC· COM:VPCOPY
Welcome to the Village pump copyright section

This Wikimedia Commons page is used for general discussions relating to copyright and license issues, and for discussions relating to specific files' copyright issues. Discussions relating to specific copyright policies should take place on the talk page of the policy, but may be advertised here. Recent sections with no replies for 7 days may be archived; for old discussions, see the archives.

Please note
  1. If you want to ask why unfree/non-commercial material is not allowed at Wikimedia Commons or if you want to suggest that allowing it would be a good thing please do not comment here. It is a waste of your time. One of Wikimedia Commons' basic principles is: "Only free content is allowed." This is just a basic rule of the place, as inherent as the NPOV requirement on all Wikipedias.
  2. Have you read the FAQ?
  3. Any answers you receive here are not legal advice and the responder cannot be held liable for them. If you have legal questions, we can try to help but our answers cannot replace those of a qualified professional (i.e. a lawyer).
  4. Your question will be answered here; please check back regularly. Please do not leave your email address or other contact information, as this page is widely visible across the Internet and you are liable to receive spam.
Purposes which do not meet the scope of this page
Commons discussion pages (index)


  • Please do not make deletion requests here – instead, use the relevant process for it.
 

Propose to update CC license tags to comply with the new wordings in CC deeds[edit]

I'm proposing this matter here per the advice of ChrisiPK at AN.

As we all know, CC had updated all of their license deeds after the release of CC 4.0 licenses. It is to educate the licensees (and licensors too) about the legal terms by highlighting them more promptly. And, we can see some terms like "remix", "work", "file" are not perfectly conveying the copyright terms. So CC changed them to "adapt", "material" to satisfy all types of works, means and medium we are using.

There is also a warning about the third party rights (like publicity, privacy and moral rights) that may limit the reuse. Our current practice is to add specific tags on individual files, which is time consuming and not perfect as we can't check all files.

Ref:

Marking your work with a CC license "Example: Image"
Choose a license
Best practices for attribution
Best Practices for Creative Commons attributions
Creative Commons Attribution For Photos

So I propose to update the layout templates:

Existing Proposed
This file is licensed under the Creative Commons <license name with link to deed> license. "Foo" <title of the work with link to URI> by Real name (www.example.com) <attribution parameter provided in author field with a link to user page> is licensed under a <license name with link to deed> license.
You are free: You are free to:
to share - to copy, distribute and transmit the work Share — copy and redistribute the material in any medium or format
to remix – to adapt the work Adapt — remix, transform, and build upon the material
Under the following conditions: Under the following terms:
attribution – You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
share alike – If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Notices:
No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license (link to legal code) before using the licensed material.

Current tag (CC BY lacks the ShareAlike clause):

w:en:Creative Commons
attribution share alike
This file is licensed under the Creative Commons Attribution-Share Alike 4.0 International license.
Attribution: Real name (www.example.com)
You are free:
  • to share – to copy, distribute and transmit the work
  • to remix – to adapt the work
Under the following conditions:
  • attribution – You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
  • share alike – If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

Option 1 Proposed tag (CC BY lacks the ShareAlike clause):

Cc primary srr.gif
By large.png Sa large.png
"Foo" by Real name (www.example.com) is licensed under a Creative Commons Attribution-ShareAlike 4.0 International license.
You are free to:
  • Share — copy and redistribute the material in any medium or format
  • Adapt — remix, transform, and build upon the material
Under the following terms:
  • Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  • ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
  • No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Notices:
  • No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
  • This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.



Option 2 Proposed tag including all terms in the deed as suggested below (CC BY lacks the ShareAlike clause):

Cc primary srr.gif
By large.png Sa large.png
"Foo" by Real name (www.example.com) is licensed under a Creative Commons Attribution-ShareAlike 4.0 International license.
You are free to:
  • Share — copy and redistribute the material in any medium or format
  • Adapt — remix, transform, and build upon the material
for any purpose, even commercially.
The licensor cannot revoke these freedoms as long as you follow the license terms.
Under the following terms:
  • Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  • ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
  • No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Notices:
  • You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
  • No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
  • This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.


Option 3 Proposed tag without a "title" (CC BY lacks the ShareAlike clause):

Cc primary srr.gif
By large.png Sa large.png
This work by Real name (www.example.com) is licensed under a Creative Commons Attribution-ShareAlike 4.0 International license. Permissions beyond the scope of this license may be available here.
You are free to:
  • Share — copy and redistribute the material in any medium or format
  • Adapt — remix, transform, and build upon the material
for any purpose, even commercially.
The licensor cannot revoke these freedoms as long as you follow the license terms.
Under the following terms:
  • Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  • ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
  • No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Notices:
  • You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
  • No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
  • This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Option 4 Proposed tag (CC BY lacks the ShareAlike clause):

Cc primary srr.gif
By large.png Sa large.png
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license.
Attribution: Real name (www.example.com)
You are free to:
  • Share — copy and redistribute the material in any medium or format
  • Adapt — remix, transform, and build upon the material
Under the following terms:
  • Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  • ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.

Option 5 Proposed tag (CC BY lacks the ShareAlike icon):

Cc primary srr.gif
By large.png Sa large.png
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license.
Attribution: Real name (www.example.com)

Option 6 Proposed tag without a "title" (CC BY lacks the ShareAlike clause):

Cc primary srr.gif
By large.png Sa large.png
This media by Real name (www.example.com) is licensed under a Creative Commons Attribution-ShareAlike 4.0 International license.
You are free to:
  • Share — copy and redistribute the material in any medium or format
  • Adapt — remix, transform, and build upon the material
for any purpose, even commercially.
The licensor cannot revoke these freedoms as long as you follow the license terms.
Under the following terms:
  • Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  • ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
  • No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

Votes[edit]

  • Symbol support vote.svg Support Option 4 or 3. Jee 07:05, 3 July 2014 (UTC) Option 6 considering new suggestions. The layout, design, colours, icons, etc. can be changed/improved. I'm only concerned about the wordings. Jee 02:35, 12 July 2014 (UTC)
  • Symbol support vote.svg Support option 4 or 2. --Graphium 15:26, 3 July 2014 (UTC)
  • Symbol support vote.svg Support option 3 and 4.    FDMS  4    14:16, 10 July 2014 (UTC)Time2wait.svg On hold
  • Pictogram voting question-blue.svg Request Please wait as we are waiting for the WMF input (see below). Jee 15:54, 10 July 2014 (UTC) See the WMF input below. Jee 07:58, 11 July 2014 (UTC)

Discussion[edit]

Welcome to any suggestions. Jee 07:40, 8 June 2014 (UTC)

The layout of this proposal is confusing, it took me a few minutes to work out that this was a "from existing text" to "new text" proposal with them side by side. Adding to the confusion is that this appears to be trying to do all variations of Commons allowed CC licences in one go. I suggest the "from" and "to" texts are side by side in a wiki table and that each licence, or each licence component in CC0, CC-BY, CC-BY-SA are made clear rather than bundling. To go the extra mile, I suggest creating the new draft licences in a sandbox and linking to them here, so that the end result can be seen as it will appear on an image page. -- (talk) 08:21, 8 June 2014 (UTC)
Those license tags are so complicated; so difficult to understand for an ordinary volunteer. Probably Multichill can help. All tags of version 1.0 to 4.0 except CC 0 use that same components. CC BY doesn't use the "ShareAlike" part. I didn't look on NC as it is out of my interest. Will try to improve the presentation. Jee 08:33, 8 June 2014 (UTC)
@: Hope ✓ Done. Jee 09:42, 8 June 2014 (UTC)
I don't like the bolding of the links in the explanations …    FDMS  4    18:17, 8 June 2014 (UTC)
Bolding can be avoided if links can be highlighted by a separate color or any other means. Jee 02:41, 9 June 2014 (UTC)
Links are generally highlighted in blue …    FDMS  4    08:03, 9 June 2014 (UTC)
I would clearly prefer to use a more grammatically correct presentation (like Wikimedia Commons does currently) than a BuzzImportantWordInCamelCase (like ShareAlike) terminology (like the new proposal offer to uniformize with Creative Commons text). --Dereckson (talk) 20:14, 8 June 2014 (UTC)
Use of separate words than in the legal code will affect the legal validity in case of disputes. Jee 02:41, 9 June 2014 (UTC)

I just noticed that the links in the icons on the current tags are not working. It seems link= only works if full URI is provided. Jee 03:53, 9 June 2014 (UTC)

This looks like a useful improvement and brings our CC4 template in line with their deed.

  • I'm not clear how the ""Foo" by Real name (www.example.com) " bit works. Could someone give examples for Commons-sourced files and perhaps indicate if e.g., Flickr-sourced files would be done differently.
  • I like how "This file is licenced" has been dropped since CC have admitted they don't consider any of their licences to be file-based [something to consider changing in earlier templates too, but that's for another day].
  • I don't think the "You are free to" or "Under the following terms" should be in bold, nor the links.
  • I think "Notices" should better be titled "Caveats", since that's what they are.
  • The "No warranties are given" sentence should best link to the Commons:General disclaimer.
  • The CC4 deed also has "for any purpose, even commercially." and "The licensor cannot revoke these freedoms as long as you follow the license terms". These are both important points and I don't see why we should miss them out.
  • I don't see why our "deed", if that is what this is, needs to link to CC's deed in the word "deed". It is just confusing to read "This dead" which contains a link to something else. Since ours is nearly the same, we've made theirs redundant and so re-users would be best jumping straight to the full licence text.

-- Colin (talk) 07:21, 9 June 2014 (UTC)

  • @Colin: Thanks for the review.
  • 1. "Foo" by Real name (www.example.com) is licensed under Creative Commons Attribution-ShareAlike 4.0 International license.
I had spend a lot of time to understand the "marking" and "attributing" procedure. "A good rule of thumb is to use the acronym TASL, which stands for Title, Author, Source, License." It covers all the necessary information for attributing a licensed material (work). I understand your question as "original source" of third party uploads are different. In that case we may consider to add the source parameter too as in the Media Viewer. Then it will look like "Foo" by Real name (www.example.com) (Own work/external source) is licensed under Creative Commons Attribution-ShareAlike 4.0 International license.
Note that we try to provide attribution parameters through various ways (Creditline, attribution= in license tag, etc. But I noticed that external sites like eol.org only look into the author= field in Commons.)
  • 2. This update will affect all CC tags except CC 0 as this edit request is on Template:CC-Layout.
  • 3 Done.
  • 4 Considerable if enough consensus (I'm not a native English speaker).
  • 5 Done.
  • 6 Considerable if enough consensus
  • 7 Done. Jee 09:18, 9 June 2014 (UTC)
On point 1, I still don't understand and need an example. Since this is a generated template, where would one get "Real name" or "www.example.com" from. Please can you give a few examples from real Commons images. -- Colin (talk) 11:31, 9 June 2014 (UTC)
@Colin: Sure; you can see here how I provide attribution to the POTY winners.
1. Real name is given.
2. Only user name given.
4. Flickr user name, Flickr source, and name of adapter provided.
5 & 8. Real name with website link provided.
The template only need to look into author (and source for not {{own}} if needed). Jee 14:03, 9 June 2014 (UTC)
Symbol support vote.svg Support the text of {{Cc-by-4.0}} should match https://creativecommons.org/licenses/by/4.0/deed.en. I did not check word by word the match of the proposed text with creativecommons.org version but it should be close. The same goes with all the translations already done by CC. One concern I have is with "Foo": most photographs do not have titles and we should not expect people to title them, but should allow someone to add title if desired. I would also like to keep the suggested attribution part as a separate field. Incorporating it into sentence will cause trouble as people can put all kind of nonsense there making the sentence incomprehensible. Current approach isolates injected text so it is less of an issue. We should probably update Commons:Credit line. --Jarekt (talk) 16:19, 9 June 2014 (UTC)
@Jarekt: Thanks.
"Foo" is "file name without extensions" as followed in Media Viewer. If it is not practical, we can satisfy with "This Licensed Material".
"Incorporating it into sentence" is the "preferred" way suggested by CC in Best practices for attribution.
The second option is "Attribution: Photo by Example / CC BY-SA" as a second line as in current template. But the current problem is we only (most people) provide attribution as "author name" only. It gives the re user a false idea that only author name is required as attribution. In fact, attribution requires Title (optional), Author, Source, License. Jee 17:18, 9 June 2014 (UTC)
I agree that the "attribution" statement might be misleading as it often only mentions author. Maybe we should update and expand Commons:Credit line and link to it (we might want to also rename it to something like Commons:License attribution). I do not think filename and title are equivalent: our filenames can be up to 240 bytes long and the only requirement are that they are unique. Many were chosen not by authors but by the uploaders, for example in case of flickr images (like all files here) --Jarekt (talk) 19:25, 9 June 2014 (UTC)
I understand; and wonder how Media viewer handle this: <p><a href="https://commons.wikimedia.org/wiki/File:Areca_catechu_nuts_at_Kadavoor.jpg#mediaviewer/File:Areca_catechu_nuts_at_Kadavoor.jpg"><img src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Areca_catechu_nuts_at_Kadavoor.jpg" alt="Areca catechu nuts at Kadavoor.jpg" height="480" width="360"></a><br>"<a href="https://commons.wikimedia.org/wiki/File:Areca_catechu_nuts_at_Kadavoor.jpg#mediaviewer/File:Areca_catechu_nuts_at_Kadavoor.jpg">Areca catechu nuts at Kadavoor</a>" by <a href="//commons.wikimedia.org/wiki/User:Jkadavoor" title="User:Jkadavoor">Jeevan Jose, Kerala, India</a> - <span class="int-own-work">Own work</span>. Licensed under <a href="http://creativecommons.org/licenses/by-sa/4.0" title="Creative Commons Attribution-Share Alike 4.0">CC BY-SA 4.0</a> via <a href="//commons.wikimedia.org/wiki/">Wikimedia Commons</a>.</p> displays "Areca catechu nuts at Kadavoor" by Jeevan Jose, Kerala, India - Own work. Licensed under CC BY-SA 4.0 via Wikimedia Commons.
Note that we need "title" or a word like "Photo" or "Media" at least to link it to the source. Further not that, according to CC this attribution may not be immediate visibility under the use. It can be in page footer, tail page of a book, or in a "credit page" especially created for that purpose alone in a website. In such cases, a meaningful tittle explains the media is the only way to associate them together. Jee 02:25, 10 June 2014 (UTC)

I got the ping. I still had this somewhere on my list. My main concern is that it's going to become some massive bulky template. The first prototype doesn't look promising at all. We should focus on getting a slick small template, not trying to teach copyright in a template. I'm inviting some of the WMF legal and design people to pitch in. Multichill (talk) 19:57, 9 June 2014 (UTC)

I'm aware of it. But my opposing arguments are:
If we use a small template just covering the first line, people use their own templates to convey the remaining parts.
We our self applying {{Personality}}, {{Trademarked}}, {{Consent}}, etc. in selected works with makes the page more bulky than this. Further, that practice is not perfect as we can't filter all such files easily from our collection.
I think educating people is more important than limiting the page size; if it leads to misuse, thus makes damage to our potential contributors.
I agree with you that sound review by a legal team is necessary before applying the change. I think Media Viewer team can help us. Pinging Keegan (WMF). Jee 02:40, 10 June 2014 (UTC)
Thanks for the ping, Jee. I'll have to read up on this and see how I can help pass it along, and to which part of the WMF, if appropriate. Pesky note: it's the Multimedia team ;) Keegan (WMF) (talk) 08:40, 12 June 2014 (UTC)
Thanks Keegan (WMF). I know you're not from the legal but hope you get enough support from them. And it will be nice if the attribution requirement is provided in the same way in the "file page" and "Media Viewer". Otherwise it will add another confusion and annoying too. :)
What is your (team) opinion about "title" = "file name without extension"? It will be nice if we can add an extra field title= in {{information}}. But we already have so many files. So I think adding it now is difficult? Jee 09:15, 12 June 2014 (UTC)
@Jkadavoor:: The Multimedia team opinion is that adding these fields isn't difficult, you can use a bot or a Lua module to take care of it. In the long run, looking at Wikidata integration, it might even be beneficial. Structured data=good data. So yeah, go for it if the community agrees. No problem from this end. As for the legal aspect, I've passed that along for someone else to look at since it's outside my purview. HTH. Keegan (WMF) (talk) 18:06, 12 June 2014 (UTC)
Thanks Keegan (WMF); this is interesting. I think adding such a field to {{Information}} will be a great improvement. May be a bot can set the default value for all existing files as "file name without extension" so that authors can change it later if they wish so. @Jarekt:, Multichill, Jean-Frédéric... what do you think? ({{Specimen}}, etc. based on Photograph template have already has a field "title"; so it can be used.) Jee 02:07, 13 June 2014 (UTC)
Many Artworks and artistic photographs have official titles, snapshots do not. As an uploader of a lot of photographs I think it would be pointless to title them and using a filename sounds like even worse idea: filenames were not designed to be titles they are only supposed to be unique. Welived for so long without titles for our photos why do we need them now? If I want a title to be mentioned in my cc license I will add it to the attribution string, since that what it was designed to do. Also you can always use {{Artwork}} or {{Photograph}} template if you need that field. But even there people are encouraged to use {{Title}} template or templates like Category:Multilingual tags: Title, which can be hard to fit in an attribution field. --Jarekt (talk) 02:59, 13 June 2014 (UTC)
Jarekt: But how then people can specify source in the attribution? There is no need of a word if the image is hyper linked in a website or attribution is mentioned near the use. But it is not applicable for all cases. See, an e-book is published with 100 photos from Commons and attribution is provided altogether in the last page. Then it is better if we can "Common Lime Butterfly Papilio demoleus by Kadavoor" by Jeevan Jose...., "Acmella ciliata by Kadavoor" by Jeevan Jose...., etc than "Photo" by Jeevan Jose...., "Photo" by Jeevan Jose...., etc. It will be far better if we can mention better titles than "file names". ("Papilio demoleus at Kadavoor" is better).
If it is a paperback book, title is more meaningful. See "Common Lime Butterfly Papilio demoleus by Kadavoor" (Source: https://commons.wikimedia.org/wiki/File:Common_Lime_Butterfly_Papilio_demoleus_by_Kadavoor.JPG) by Jeevan Jose...., "Acmella ciliata by Kadavoor" (Source:https://commons.wikimedia.org/wiki/File:Acmella_ciliata_by_Kadavoor.jpg) by Jeevan Jose.... Jee 03:19, 13 June 2014 (UTC)
But not everybody names their files that way. I always try to concatenate few fields: a place or source, subject or species, and some number to make it unique. Others pick names differently like for example File:I got my Honda Accord 1990 4 door 4 cylinder power windows power door lock run good engine and transmission good 120,000 miles do you want to contact me text me or call me 8608406395- 2014-05-28 20-07.jpg --Jarekt (talk) 13:51, 13 June 2014 (UTC)
Jarekt, I understand; and some file names by bots are also very lengthy. So what about picking title from {{credit line}} if provided, else from {{Title}} if provided, else use file name without extension as a compromise? (BTW, that example is com:ADVERT and need to be renamed. :)) Jee 14:37, 13 June 2014 (UTC)
I am fine with picking titles from license attribution string, {{credit line}} or {{Title}}, but if those are not provided than I would assume the uploader did not wish to title his/her images, like I do not care about titles in all the images I uploded over the years. Creating default titles for others would need to be a bot job and I doubt it would be approved. But we can offer a service where people that want titles can request for them to be added to their files. --Jarekt (talk) 14:53, 13 June 2014 (UTC)
Jarekt: Then what about using a word like "media" to link to the source if no {{credit line}} or {{Title}}? The Media Viwers also need to to updated; as it is now using file name as title. I think they did it on the advice of Legal. So we need to consult them (legal) too? Jee 15:14, 13 June 2014 (UTC)
The Media Viwer is not suggesting attribution strings. I do not see any problem with it. I also do not see how is it related to the discussion about a license template. --Jarekt (talk) 15:45, 13 June 2014 (UTC)
Jarekt: See this discussion. Media Viewer or any other third party automated tools need to pick the license and attribution string properly from our tags. A manual user can pick it even from data scattered in various locations. Jee 16:00, 13 June 2014 (UTC)
Jarekt: While experimenting with [1], I found another option without title: "This work by <author name with url> is licensed under a <License name with url>. Permissions beyond the scope of this license may be available at <source url>". Can we proceed this way? See Option 3. Jee 09:34, 14 June 2014 (UTC)
  • Symbol support vote.svg Support the changes, but it would be good to include the "Licensor cannot revoke the licence" part in all the deeds here, and the CC Some Rights Reserved image on the left would look better using the version on our current commons deeds. --Graphium 07:16, 10 June 2014 (UTC)
  • @Graphium: I included an example showing those information too. Regarding logo, they are a collection of three separate logos; will change automatically in the layout template to match with the license used. (eg: CC BY, CC BY-SA, etc.). Regarding the design, see http://creativecommons.org/policies#license. It should be a "double C in a circle". Jee 03:08, 12 June 2014 (UTC)
  • @Jkadavoor: Ok noted. Just adding one more suggestion. There should be a spacing between the "CC Some Rights Reserved" logo and the "Attribution" and/or "ShareAlike" buttons. The template appears better that way IMO. --Graphium 05:32, 12 June 2014 (UTC)
  • Hope the alignment problem will be solved by the code experts while implementing. Jee 06:09, 12 June 2014 (UTC)
  • Pictogram voting comment.svg Comment As far as I know, the CC-licenses also require the re-user to name the license the work is made available under. That's something we have always neglected for reasons I don't remember, but this seems like a good opportunity to re-think the issue and maybe put an additional notice into the templates. --El Grafo (talk) 08:50, 10 June 2014 (UTC)
  • El Grafo, I think it is well mentioned under the "appropriate credit" link. There is some more conditions for adaptations of BY-SA licenses. They are mentioned under "same license". Jee 14:28, 11 June 2014 (UTC)
  • Thanks, Jee, I must admit I didn't notice that when I first looked through the proposal. All in all, it looks very reasonable to me. Are the wiki pages linked in the new template available in other languages than english? Couldn't find any direct links there … --El Grafo (talk) 15:03, 11 June 2014 (UTC)
  • Noted; will look into it. Thanks. Jee 15:07, 11 June 2014 (UTC)
  • Any news on that? If there are no translations of that, we should think about other ways to make sure people know they have to name the license. (I think that's a very important part that has been neglected far too long). --El Grafo (talk) 09:28, 10 July 2014 (UTC)
  • Pictogram voting comment.svg Comment I like the approach this is taking and have promoted these changes in the past. Our license templates should at a minimum contain all the things the relevent CC Deed does. BTW, the word Notices is bolded and need not be to create a common format. Otherwise bold the other section headings. When there is a final version it should be put up for a !Vote, not yet while discussion ensues. Saffron Blaze (talk) 15:54, 10 June 2014 (UTC)
  • Oops; I forgot it while correcting per Colin. Jee 14:36, 11 June 2014 (UTC)
  • Pictogram voting comment.svg Comment Fix the English please. "Foo" by Real name (www.example.com) is licensed under Creative Commons Attribution-ShareAlike 4.0 International license. --> "Foo" by Real name (www.example.com) is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license. --Graphium 16:13, 10 June 2014 (UTC)
    There no "the" at CreativeCommonsWiki:Best practices for attribution or in the attribution link generated by Media Viewer. So I doubt with is the best English style. Jee 14:31, 11 June 2014 (UTC)
    That's because they never spell out the full name with "License" at the end. "the" is required here for style reasons, without it it sounds clumsy. Regards, --ChrisiPK (Talk|Contribs) 09:19, 12 June 2014 (UTC)
    Thanks ChrisiPK, I re checked and found that they use a whenever full name is spelled. They use "License" and "license". So the or a? Jee 09:30, 12 June 2014 (UTC)
    @Jkadavoor: It would be good to follow what CC uses, which in this case is "a". However English-wise I think "the" is more appropriate. Let's wait for Chris' input. --Graphium 09:42, 12 June 2014 (UTC)

I added a second example covering all CC terms in the deed. Note that I included the "exception" clause too under "notices". Jee 15:05, 11 June 2014 (UTC)

The advice of the legal team is requested, and LuisV (WMF) offered to help. Jee 06:27, 17 June 2014 (UTC)

  • Files on Flickr have a headline and a description. The headline could arguably be a title, but is sometimes something useless such as "IMG1234.JPG". Should we interpret it as a title? --Stefan4 (talk) 00:08, 1 July 2014 (UTC)
  • Be careful with how you use words such as "material" and "work" and how you name the rights holder. They have different definitions, and if the licence uses a different word than the template proposals above, this could have strange results in court. For example, the Swedish copyright law provides protection to the following kinds of material:
Kind of material Rights holder Explanation
Works Author A work is something which meets certain quality requirements, see COM:TOO. Parts of the quality requirements come from the notion that a work must be "created", and parts of them come from the word "work" itself. Split in two groups: "artworks" and "literary works", with different degrees of protection.
Performances Performing artist Only performances of literary works are protected, see "works" above. The performance itself doesn't need to meet any quality requirements. On Commons, this should only affect sound and video files.
Sound and video recordings Producer No quality requirements needed, but protection is only given to the first fixation. Mere duplication doesn't reset the term. Some recordings are also protected as works and/or performances.
Catalogues et cetera Producer See w:Database Directive.
Photographic images Producer It must be a photograph and it must be an image. Some photographs are also protected as works. No quality requirements needed, but it seems that only new photographic images are protected and that new copies of existing photographic images aren't separately protected. Strange applications of COM:DW, see e.g. NJA 1989 p. 315 (drawings based on photographs weren't copyright violations). Single frames in films count as photographs if created using a camera.

Stefan4 (talk) 00:08, 1 July 2014 (UTC)

Thanks Stefan4. My understanding form the previous discussions with CC community is that they changed the word "Work" to "Licensed Material" to accommodate databases. (See [2], [3]).) They replaced the word in almost every places; but still using "work" in marking guides. I don't know whether it is an unnoticed error or not. I can see many such errors (like license text changed to CC BY 4.0; but links till to CC BY 3.0) in their sites. Reported to them; but doesn't get any reply so far. Jee 02:44, 1 July 2014 (UTC)
Yes, different versions of CC licences use different words. Use the word "work" in the templates for licences which license works, and use the word "material" in the templates for licences which license material. --Stefan4 (talk) 15:52, 1 July 2014 (UTC)
@Stefan4: But they (CC) changed the word "work" to "material" in all of their deeds, even in CC BY-SA 1.0. We need not compelled to follow them; but I wonder what they mean by such changes. Jee 17:05, 1 July 2014 (UTC)
That's strange. We should try to figure out why they did this. --Stefan4 (talk) 20:20, 1 July 2014 (UTC)
I believe the intent was to have a more generic term that would not depend on what is used in a specific jurisdiction, so that the license would be more robust across national boundaries and types of material. "work" can still be found in the body of the license itself, as part of the definition of "Licensed Material" in 4.0: "the artistic or literary work, database, or other material to which the Licensor applied this Public License".
I'm not sure I would have made this change to the older deeds, but it is important to keep in mind that in the situations where the work/material distinction is legally important, the legal code, not the deed, is likely to be what is getting read/interpreted. So being consistent and easy-to-understand is arguably more important than being legally precise in this particular situation. —Luis Villa (WMF) (talk) 00:37, 11 July 2014 (UTC)
By the way, with smart templates we could avoid this problem by saying "image", "video", "recording", etc. (depending on mimetype) instead of "work" or "material". This would be more clear for most non-lawyer users and not bother the lawyers (since they'd read the full license anyway). CC is stuck using generic words, but we don't have to be. —Luis Villa (WMF) (talk) 16:39, 11 July 2014 (UTC)
Yes. Or we can use the word "media" to cover all of our contents (if a mimetype check is not practical)? Jee 17:16, 11 July 2014 (UTC)
@Stefan4: @Jkadavoor: @LuisV (WMF): "Material" was used because the license is not always being applied to the entirety of what most people would consider a "work", and sometimes what the license is applied to isn't considered a work of authorship. So yes, databases—not generally considered works of authorship, but are "licensed material"; other things that don't strictly fall under the definition of "work" in a jurisdiction but include rights that are licensable under CC licenses might also count. But also it is more accurate in the case where only certain elements are being released under the CC license—only an excerpt from a book, only the music from a video, only the content from a website but not its copyrightable design elements. You could still accurately call these "works" (the wording on the older licenses isn't wrong in these cases) but it is confusing to people who see that the license applies to the work and don't know that "work" may be defined to be a smaller subset of the more obvious thing. We chose "material" not only to be more broadly inclusive but to indicate that a license may not necessarily apply to the entirety of a thing, but only to a separately copyrightable element. (Not that CC encourages people licensing things in a confusing fashion--if you license a bunch of different elements of a larger work differently, even if you mark them all as clearly as possible, it is probably just asking for trouble. But it is legally possible and people were in fact doing this with their materials.) Using "work" is not wrong; using "material" is more generic. Kat Walsh (spill your mind?) 19:19, 11 July 2014 (UTC)
  • Pictogram voting comment.svg Comment I think this is moving in the entirely wrong direction. The licensing notices are already too verbose. The proposed versions are twice as long and guarantee that no one will ever bother reading them. Why do we always have to make things more complicated (to the point of absurdity), rather than simplifying. Does anyone think that users actually read the wall of text at Special:Upload, for example? Less is more. Kaldari (talk) 23:42, 2 July 2014 (UTC)
  • @Kaldari: We had considers a brief option too at Template talk:Cc-by-sa-4.0. So either it can be as brief as a 1. single line (This work/material by <author> is licensed under a <license name with link to deed>. You can find a specimen of this license at <link to legal code>.) or 2. a summary of the license. Most of our other license tags are very brief. I don't know why CC tags are designed in a different way. Anyway the current tag is not acceptable as CC already changed many words/explanations in their deeds. Jee 03:35, 3 July 2014 (UTC)
  • @Jkadavoor: I'm fine with changing the wording, but can we have a simpler option to vote on? I don't like any of the lengthy ones suggested above and actually think they would make people less likely to understand the licensing. Kaldari (talk) 05:18, 3 July 2014 (UTC)
  • @Kaldari: Sure. Could you add one as option 4? I'm happy to wait more time for further suggestions before the voting start. Jee 05:27, 3 July 2014 (UTC)
  • I added a 4th option which keeps things simple, but still emphasizes the most important piece of information, the attribution. Kaldari (talk) 05:55, 3 July 2014 (UTC)
  • @Kaldari: Thanks; it is an acceptable compromise for me. One minor suggestion. The word "file" is a bit confusing as it was a matter of debate here. According to CC's stand the license is applicable to the Licensed Material without considering the medium of expression or quality. So I think a word "Material", "Work" or "Media" may more suitable than "File". Jee 06:05, 3 July 2014 (UTC)
  • Good point. I'll change it. Kaldari (talk) 06:48, 3 July 2014 (UTC)
  • I'm not yet sure whether I'd prefer a long or a short version, but what I do like a lot about option 4 is the emphasis on the attribution part. I'd very much prefer this. --El Grafo (talk) 09:36, 10 July 2014 (UTC)
  • Pictogram voting comment.svg Comment Of the current options given, a useful possibility would be Option 1 with the title and author of the work being optional i.e. the top line could read "This work by Real name (www.example.com) is licensed under" or "This work is licensed under". Wikimedia Commons has many already uploaded works for which changing the deed markup would not automatically cause the work title and author info to appear in the deed. In addition, it may happen where an altered version (i.e. a derivative work) of a CC-licensed work is uploaded and in such a case, assuming that there is only one author name may be problematic. For the Option 1 deed, it would also be useful for the deed to mention that commercial usage is allowed, possibly by changing "upon the material" to "upon the material, even commercially" for clarification. --Gazebo (talk) 10:25, 4 July 2014 (UTC)
  • Pinging early participants for further input: @, FDMS4, Dereckson:, @Colin, Jarekt, Multichill:, @El Grafo, Saffron Blaze, ChrisiPK:... Jee 09:13, 10 July 2014 (UTC)
    Sorry, I had totally forgotten about this discussion and now I am somewhat late to the party. The current suggestions are all still too explanatory for my taste. Note that we don't provide for any other licenses (e.g. {{GFDL}}, {{FAL}}) and from looking at the WMF input below it seems this is a good idea to protect both us and reusers. So my recommendation would be to change the template to visibly identify the licensing elements but not explain what they entail. Regards, -- ChrisiPK (Talk|Contribs) 11:54, 10 July 2014 (UTC)
    Thanks ChrisiPK. I like simple tags like {{GFDL}} and {{FAL}}) too. Since this is an important step, let us wait and see what WMF will say. Jee 13:57, 10 July 2014 (UTC)
    @Jkadavoor: then maybe we should abort the voting for now and postpone it? --El Grafo (talk) 14:32, 10 July 2014 (UTC)
    I've no clear idea. Usually Legal take much time to make any comment. In the mean time, I will try to add a simple option too as ChrisiPK suggested. Jee 15:07, 10 July 2014 (UTC)
I didn't follow the discussion either, but has it been discussed whether we could make the license details collapsible? They could be expanded by default for logged-out and new users, and collapsed by default for experienced users …    FDMS  4    15:41, 10 July 2014 (UTC)

WMF input[edit]

Hi everyone, I asked the WMF people for input. Actually for two types of input:

  1. Legal part: The license templates should be as short as possible (less is more!), but legally sound
  2. Design part: Our current layout has been in use for quite some time and can use an update. If we're rebuilding all cc license templates we might as well make them look more appealing

They're not telling us what to do, but advising us (the community) so we can make a decision. The people who'll take the lead from the WMF side:

  1. Legal part: Luis Villa (WMF wiki / wp entry). He knows quite a bit about copyright and cc licenses specifically, he's even doing a presentation about it on Wikimania
  2. Design part: Mun May Tee-Galloway (WMF wiki). One of the designers who will have a fresh view on the layout here. She has a specialty: icons!

Some other WMF people might help out too. I hope this helps to increase the quality of our licensing templates. Multichill (talk) 09:42, 10 July 2014 (UTC)

  • Pictogram voting comment.svg Comment Hi Multichill, thanks for asking them. Nothing wrong with a design overhaul in general, but I'd suggest to keep that separate from the content part this discussion is about. It's already complicated enough, imho. --El Grafo (talk) 09:58, 10 July 2014 (UTC)
  • Thanks Multichill and El Grafo. It will be very helpful if WMF can advise/help us. I too mentioned this with Luis Villa earlier. So I think we can wait a bit more? Jee 10:17, 10 July 2014 (UTC)
  • If we wait for WMF legal we may be here until next year. I say we provide a license template that replicates the deed offered by CC (their legal obviously had input into that and thinks they are valid) Then link to the license itself only. As to design, make that a separate issue. No need waiting for this cosmetic update as that can be done only after we decide on content anyway. Saffron Blaze (talk) 17:37, 10 July 2014 (UTC)

Pictogram voting comment.svg Comment So, some preliminary thoughts from me - thanks to Multichill and Jee for asking me to weigh in; sorry I couldn't do it more promptly.

  • There is no legally right/wrong answer, because there isn't much precedent for analyzing this sort of "summary" of a legal agreement. So these comments are even less legal advice than usual. They're essentially opinions of what I would think about if I were doing this for the Foundation; they're not statements of the law/meaning of the license, and they aren't the Foundation saying "do X".
  • I think it would be very good if design could weigh in before any decisions are made about which words to use, for two reasons. First, readability: more words + better visual design might be just as readable as fewer words + current (not very good) visual design. So the design may impact how many words we choose. Second, design will influence content and vice-versa: design may have creative ideas on how to present the core ideas, like a complete reorganization, or suggesting a "hide this in future" button, or many other things. They don't just simply make the words we choose prettier :)
  • This is probably obvious, but most of the wording improvements suggested by CC are, I think, no-brainers to adopt. For example, the new attribution language is much more helpful to readers than the old attribution language. So I'm glad to see that mostly reflected in the options above.
  • I suspect that attribution and the license information should not be mixed together. That can make it very confusing to know what attribution a user should use - the one in the "use this file" widget? The one in the license text? ...? There is also a lot of duplication- many repetitions of the file name, author name, etc. (I should also say that I'm pointing out the problem, but design will probably have better solutions for it than I will :)
  • If design and/or the community wants to cut word count, I would suggest leaving in restrictions (DRM clause, "may not give you all of the rights") and leaving out the non-core permissions ("licensor cannot revoke", "exception or limitation"). Prioritizing this way respects licensors and reduces the risk of a mistake for users.
  • I am biased, because I pushed CC to add it to the deed, but I think the "no additional restrictions" language needs to be in the summary. That is a core requirement of the license and should be visible to reusers.
  • The "no warranties are given" and "only some of the key features" language might make sense to move outside of the CC template, and use more widely, since those are true of essentially all of the license templates as far as I know (with the obvious exception of PD, since there is no "actual license" to link to).

Those are my preliminary thoughts; sorry they can't be more concrete/specific but this isn't that sort of problem :/ Hope they are helpful. I'm very busy in the run up to Wikimania but will try to be as responsive as possible here. Thanks! —Luis Villa (WMF) (talk) 01:59, 11 July 2014 (UTC)

Based on your points I'm wondering if we should work on a expandable show/hide template like at this example. We could show the minimum information in normal view and have the option to expand to show more information. Just a thought.... Multichill (talk) 11:50, 11 July 2014 (UTC)
@Multichill: Seems a good idea. I already implemented it for my old licenses. (FDMS4 also made a similar suggestion above.) Jee 15:56, 11 July 2014 (UTC)
Both of those examples hide the whole thing. I think I was thinking of hiding just the new "notices" section, since that is secondary information. In my mind, the important thing (that many of the PD templates get wrong :/ ) is to clearly explain to users what rights they have, so I would think we would always want to show the rights/basic responsibilities.
They also seem to default to closed, which is probably not ideal, but then again, I'm not a designer - I'd just like to be one in my next life ;) —Luis Villa (WMF) (talk) 16:28, 11 July 2014 (UTC)
@LuisV (WMF): Dou you mean option 6? Jee 17:33, 11 July 2014 (UTC)
Yes, something like that! I might consider calling them "Additional details" instead of "notices" if we went this route - the extra word won't hurt since so much else is hidden. —Luis Villa (WMF) (talk) 17:53, 11 July 2014 (UTC)
  • I can live with version 6. Version 6 still links to the deed instead of the actual license. Saffron Blaze (talk) 17:58, 11 July 2014 (UTC)
  • @Saffron Blaze: It has two links. One to deed and one to actual license under "Additional details". I think the CC deed is available in more languages than the legal code (not sure). I think it is OK; but open for further suggestions. Jee 03:56, 12 July 2014 (UTC)
  • Sorry Jee, but from the beginning it was pointed out that the template was in effect a deed and linking to it was redundant. The header link should be to the full text of the license and thus the link in the sentences would serve no further purpose. Saffron Blaze (talk) 14:06, 12 July 2014 (UTC)
  • @Saffron Blaze: I understand, and agree. Since our new template cover almost everything in the deed, there is no need to link again to it. Jee 15:40, 12 July 2014 (UTC)
Hi Multichill, any response from Mun May Tee-Galloway? Jee 15:48, 17 July 2014 (UTC)
Still working on it. But I agree with showing the most important info first and then make it an option to expand the rest if users want to find out more. I'll get back to you guys hopefully at latest the end of next week. MGalloway (WMF) (talk) 16:43, 17 July 2014 (UTC)
I have some initial thoughts and mock-ups to illustrate. Thanks for being so patient! Wikimania prep has been taking up pretty much all my time. Here
(1.0)
is an attempt to connect the usage and terms more than we previously did, by stating in one place and sentence "Under this license terms*, you are free to…:" and then a list of things you're free to do and what you must do after, which is to attribute and sharealike. But I began by questioning why we care about CC license banner and the purpose of the license. Because people tend to be unaware of their boundaries, a CC license is there to protect the work of the creator and the fair usage of the user of the work. Since CC license permits users to do a lot of things (which they already have no problems with) so long as they are in compliant with license. I thought it was more important for users to know know what they must do if they choose to use the work, because without following terms, they risk getting in trouble. Here
(2.0)
, I made the entire banner look like a single important message with a very clear hierarchy of info, as if saying: Attribute and Sharealike and you'll be fine. Same thing here
(2.1)
, just with different language that's more actionable, "You are free to share & adapt…as long as you…Give attribution, Share Again." I've moved around some sentences here and there but don't claim to for them to be more appropriate for legal purposes, but is what I think could be more understandable. A more condensed version could look like this
(2.2)
. On a side note, I really like how The Noun Project has done to educate icon downloaders to properly attribute the author. When you click on the Download button, you are required to agree to attribute the author (3.0). Once downloaded, you are directed to a page where you get pretty specific instructions on where to attribute the author depending on popular medium usages. We should do something similar!MGalloway (WMF) (talk) 13:56, 7 August 2014 (UTC)
I want to thank May for working on this - it has challenged me to think hard about what should be in the templates. Three quick comments:
  1. It took me a while to wrap my head around it, but I like the idea of de-emphasizing the permissions (which I think are widely assumed) and emphasizing the restrictions.
  2. It is not obvious from the mockup, but the idea with 2.2 is that there could be mouseovers, popups, or other expansion which would show more information around the two primary restrictions.
  3. 2.2 scared me at first (fewer words == worried lawyer) but the more I think about it, the more it could free us up to do some interesting things in the expanded area. I still want to discuss it some with others on the legal team, but I think it's very promising.
My two cents. —Luis Villa (WMF) (talk)
Do we really want to give specific instructions how to follow the license? Looking at the screenshot of the Noun Project, they tell you clearly what you need to do, e.g. to "Include the attribution either on the page where the symbol is displayed, or in About or Credits pages.". The problem with CC licenses is that we do not know what exactly they require. Threads about whether CC-by mandates that you put the attribution next to the image pop up regularly. The Commons/Wikimedia community may have an idea of how to interpret the license but who tells us that this is the one true way? Thinking ahead: What happens if we propagate this interpretation via our license templates and some court decides that it is invalid? Which ramifications would this have for us; would people even be able to extract damages from WMF because they followed the interpretation on the license template and were subsequently sued themselves? Regards, -- ChrisiPK (Talk|Contribs) 08:25, 8 August 2014 (UTC)
To a large extent, we already give instructions on how to follow the licenses. The template contains statements about compliance, and the various attribution gadgets make (implicit) statements about how to comply. So, sure, we have to do it carefully (and ultimately it has to be a collective/community decision) but that shouldn't stop us from thinking creatively about how to encourage people to attribute correctly/easily. Or perhaps to put it another way: anecdote suggests people fail to understand how to comply the vast majority of the time. If we try to help fix that, of course there is some risk that we get it wrong, but it is hard to see how we could get it so wrong that we make it worse than the current situation. —Luis Villa (WMF) (talk) 10:03, 8 August 2014 (UTC)
Multichill, what about this new layout? I think "texts" of "Option 6" can be used with any of these layout, hiding bottom parts under "Read more". Jee 11:28, 15 August 2014 (UTC)

Made in Japan, published in USA?[edit]

Hi,

Can we assume that this was first published in USA, even if the device was made in Japan? Regards, Yann (talk) 07:42, 7 September 2014 (UTC)


About the file Vintage Panasonic Panapet 70 Ball'n Chain Radio, Model R-70, 4-3-8 Inches in Diameter, Made in Japan (9791099194).jpg, yes. That file includes four published elements:
1. The 2013 photograph of the box was published on flickr, in the U.S.
2. The 1970s box, which displays a photograph of the radios, was published in the U.S., as evidence by the fact that the box bears the brand Panasonic, which, in those years, was the brand that the company Matsushita used specifically and only in North America, and the accompanying text is in English.
3. The photograph of the radios, which can reasonably be assumed to have been made specifically for publication on the packaging and perhaps in other advertising material for the product. The same photograph may have been used also for the same purposes around the same time elsewhere in the world with the National brand packaging, but there would be no particular reason to believe that the publication in the rest of the world would have significantly preceded the publication in the U.S.
4. The radios. The radios of this version also bear the brand Panasonic, which might imply the distribution of this version specifically in the United States, but anyway the reasoning is the same as for the photograph, as there is no particular reason to believe that the offering and distribution to the public of the radios would have come significantly later in the U.S. than elsewhere in the world.
That said, it does not mean that the file can or should be kept on Commons. Firstly, a "no notice" tag was added, but it should be checked if actually the boxes did not have a copyright notice somewhere, and if the radios did not have a copyright notice somewhere (if someone believes that would make a difference for the reproductions of images of objects of that type). Secondly, the uploader himself (although not the author of any of the four elements) requested the speedy deletion of the file soon after the upload, not for a reason of copyright, but only for the reason "accidental upload". Commons usually deletes files when it is requested soon after the upload by the uploader invoking that he did not really mean to upload it. Which is a sensible practice, as Commons can't reasonably force anyone to upload files against their will. However, that would not stop anyone else from reuploading the file to Commons from the source, if the file is free. -- Asclepias (talk) 13:59, 7 September 2014 (UTC)
The radios themselves are utilitarian objects, and do not get a copyright. I am talking of the packaging only, of course. I suppose that these were sold in USA, even if made in Japan, and that selling the boxes constitutes publication. Yann (talk) 14:29, 7 September 2014 (UTC)

First publication in the USA does not tangle the copyright in the country of origin. Fair use at best. --Denniss (talk) 11:20, 7 September 2014 (UTC)

First publication in the USA means the USA is the country of origin. Interesting question on where publication occurred though. Carl Lindberg (talk) 12:45, 7 September 2014 (UTC)
Country of origin is where the original work was created or where the company releasing the product is located. --Denniss (talk) 13:31, 7 September 2014 (UTC)
That is incorrect. "Country of origin" is defined by the Berne Convention; it is typically the country of first publication. (It gets into other cases when unpublished, published in a non-Berne country, or simultaneously published in multiple countries). See Article 5(4). This is intentional; it is very possible for an author in a non-Berne country to get protection by having first publication be in a Berne country. I think Article 3 is the one that speaks most to where publication happens, but it's not explicit. Carl Lindberg (talk) 13:39, 7 September 2014 (UTC)
If the box art was published in multiple countries within 30 days, the country of origin is the country with the shortest term. According to [4], {{PD-US-no notice}} does not seem to be a term, although the ruling was specifically about {{PD-US-not renewed}}. If it was published concurrently in multiple countries, it may therefore be necessary to show that none of those countries has a term shorter than 95 years from publication. --Stefan4 (talk) 20:22, 7 September 2014 (UTC)
Yep. I don't think the failure of formalities would count as a shorter term under Berne. But then the question is which countries was it published in. The Berne Convention seems to more lean towards where copies were made available to the public. Given that the packaging was in English, it seems likely that these were mainly distributed only in English-speaking countries, and maybe even the US in particular. (And it's not the actual items which have the copyright in this case; it's the packaging, so the question is where was that published). One or two might qualify as incidental -- the photo is of the product, and whatever designs happened to be there are incidental -- but a couple are basically only of the packaging. Carl Lindberg (talk) 03:05, 8 September 2014 (UTC)
All text seems to be below the threshold of originality, so the question is only about the images. The same images may be used in multiple countries, even if the language of the text differs. --Stefan4 (talk) 15:22, 8 September 2014 (UTC)
Per definition, first publication in the USA makes the USA the country of origin. -- Asclepias (talk) 13:59, 7 September 2014 (UTC)

Why are radios intended for use in Europe almost worthless in Japan? --84.61.136.79 10:08, 9 September 2014 (UTC)

Although the question does not relate to copyright, it is likely the case where radios (as well as other products) may be manufactured in one country (such as Japan) for reasons such as cost or logistics even though the product will be exclusively marketed in a different region (i.e. Europe.) For example, the Lafayette LT-725A radio tuner was marketed in the US but was (at least in some cases) made in Japan. In such a case, the product will be designed for usability in the country or countries where it is marketed. According to the English Wikipedia article on the FM broadcast band, the FM broadcast range in Japan (76.0 to 90 MHz) does not completely overlap the European FM broadcast range (87.5 to 108.0 MHz.) Other radio broadcast bands may have similar limitations. --Gazebo (talk) 14:58, 10 September 2014 (UTC)
Why are FM radios intended for use in Japan illegal in Malaysia? --84.61.136.79 17:25, 14 September 2014 (UTC)

Full metal Alchemist images[edit]

While looking for alchemical symbols I noticed File:FMA Human Transmutation Circle.svg's description has "Fullmetal Alchemist original 2003 Anime." The page claims it is licensed under the Creative Commons Attribution 3.0 Unported License, but I am dubious that the uploader is the copyright holder or that the book or anime creators gave such a license. All my googles just point to Full Metal Alchemist as the origin. This looks to be too complex to fall below Commons:Threshold of originality. -84user (talk) 20:59, 10 September 2014 (UTC)

  • Pictogram voting comment.svg Comment: There is a Deletion request. Please address your arguments there. --Amitie 10g (talk) 19:39, 13 September 2014 (UTC)

1925 diagram of an archeological site[edit]

I can't tell whether I am allowed to use the 1925 diagram of the Roman villa at Folkestone or not! It was originally published in the United Kingdom (London) by Samuel Edwards Winbolt in 1925, in his archeological "Roman Folkestone." I cannot find the date of his death, or any other information about him. The book was only published in one edition, and as far as I know, the copyright was not renewed, and it is currently in the public domain in the UK - a PDF of the book is available for download on the website of the most recent archeological dig (url=http://www.atownunearthed.co.uk/wp-content/uploads/2011/10/Roman-Folkestone-Main-Text-PDF-27.2MB.pdf). However, I can't tell if it is yet in the public domain in the US - I'm confused by the public domain dates and renewal system for 1925. Florimell1919 (talk) 07:17, 14 September 2014 (UTC)

Patuxai[edit]

The Patuxai in Laos was designed by Tham Sayasthsena in 1957. The paragraph on FoP let me stop to file in a deletion request for almost the whole category. Have you talked about Laos already? Many pictures of the Lao monasteries may be ok because mostly older or no known artists or year of construction and always under (re)construction, but how about the Patuxai in Laos. In Cambodia we deleted the photos of the Independence Monument. I will stop my own uploads of the Patuxai, but I am not 100 per cent sure, whether I should request the deleting due to the lack of FoP in Laos. -- DerFussi 07:59, 14 September 2014 (UTC)

Unsure of copyright[edit]

Would someone have a moment to look at this photo. When the uploader added it in 2006, he added a copyright logo. I'm not sure if the logo should be removed, or the photo deleted. Thanks! Magnolia677 (talk) 15:11, 14 September 2014 (UTC)

There are several copyrighted logo on the picture, all seems to me to be de minimis, ie not the main subject of the picture (it's a picture about Beale Street, not about a logo). --Dereckson (talk) 15:31, 14 September 2014 (UTC)
That looks quite alright. You always retain your copyrights by releasing a work under the Creative Commons licenses. And the uploader JeremyA[therton] appears to be the original photographer. De728631 (talk) 15:36, 14 September 2014 (UTC)

how to get licence info[edit]

hi friends! I have uploaded two photographs today. S M Pathak.jpg and JoLareDeenKeHet.jpg and I found them on the website of the concerned author. i have provided this info in the source section. but, I am not sure if it is free to use or not. how can i get this info? please help me!--सत्यम् मिश्र (talk) 18:01, 14 September 2014 (UTC)

Hello, I have marked your uploads for speedy deletion because they are copyright infringements. As a rule of thumb, all works published anywhere online or in print are copyrighted and non-free unless it has specifically been mentioned that they are free to use. The website you took the images from does not seem to have any free licence so you should not have uploaded the files at all. If any web content has been released under a free licence or the image is out of copyright, it should be noted on that page, or the image is obviously old enough to be in the public domain. And, again, this didn't happen to be the case for your uploads. So, next time please research the image's copyright status before you upload them here. De728631 (talk) 18:48, 14 September 2014 (UTC)
Thanks for your reply De728631 sir! I will contact you later when get a free copy of the image.--सत्यम् मिश्र (talk) 09:07, 15 September 2014 (UTC)

Wikimedia Commons & Facebook[edit]

Howdy guys, I want to upload pictures to Wikimedia Commons (yay! finally! :-)), and I was also asked to post some of them on Facebook. Now I want to make sure I got this copyright thing right: I upload pictures to Commons under CC-BY-SA, then on Facebook, the license there stays the same, only Facebook is given the right to do whatever they please with them (fine with me for the selection). Anything wrong or that I forgot? Thank you guys. --The Evil IP address (talk) 16:21, 15 September 2014 (UTC)

I think that's right. According to some earlier discussion (can't find it right now, I think it was here on Commons somewhere), there may be a problem with CC-BY-SA and Facebook, as Facebook apparently requires that they can use images uploaded there for their purposes (without adhering to a copyleft license such as CC-BY-SA). This, however, doesn't affect you if you're the author. You can't give away any rights for CC-BY-SA images by other people, so it seems that one shouldn't upload CC-BY-SA images by others to Facebook, but for your own images, you can grant Facebook any rights you want in addition to the CC-BY-SA license you grant to the public. Gestumblindi (talk) 19:22, 15 September 2014 (UTC)
Yes, it's right, User:The Evil IP address here on FB "For content that is covered by intellectual property rights, like photos and videos (IP content), you specifically give us the following permission, subject to your privacy and application settings: you grant us a non-exclusive, transferable, sub-licensable, royalty-free, worldwide license to use any IP content that you post on or in connection with Facebook (IP License). This IP License ends when you delete your IP content or your account unless your content has been shared with others, and they have not deleted it."; even if you are evil :)--Pierpao.lo (listening) 11:18, 18 September 2014 (UTC)

text logos[edit]

this File:Oxfam italia.JPG and this File:Stemma Provincia MB con scritte.png can stay here on Commons? thanks--Pierpao.lo (listening) 11:11, 18 September 2014 (UTC)

Maison de Balzac, photo of the room with the genealogical chart[edit]

I asked this at the Help Desk the other day but now see that the question may be more appropriate on this page, so here it is. I'd like to use a picture (which I took myself) of the genealogical chart of the characters in fr:La Comédie humaine, in one of the rooms of the fr:Maison de Balzac. The house itself is over 150 years old, but this room has been renovated more recently. The information in the chart is deduced from the novels, so presumably public-domain by this point, but the form and presentation of the chart may still be under copyright. If you want to see what I'm talking about, there are pictures at L'Internaute.com. My own picture is similar to the one at L'Internaute; I would happily contribute it to Commons if it's OK to do so, but obviously not if it would violate the museum's copyrights. May I upload it? A. Mahoney (talk) 12:33, 18 September 2014 (UTC)

I don't believe the date of the renovation of the room would be relevant -- only the date that the chart was made, and who the author of the chart was. Facts themselves are not copyrightable, but distinctive presentations based on facts are. AnonMoos (talk) 01:51, 21 September 2014 (UTC)

Quick question[edit]

Are morgue/autopsy photos in the United States copywritten? They are the work of state government and I do not believe that they would be copywritten. Are they not eligible for copyright? If not, what license would be appropriate?--Gourami Watcher (talk) 23:09, 18 September 2014 (UTC)

It's only works of the United States Federal Government which are PD in the US. The only state governments AFAIK that have any such sort of exemption are California ({{PD-CAGov}}) and Florida ({{PD-FLGov}}) –⁠moogsi (talk) 23:25, 18 September 2014 (UTC)
By the way, the verb form is "copyrighted", not "copywritten"... AnonMoos (talk) 01:53, 21 September 2014 (UTC)

Re-upload of nazi supertanks[edit]

Hi, a user from it:wiki, specifically it:Discussioni utente:Caccola581, uploaded these images: File:LandkreuzerP1000Ratte.jpg, File:P.1500 Monster.jpg. As you can see he cites photobucket.com and strangevehicles.com as sources, and I would suppose these would not be free-licence images. This is not the first time he uploaded them, he also uploaded and/or used them in 2012 (I don't know if only on it:wiki or also Commons), and they were canceled, see: his contributions and his discussion page, where he was notified about them. In short, I suppose they should be cancelled, but I'm asking you to be sure. When you take a decision I can write him on it:wiki, in case you need it. Thanks, --Amendola90 (talk) 10:38, 19 September 2014 (UTC)

New Hershey logo a PD-textlogo?[edit]

New Hershey logo looks like it may qualify as a non-copyrightable textlogo... but it's borderline IMO. Figured I'd ask for opinions before moving. – JBarta (talk) 19:58, 20 September 2014 (UTC)

Considering the Best Western logo, I'm going to go with non-copyrightable.--Prosfilaes (talk) 20:52, 20 September 2014 (UTC)