<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<base href="x-msg://7/"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Heather wrote : “An author wishing to pre-authorize translations but only under particular conditions [...] should [...] grant additional permissions
[...] with a CC+ license.”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First, note that CC+ it’s not a CC license, but a CC protocol (or tool). The distinction is important because what’s in the “+” doesn’t involve
Creative Commons at all: it only redirects users to where these permissions are described and(or) can be obtained.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">But, if one believes that one of the goals of CC licenses was to simplify the life of users who need to understand the permissions granted to them,
by limiting the number of permissions and normalizing their formulation, this goes exactly against this goal. Statements of supplementary permissions will raise new uncertainties, above those already present in the standard CC conditions (-NC, above all).
For instance, I would like to see a definition of “appropriate professional translator” that wouldn’t raise uncertainties, considering that translation will involve different countries, with their traditions, educational systems, professional organizations,
etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A more appropriate use of CC+ in this specific example would be to (1) indicate that translations are welcomed and (2) provide the way to seek
permission (for instance, giving the email of the person who can grant it, or confirming that it’s the author, who is normally identified through attribution). A potential translator could then explain why he or she can do the job adequately.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">By the way, although CC+ has been around for more than 9 years; does anyone know it it’s widely used. A Google search didn’t bring me much information.
Creative Commons asks users of this protocol to let them know, but there seems to be only a handful of them, not related to the issues discussed here
<a href="https://wiki.creativecommons.org/wiki/Category:License_and_CCPlus">https://wiki.creativecommons.org/wiki/Category:License_and_CCPlus</a>
<a href="https://wiki.creativecommons.org/wiki/Category:CC%2B">https://wiki.creativecommons.org/wiki/Category:CC%2B</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Marc Couture<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> goal-bounces@eprints.org [mailto:goal-bounces@eprints.org]
<b>De la part de</b> Heather Morrison<br>
<b>Envoyé :</b> 24 janvier 2017 09:27<br>
<b>À :</b> Global Open Access List (Successor of AmSci)<br>
<b>Objet :</b> Re: [GOAL] How much of the content in open repositories is able to meet the definition of open access?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">hi Fiona,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It seems we have been thinking along the same lines - I have a similar proposal that tries to address the same issue.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">An author wishing to pre-authorize translations but only under particular conditions, e.g. that the translation is done by an appropriately qualified translator and a disclaimer is used, should use a restrictive license (either All Rights
Reserved but free-to-read, CC-BY-NC-ND or CC-BY-ND) but grant additional permissions. In the case of CC licenses, this can be done with a CC+ license.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As explained on the Creative Commons page: "You have the option of
<a href="https://wiki.creativecommons.org/wiki/Frequently_Asked_Questions#Can_I_waive_license_terms_or_conditions.3F" title="Frequently Asked Questions">
granting permissions</a> above and beyond what the license allows; for example, allowing licensees to translate ND-licensed material. If so, consider using
<a href="https://wiki.creativecommons.org/wiki/CCPlus" title="CCPlus">CC+</a> to indicate the additional permissions offered."<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The reason you need to start with the more restrictive license and then grant additional permissions is because you cannot use a more open license and then attach additional restrictions - this defeats the purpose of open licensing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Here is a boilerplate approach to put on a terms and conditions website to explain these permissions:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Translations can be made without explicitly seeking permission under the following conditions:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Professional qualifications of translator: [insert definition of what you consider to be an appropriate professional]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A disclaimer must be prominently placed on the work as follows [insert disclaimer language and any other terms such as placement]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Certification by the original publisher - provide instructions for the translator in case they wish to have the translation certified.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If the author (or publisher) does not want to grant blanket commercial rights but is willing to grant some rights that others might consider commercial, this can also be specified here. For example, if the author or publisher of a book
expects royalties if a downstream for-profit publisher actually makes money, details might be specified here so people know what to expect, e.g. after costs of producing the translation are covered, royalties of x are due to y. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't suggest that this is the final answer on how to handle translations but hope that this is a useful discussion.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Heather Morrison<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On 2017-01-24, at 8:37 AM, Fiona Bradley <<a href="mailto:Fiona.Bradley@rluk.ac.uk">Fiona.Bradley@rluk.ac.uk</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hi Heather,</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I think there’s too much variation in copyright arrangements and agreements for me to comment on that but indeed should authors prefer and there’s no other arrangements
in place stating otherwise you could put authors in place of institution/publisher in my comment.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I think license choice and translation inform but shouldn’t necessarily drive eachother. Personally speaking, I tend to start with an assumption of best intentions
(eg CC-BY) but make room for exceptions. Under CC-BY or another open license it can still be helpful to have some basic procedures as a professional courtesy for translation in place (as simple as emailing the author or as formal as a permissions procedure)
as eg it avoids situations like doubled work - if more than one person decides to translate a paper into the same language, but they are unaware of each other – have had that happen before!</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Fiona</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-family:"Calibri","sans-serif"">From:<span class="apple-converted-space"> </span></span></b><span lang="EN-GB" style="font-family:"Calibri","sans-serif""><<a href="mailto:goal-bounces@eprints.org"><span style="color:purple">goal-bounces@eprints.org</span></a>>
on behalf of Heather Morrison <<a href="mailto:Heather.Morrison@uottawa.ca"><span style="color:purple">Heather.Morrison@uottawa.ca</span></a>><br>
<b>Reply-To:<span class="apple-converted-space"> </span></b>"Global Open Access List (Successor of AmSci)" <<a href="mailto:goal@eprints.org"><span style="color:purple">goal@eprints.org</span></a>><br>
<b>Date:<span class="apple-converted-space"> </span></b>Tuesday, 24 January 2017 at 11:59 am<br>
<b>To:<span class="apple-converted-space"> </span></b>"Global Open Access List (Successor of AmSci)" <<a href="mailto:goal@eprints.org"><span style="color:purple">goal@eprints.org</span></a>><br>
<b>Subject:<span class="apple-converted-space"> </span></b>Re: [GOAL] How much of the content in open repositories is able to meet the definition of open access?</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Fiona,<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Thank you for this information about professional translation services, and the importance of certification and disclaimers with translated works. If the original author wishes to ensure that translations are done by
appropriately trained professionals, certified, etc., this is a reason to avoid using licenses granting blanket downstream rights to create derivatives, ie if using CC licenses the No Derivatives should be used. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">I refer to "author" rather than "institution/publisher" as you did. If you support CC licensing it seems odd to me that you would assume the institution/publisher should make choices relating to copyright. Do you see
authors as the copyright holders / CC licensors or do you assume copyright transfer to an institution / publisher who is then the CC-BY licensor (it appears this is similar to what Elsevier is currently doing)?<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">best,<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Heather Morrison <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">-------- Original message --------<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">From: Fiona Bradley <<a href="mailto:Fiona.Bradley@rluk.ac.uk"><span style="color:purple">Fiona.Bradley@rluk.ac.uk</span></a>><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Date: 2017-01-24 6:43 AM (GMT-05:00)<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">To: "Global Open Access List (Successor of AmSci)" <<a href="mailto:goal@eprints.org"><span style="color:purple">goal@eprints.org</span></a>><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Subject: Re: [GOAL] How much of the content in open repositories is able to meet the definition of open access?<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hi all,</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">For a similar approach in terms of data, the Open Data Institute has a data spectrum that also looks at closed -> open pathways:<span class="apple-converted-space"> </span><a href="https://theodi.org/data-spectrum"><span style="color:purple">https://theodi.org/data-spectrum</span></a></span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Regarding translations, in my experience having managed these processes the most important policies aren’t those relating to how the original work is licensed
but whether the originating institution/publisher makes agreements with translators, insists on certified translations, makes disclaimers about whether translations are considered official or not (in the case of legal texts, for instance), and provides for
a notice and takedown procedure. This risk mitigation acknowledges that however a work is licensed, whether OA or in formal license by the publisher, there is always the potential for issues in translation to occur and there needs to be procedures in place
in place to handle that and to address where liability resides. I wouldn’t see this as a risk inherent to OA or reason not to license CC-BY.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">In the case of medical instructions, organisations such as<span class="apple-converted-space"> </span><a href="http://translatorswithoutborders.org/"><span style="color:purple">http://translatorswithoutborders.org/</span></a><span class="apple-converted-space"> </span>and
many others work extensively in this area to provide professional and/or certified translation, whereas journal articles are often translated by researchers in the field who are fluent in both languages but not translators.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Kind regards,</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Fiona</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">-- </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Fiona Bradley<span class="apple-converted-space"> </span><br>
Deputy Executive Director<br>
RLUK</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Office: 020 7862 8463 Mobile: +44<span class="apple-converted-space"><span style="background:white"> </span></span><span style="background:white">7432 768 566<br>
</span><a href="http://www.rluk.ac.uk/" target="_blank"><span style="color:#0563C1">www.rluk.ac.uk</span></a><br>
RLUK Twitter feed: @RL_UK</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Registered Office: Senate House Library, Senate House, Malet Street, London WC1E 7HU<br>
Registered Company no: 2733294<br>
Registered Charity no: 1026543</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-family:"Calibri","sans-serif"">From:<span class="apple-converted-space"> </span></span></b><span lang="EN-GB" style="font-family:"Calibri","sans-serif""><<a href="mailto:goal-bounces@eprints.org"><span style="color:purple">goal-bounces@eprints.org</span></a>>
on behalf of Heather Morrison <<a href="mailto:Heather.Morrison@uottawa.ca"><span style="color:purple">Heather.Morrison@uottawa.ca</span></a>><br>
<b>Reply-To:<span class="apple-converted-space"> </span></b>"Global Open Access List (Successor of AmSci)" <<a href="mailto:goal@eprints.org"><span style="color:purple">goal@eprints.org</span></a>><br>
<b>Date:<span class="apple-converted-space"> </span></b>Monday, 23 January 2017 at 7:55 pm<br>
<b>To:<span class="apple-converted-space"> </span></b>"Global Open Access List (Successor of AmSci)" <<a href="mailto:goal@eprints.org"><span style="color:purple">goal@eprints.org</span></a>><br>
<b>Subject:<span class="apple-converted-space"> </span></b>Re: [GOAL] How much of the content in open repositories is able to meet the definition of open access?</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">With all due respect to the people who created and shared the "how open is it" spectrum tool, I find some of the underlying assumptions to be problematic.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">For example the extreme of closed access assumes that having to pay subscriptions, membership, pay per view etc. is the far end of closed. My perspective is that the opposite of open is closure of knowledge. Climate change
denied, climate scientists muzzled, fired or harassed, climate change science defunded, climate data taken down and destroyed, deliberate spread of misinformation. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">This is not a moot point. This end of the spectrum is a reality today, one that is far more concerning for many researchers than pay walls (not that I support paywalls).<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Fair use in listed in a row named closed access. I argue that fair use / fair dealing is essential to academic work and journalism, and must apply to all works, not just those that can be subject to academic OA policy.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">There is an underlying assumption about the importance and value of re-use / remix that omits any discussion of the pros, cons, or desirability of re-use / remix that I argue we should be having. Earlier today I mentioned
some of the potential pitfalls. Now I would like to two potential pitfalls: mistranslation and errors in instructions for dangerous procedures.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">There are dangers of poor published translations to knowledge per se (ie introduce errors) and to the author's reputation, ie an author could easily be indirectly misquoted due to a poor translation. There are good reasons
why some authors and journals hesitate to grant downstream translations permissions. Reader side translations (eg automated translation tools) are not the same as downstream published translations, although readers should be made aware of the current limitations
of automated translation.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">If people are copying instructions for potentially dangerous procedures (surgery, chemicals, engineering techniques), and they are not at least as expert as the original author, it might be in everyone's best interests
if downstream readers are not invited and encouraged to manipulate the text, images, etc.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">In creative works, eg to prepare a horror flick, by all means take this and that, mix it together and create something new and intriguing. I am not convinced that the same arguments ought to apply to works that might
guide procedures in a real hospital operating room.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">I suggest the "how open is it" spectrum is a useful exercise that has served a purpose for some but not a canon for all to adhere to. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">best,<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Heather Morrison <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">-------- Original message --------<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">From: David Prosser <<a href="mailto:david.prosser@rluk.ac.uk"><span style="color:purple">david.prosser@rluk.ac.uk</span></a>><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Date: 2017-01-23 2:16 PM (GMT-05:00)<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">To: "Global Open Access List (Successor of AmSci)" <<a href="mailto:goal@eprints.org"><span style="color:purple">goal@eprints.org</span></a>><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Subject: Re: [GOAL] How much of the content in open repositories is able to meet the definition of open access?<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">I rather like the ‘How open is it?’ tool that approaches this as a spectrum:<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><a href="http://sparcopen.org/our-work/howopenisit/"><span style="color:purple">http://sparcopen.org/our-work/howopenisit/</span></a><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif"">I may be quite ‘hard line’, but I acknowledge that by moving along the spectrum a paper, monograph, piece of data (or whatever) becomes more open - and more open is better
than less open.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif"">If the funders have gone to the far end of the spectrum it is perhaps because they feel that the greatest benefits are there, not because they have been convinced that they
have to follow the strict, ‘hard line’ definition of open access.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif"">David</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Helvetica","sans-serif""> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">On 23 Jan 2017, at 18:30, Richard Poynder <<a href="mailto:richard.poynder@gmail.com"><span style="color:purple">richard.poynder@gmail.com</span></a>> wrote:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">Hi Marc,</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">You say:</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">"I certainly qualify as an OA advocate, and as such:</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">I don’t equate OA with CC BY (or any CC license); in fact, I’m a little bit tired of discussions about what 'being OA' means."</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">I hear you, but I think the key point here is that OA advocates (perhaps not you, but OA advocates) are successfully convincing a growing number of research funders (e.g.
Wellcome Trust, RCUK, Ford Foundation, Hewlett Foundation, Gates Foundation etc.) that CC BY is the only acceptable form of open access. </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">So however tired you and Stevan might be of discussing it, I believe there are important implications and consequences flowing from that. </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Trebuchet MS","sans-serif"">Richard Poynder</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:18.0pt;font-family:"Trebuchet MS","sans-serif";color:blue"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:18.0pt;font-family:"Trebuchet MS","sans-serif";color:blue"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">On 23 January 2017 at 16:31, Couture Marc <<a href="mailto:marc.couture@teluq.ca" target="_blank"><span style="color:purple">marc.couture@teluq.ca</span></a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Hi all,<span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Just to be clear, my position on the basic issue here.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">I certainly qualify as an OA advocate, and as such :<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">- I don’t equate OA with CC BY (or any CC license); in fact, I’m a little bit tired of discussions about what “being OA” means.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">- I work to help increase the proportion of gratis OA, still much too low.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">- I try to convince my colleagues that CC BY is the best way to disseminate scientific/scholarly works and make them useful.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">I favour CC BY over the restricted versions (mainly -NC) because I find the arguments about potentially unwanted or devious uses far less compelling than those about the advantages of unrestricted uses and the drawbacks
of restrictions that can be much more stringent than they seem at first glance.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA">Like Stevan said, OA advocates are indeed a plurality. The opposite would bother me.</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#888888"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#888888">Marc Couture</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB"><br>
_______________________________________________<br>
GOAL mailing list<br>
<a href="mailto:GOAL@eprints.org"><span style="color:purple">GOAL@eprints.org</span></a><br>
<a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal" target="_blank"><span style="color:purple">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal</span></a><o:p></o:p></span></p>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><br>
<br clear="all">
<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">--<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Richard Poynder<br>
<a href="http://www.richardpoynder.co.uk/" target="_blank"><span style="color:purple">www.richardpoynder.co.uk</span></a><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">_______________________________________________<br>
GOAL mailing list<br>
<a href="mailto:GOAL@eprints.org"><span style="color:purple">GOAL@eprints.org</span></a><br>
<a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal"><span style="color:purple">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal</span></a><o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">_______________________________________________<br>
GOAL mailing list<br>
<a href="mailto:GOAL@eprints.org"><span style="color:purple">GOAL@eprints.org</span></a><br>
<a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal"><span style="color:purple">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal</span></a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>