<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
/* 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
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{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;}
/* List Definitions */
@list l0
{mso-list-id:1734964213;
mso-list-template-ids:-1535628242;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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:black">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Heather Morrison raises in this thread some relevant and important issues regarding open licenses: How they are displayed? How to treat works combining
elements bearing various licenses (some of them being possibly “all rights reserved”)? She asks:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">“who is using embedded licensing metadata (as opposed to displayed), and how?”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Licensing metadata embedding, though not explicitly part of its “best practice”, is suggested by DOAJ, and is a condition for obtaining the DOAJ
Seal. This can be done by including basic HTML code in the article (and/or abstract) pages, and by importing XMP metadata in the PDF (see
<a href="https://doaj.org/rights">https://doaj.org/rights</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:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">I was in charge of this task for our small journal (<a href="http://ijthe.org">http://ijthe.org</a>) when we had to reapply to DOAJ, and we did qualify
for the Seal. However, I didn’t see any way to embed, in the (HTML) abstract page or the PDF, anything other than a global license applying to the whole article. Embedding licensing metadata of individual elements is probably easier in the HTML versions of
the articles, but as we offer only PDFs (and HTML abstracts), I didn’t try to find how to do it. Maybe others can pitch in.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">We do include in the CC mention displayed in the journal footer the disclaimer (“Except when otherwise noted...”), and we clearly display in the
articles (as it’s usually done in scholarly publishing) the status of any element not covered by our CC licence. However, I didn’t find anything about embedding in the PDF such a disclaimer, which would be useless anyway if the licensing info of individual
elements is not also embedded.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">As a final thought, as part of an exhaustive survey of Canadian scholarly OA journals, I assessed how journals cope with copyright matters. I plan
to write about it soon (the survey is almost finished), but I can already point out that these (mostly) small (or very small indeed) journals could really improve their practice in this matter. I’ll just say for now that talking of embedding licensing metadata
would be too soon, too much for many journals, as compared to actually display the license (if any) so that their potential recipients (users/readers) can see it, or even to say something user rights, or even about copyright itself. DOAJ could really be of
help here, and I know they are making efforts to reach these journals.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><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:black">Marc Couture<o:p></o:p></span></a></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>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-CA" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-CA" 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> 28 août 2019 12:17<br>
<b>À :</b> goal@eprints.org<br>
<b>Objet :</b> Re: [GOAL] Informed consent and open licensing: some questions for discussion<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Thank you Martyn, this is very helpful.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">As an author, I have appreciated MDPI's flexibility with respect to licenses. I am sure that other publishers have similar situations where re-use of material and/or accommodating
particular authors requires flexibility with respect to licensing. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">This mixed licensing environment raises a number of questions, mostly technical ones. Fully answering the questions requires an understanding of who proposes to use these works,
and how. Following are 2 questions that I hope will further understanding of the issues, one for MDPI and other publishers and one for everyone.<o:p></o:p></span></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Calibri","sans-serif"">For MDPI and other publishers: based on the Jan. 31, 2019 DOAJ metadata, it appears that all or nearly all of MDPI journals have answered "yes" to "Machine-readable CC licensing information embedded or displayed
in articles". Q: can you explain how embedding works when the CC license does not apply to all of the content in the article, as is the case when re-use of an item like an image requires permission and must be under All Rights Reserved terms? For example,
do the elements that require separate licensing have separate metadata embedded licensing? Does the embedded metadata at the article level state the default license only or does it speak to the separately licensed material, in specific or general terms? <br>
<br>
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Calibri","sans-serif"">Everyone: who is using embedded licensing metadata (as opposed to displayed), and how? Are there hopes or expectations of how this metadata will be used in future for which there are no examples yet? <o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">Further discussion - answers or more questions - is encouraged.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div id="Signature">
<div id="divtagdefaultwrapper">
<p><span style="font-family:"Calibri","sans-serif";color:black">Dr. Heather Morrison<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">Associate Professor, School of Information Studies, University of Ottawa<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">Professeur Agrégé, École des Sciences de l'Information, Université d'Ottawa<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">Principal Investigator, Sustaining the Knowledge Commons, a SSHRC Insight Project<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">sustainingknowledgecommons.org<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">Heather.Morrison@uottawa.ca<o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black"><a href="https://uniweb.uottawa.ca/?lang=en#/members/706">https://uniweb.uottawa.ca/?lang=en#/members/706</a><o:p></o:p></span></p>
<p><span style="font-family:"Calibri","sans-serif";color:black">[On research sabbatical July 1, 2019 - June 30, 2020]<o:p></o:p></span></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> goal-bounces@eprints.org <goal-bounces@eprints.org> on behalf
of Martyn Rittman <rittman@mdpi.com><br>
<b>Sent:</b> Wednesday, August 28, 2019 7:02 AM<br>
<b>To:</b> goal@eprints.org <goal@eprints.org><br>
<b>Subject:</b> Re: [GOAL] Informed consent and open licensing: some questions for discussion</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#FF4233">Attention : courriel externe | external email</span></b><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#FF4233"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white">Heather raises a good point here related to certain types of images. MDPI provides a sample consent form (you can access the link e.g. at
<a href="https://www.mdpi.com/journal/ijms/instructions#ethics">https://www.mdpi.com/journal/ijms/instructions#ethics</a>) in which we try to make clear the implications of publishing in open access, but when it comes to reuse there are clearly other rights
that should be enforced for the protection of patients.<br>
<br>
I don't recall a case where this has been flagged as an issue, but we have had similar cases with images taken by someone other than the authors and numerous cases of previously published images where the authors needed permission to republish. Here, a more
restrictive copyright (e.g. all rights reserved) can be applied to the image than to the rest of the text. I would suggest that this could provide a solution in most cases.<br>
<br>
Best regards,<br>
Martyn<br>
<br>
-- <br>
Martyn Rittman, Ph.D.<br>
Publishing Director, MDPI<br>
St. Alban-Anlage 66, 4052 Basel, Switzerland<br>
+41 61 683 77 35<br>
<a href="mailto:rittman@mdpi.com">rittman@mdpi.com</a><br>
<a href="http://www.mdpi.com">www.mdpi.com</a><br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>