<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=us-ascii">
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Grande";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{mso-style-priority:99;
mso-style-link:"Footnote Text Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
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;}
span.FootnoteTextChar
{mso-style-name:"Footnote Text Char";
mso-style-priority:99;
mso-style-link:"Footnote Text";
font-family:"Calibri","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">Dear Kathleen
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">There is a tremendous difference between
</span><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">“open access” and “free to read”.
</span></b><span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">You can’t simply state
</span><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Use the term “open access” instead of “free to read”: <o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif"">I can’t see how this can be the official statement from COAR.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Yours sincerely<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Wouter Gerritsma</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","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-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> goal-bounces@eprints.org [mailto:goal-bounces@eprints.org]
<b>On Behalf Of </b>Kathleen Shearer<br>
<b>Sent:</b> dinsdag 4 februari 2014 18:12<br>
<b>To:</b> Global Open Access List (Successor of AmSci)<br>
<b>Subject:</b> [GOAL] COAR Comments on NISO's Open Access Metadata and Indicators<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Dear OA community,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt">I thought some of you may be interested in COAR's comments on NISO's </span><a href="http://www.niso.org/apps/group_public/document.php?document_id=12047"><span style="font-size:10.0pt">draft Open Access Metadata
and Indicators</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">COAR's Comments on NISO's Open Access Metadata and Indicators</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:18.0pt;font-family:"Helvetica","sans-serif"">The Confederation of Open Access Repositories (COAR) supports NISO’s efforts to harmonize the expression of open
access and re-use rights for publications. We strongly believe that it would be very beneficial to have a common approach to these indicators across the entire scholarly community.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">COAR is an international association of repository initiatives representing over 100 organizations in 35 countries
on 4 continents (Asia, Europe, North America and South America). </span><span lang="EN-CA" style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Our mission is to enhance the visibility and application of research outputs through a global network of
Open Access digital repositories. COAR’s members represent an important stakeholder community, as they would be tasked with adapting to any such community standard within the context of their repositories. </span><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">To
that end, we have a number of specific comments that we invite the NISO working group to consider.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Adopt a common vocabulary within the context of existing metadata schemas, instead of creating new metadata
elements: </span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">In principal, COAR concurs that there should be a clear distinction between the expression of access status and associated rights. However, we have strong concerns with
the proposal to introduce new metadata elements in order to express these concepts. Most existing metadata schemas already have elements for expressing rights (for example, the rights element in Dublin Core). Instead of introducing new metadata elements, which
will be extremely onerous for the community to adopt, COAR proposes the adoption of a common vocabulary that can be implemented into elements within existing metadata schemas. COAR and other stakeholders in the repository community are already maintaining
the “</span><span lang="EN-CA" style="font-size:13.5pt;font-family:"Helvetica","sans-serif""><a href="https://www.coar-repositories.org/activities/repository-interoperability/ig-controlled-vocabularies-for-repository-assets/"><span lang="EN-US">info:eu-repo</span></a></span><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">”
vocabulary</span><a name="_ftnref1"></a><a href="x-msg://1316/#_ftn1" title=""><span class="MsoFootnoteReference"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">[1]</span></span></a><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif""> that
could promote the use of standard vocabulary elements around open access. In addition, any described standards should also be compatible with more detailed and extensive metadata formats beyond Dublin Core (for example MODS, MARCXML or CERIF) and should be
checked in this respect.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Use the term “open access” instead of “free to read”: </span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Open
access is a term widely used and understood in the scholarly community and has become the standard terminology. COAR sees no value in adopting a new term. Rather a new term, free to read, will only serve to obfuscate the issue.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">There should be no end dates for “free to read” (or “open access”) indicator: </span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">By
allocating an end date to the “free to read” element, the working group is confusing open access content with promotional material (that may be made available for a short time and then attached with a fee). This practice would go against normal and best practice
of the scholarly community. Open access (free to read), by its very nature, can be embargoed for a time, but once it has been made available without a fee, cannot be put again behind a pay wall.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">More repository use cases should be included: </span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">There
are two major options for providing open access to articles: open access journals and open access repository. The NISO recommendations fail to take into account the range of indicators that are required in the repository context. For example, in their current
form, there is no way to express who the copyright holder is or distinguish between pre-prints from post-prints. Furthermore, there is a significant portion of content in repositories that lacks a URI with information about re-use rights. Current repository
platforms have already implemented much more sophisticated approaches to rights expression than the ones recommended by NISO. These may have to be drastically altered if current indicators are adopted. In terms of next steps, we strongly urge the working group
to consider designing a simple mapping or crosswalk that would allow repositories to join into this harmonization effort. In addition, more repository use cases should be taken into account as the recommendations are adapted and implemented, and NISO should
broaden its working group to include greater representation from the repository community.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Widen the scope of recommendations: </span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">End
users of repositories need transparent information on the access conditions for all types of material in their collections. The NISO draft emphasizes content and scholarly works, terms that imply a wide range of content types beyond publications. However,
as acknowledged by NISO (pg. 2), these indicators do not take into account the characteristics of a range research outputs including datasets. Research data is increasingly recognized as an important scholarly output, valuable on its own or in connection with
publications. It is clear that the issue of access to research data is difficult to describe with a simple "free-to-read" tag, or similar. Taking all this in consideration COAR suggests that any recommended practice should also address research data.</span><o:p></o:p></p>
<div>
<div class="MsoNormal">
<hr size="1" width="33%" align="left">
</div>
<div id="ftn1">
<p class="MsoFootnoteText"><a name="_ftn1"></a><a href="x-msg://1316/#_ftnref1" title=""><span class="MsoFootnoteReference"><span lang="EN-CA" style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">[1]</span></span></a><span lang="EN-CA" style="font-size:13.5pt;font-family:"Helvetica","sans-serif""> <a href="https://www.coar-repositories.org/activities/repository-interoperability/ig-controlled-vocabularies-for-repository-assets/">https://www.coar-repositories.org/activities/repository-interoperability/ig-controlled-vocabularies-for-repository-assets/</a></span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Kathleen Shearer<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black">Executive Director, COAR<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black"><a href="mailto:kathleen.shearer@coar-repositories.org">kathleen.shearer@coar-repositories.org</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black"><a href="http://www.coar-repositories.org">www.coar-repositories.org</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black">Skype: kathleen.shearer2<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black">+1 514 847 9068<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Lucida Grande","serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>