<HTML>
<HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
Dear Stevan,
<br />
<br />I have no problem with CC-BY-NC-ND. The problem I have with Elsevier's
<br />policy is
<br />
<br />- they require Counter compliance for repositories (I don't know any Counter
<br />compliant repositories, though I see project PIRUS on the Counter website);
<br />
<br />- they definition on non-commercial excludes any non-commercial repositories
<br />providing service for any other (even non-commercial) organisations besides
<br />the parent organisation.
<br />
<br />So practically, as I read it, no repositories comply right now. Certainly not mine.
<br />I had an earlier agreement with Elsevier - I hope it is still holds, but I am not sure.
<br />I can ask, of course, but I feel that individual researchers will again feel (wrongly or
<br />rightly) that they could not deposit, at best they will be uncertain.
<br />
<br />Andras Holl
<br />
<br /><font size="2"><b>On Wed, 27 May 2015 13:44:11 -0400, Stevan Harnad wrote</b>
<br />> I beg the
OA community to remain reasonable and realistic.
<br />>
<br />> <i>Please
don't demand that Elsevier agree to immediate CC-BY. </i>If Elsevier did
that, I could immediately start up a rival free-riding publishing operation and
sell all Elsevier articles immediately at cut rate, for any purpose at all that
I could get people to pay for. Elsevier could no longer make a penny from
selling the content it invested in.
<br />>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;"><a href="https://creativecommons.org/licenses/by-nc-nd/3.0/">CC-BY-NC-ND</a> is
enough for now. It allows immediate harvesting for data-mining.</span>
<br />>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">The OA movement must
stop shooting itself in the foot by over-reaching, insisting on having it all,
immediately, thus instead ending up with next to nothing, as now.</span>
<br />>
<span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">As I pointed out in a
previous posting, <i>the fact that Elsevier requires all authors to
adopt </i></span><span style="font-family: Arial; font-size: 14px; line-height: 19px;"><i>CC-BY-NC-ND license
is a positive step</i>. Please don't force them to
back-pedal!</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">Please read the terms,
and reflect.</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">SH</span>
<br />>
<span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span><blockquote style="margin: 0px 0px 0px 40px; border: medium none; padding: 0px;">
<br />> <h2 style="margin: 0px 0px 22px; padding: 0px; font-size: 14px; line-height: 18px; color: rgb(102, 102, 102); font-family: Helvetica,sans-serif;"><a href="http://www.elsevier.com/about/policies/article-posting-policy#accepted-manuscript">Accepted
Manuscript</a> </h2>
<br />>
<br />> Authors can share their accepted
manuscript:
<br />>
<br />> <strong>Immediately </strong></blockquote>
<br />>
<ul style="margin: 0px 0px 12px 20px; padding: 0px; list-style: none outside none; color: rgb(0, 0, 0); font-family: Helvetica,sans-serif; font-size: 12px; line-height: 18px;">
<ul>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">via their
non-commercial personal homepage or blog.</li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">by updating a <a style="color: rgb(0, 117, 155); text-decoration: none;" class="" href="http://www.elsevier.com/about/open-access/open-access-policies/preprint_lightbox">preprint</a> in
arXiv or RePEc with the accepted manuscript. </li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">via their research
institute or institutional repository for internal institutional uses or as part
of an invitation-only research collaboration work-group.</li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">directly by
providing copies to their students or to research collaborators for their
personal use.</li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">for private scholarly sharing as part of an invitation-only work group on
commercial sites with which Elsevier has an agreement.</li>
</ul>
</ul>
<blockquote style="margin: 0px 0px 0px 40px; border: medium none; padding: 0px;">
<br />> <strong>After
the embargo period </strong></blockquote>
<br />>
<ul style="margin: 0px 0px 12px 20px; padding: 0px; list-style: none outside none; color: rgb(0, 0, 0); font-family: Helvetica,sans-serif; font-size: 12px; line-height: 18px;">
<ul>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">via non-commercial
hosting platforms such as their institutional repository.</li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">via commercial sites
with which Elsevier has an agreement.</li>
</ul>
</ul>
<blockquote style="margin: 0px 0px 0px 40px; border: medium none; padding: 0px;">
<br />> <strong>In all
cases accepted manuscripts should:</strong></blockquote>
<br />>
<ul style="margin: 0px 0px 12px 20px; padding: 0px; list-style: none outside none; color: rgb(0, 0, 0); font-family: Helvetica,sans-serif; font-size: 12px; line-height: 18px;">
<ul>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">Link to the formal
publication via its <a style="color: rgb(0, 117, 155); text-decoration: none;" class="" href="http://www.elsevier.com/about/policies/lightbox-doi">DOI</a>.</li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">Bear a CC-BY-NC-ND
license – this is easy to do, <a style="color: rgb(0, 117, 155); text-decoration: none;" class="" href="http://www.elsevier.com/about/open-access/lightbox_attach-a-user-license">click here</a> to
find out how. </li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">If aggregated with other manuscripts, for example in a repository or other
site, be shared in alignment with our <a style="color: rgb(0, 117, 155); text-decoration: none;" href="http://www.elsevier.com/about/policies/hosting">hosting policy</a>.</li>
<li style="margin: 0px; padding: 0px; list-style: disc outside none;">Not be added to or
enhanced in any way to appear more like, or to substitute for, the published
journal article.</li>
</ul>
</ul>
<blockquote style="margin: 0px 0px 0px 40px; border: medium none; padding: 0px;">
<br />> <h2 style="margin: 0px 0px 15px; padding: 0px; font-size: 14px; line-height: 18px; color: rgb(0, 0, 0); font-family: Helvetica,sans-serif;"><a href="http://www.elsevier.com/about/open-access/lightbox_attach-a-user-license">How
to attach a user license</a></h2>
<br />>
<br />> Elsevier requires authors
posting their accepted manuscript to attach a non-commercial Creative Commons
user license (CC-BY-NC-ND). This is easy to do. On your accepted manuscript
add the following to the title page, copyright information page, or header
/footer: © YEAR, NAME. Licensed under the Creative Commons [insert license
details and URL].
<br />>
<br />> For example: © 2015, Elsevier. Licensed
under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0
International <a style="color: rgb(0, 117, 155); text-decoration: none; background-image: url("https://www.elsevier.com/__data/assets/image/0019/685/small.png?v=0.1.11?v=0.1.11"); background-color: transparent; padding-right: 12px; background-repeat: no-repeat no-repeat;" class="" href="http://creativecommons.org/licenses/by-nc-nd/4.0/">http://creativecommons.org/licenses/by-nc-nd/4.0/</a>
<br />>
<br />> You can also include the license badges available from the <a style="color: rgb(0, 117, 155); text-decoration: none; background-image: url("https://www.elsevier.com/__data/assets/image/0019/685/small.png?v=0.1.11?v=0.1.11"); background-color: transparent; padding-right: 12px; background-repeat: no-repeat no-repeat;" class="" target="_blank" href="http://creativecommons.org/about/downloads">Creative Commons website</a> to provide visual recognition. If you
are hosting your manuscript as a webpage you will also find the correct HTML
code to add to your page</blockquote>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span>
<br />> <span style="font-family: Arial; font-size: 14px; line-height: 19px;">
<br />>
</span>
<br />>
<br />> On Wed, May 27, 2015 at 12:37 PM, Kathleen
Shearer <span dir="ltr"><<a target="_blank" href="mailto:m.kathleen.shearer@gmail.com">m.kathleen.shearer@gmail.com</a>></span> wrote:
<br />>
<blockquote style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
<br />>
<br />> <font face="Arial"><span style="font-size: 14px; line-height: 19px;">(sorry
for any cross-posting)</span></font>
<br />> <span style="font-size: 14px; font-family: Arial; line-height: 1.38; text-align: justify; vertical-align: baseline;">
<br />>
</span>
<br />> <span style="font-size: 14px; font-family: Arial; line-height: 1.38; text-align: justify; vertical-align: baseline;">In
its recently released “Sharing and Hosting Policy FAQ”, Elsevier
“recognize(s) that authors want to share and promote their work and
increasingly need to comply with their funding body and institution's open
access policies.” However there are several aspects of their new policy that
severely limit sharing and open access, in particular the lengthy embargo
periods imposed in most journals- </span><span style="font-size: 14px; font-family: Arial; line-height: 1.38; text-align: justify; vertical-align: baseline;">with
about <a target="_blank" href="http://www.elsevier.com/__data/assets/pdf_file/0018/121293/external-embargo-list.pdf">90% of Elsevier journals</a> having embargo periods of 12
months or greater. This is a significant rollback from the original 2004
Elsevier policy which required no embargos for making author’s accepted
manuscripts available; and even with the 2012 policy change requiring embargoes
only when authors were subject to an OA mandate.</span>
<br />> <font face="Arial" style="font-size: 14px;">
<br />> </font>
<br />> <font face="Arial" style="font-size: 14px;"><span style="vertical-align: baseline;">With article
processing charges (APCs) that can cost as much as </span><span style="vertical-align: baseline;"><a target="_blank" href="https://www.elsevier.com/journal-authors/open-access/sponsored-articles"><span style="vertical-align: baseline;"><font color="#0042aa">$5000 US dollars</font></span></a> for publishing in one of
Elsevier’s gold open access titles or hybrid journals, this is not a viable
option for many researchers around the world. Furthermore, the rationale for
lengthy embargo periods is to protect Elsevier’s subscription revenue. We do
not believe that scientific, economic and social progress should be hindered in
order to protect commercial interests. In addition, t</span><span style="line-height: 1.38;">here is currently no evidence that articles made
available through OA repositories will lead to cancellations.</span><span style="line-height: 1.38;"> </span></font>
<br />> <span style="vertical-align: baseline; font-size: 14px;"><font face="Arial">
<br />>
</font></span>
<br />> <font face="Arial" style="font-size: 14px;"><span style="vertical-align: baseline;">Elsevier’s new policy also requires that
accepted manuscripts posted in open access repositories bear a CC-BY-NC-ND
license. This type of license severely limits the re-use potential of publicly
funded research. ND restricts the use of derivatives, yet derivative use
is </span><a style="line-height: 1.38; text-decoration: none;" target="_blank" href="http://oaspa.org/why-cc-by/"><span style="text-decoration: underline; vertical-align: baseline;">fundamental</span></a><span style="vertical-align: baseline;"> to the way in which scholarly research builds
on previous findings, for example by re-using a part of an article (with
attribution) in educational material. Similarly, this license restricts
commercial re-use greatly </span><a style="line-height: 1.38; text-decoration: none;" target="_blank" href="http://www.kuro5hin.org/story/2005/9/11/16331/0655"><span style="text-decoration: underline; vertical-align: baseline;">inhibiting</span></a><span style="vertical-align: baseline;"> the potential impact of the results of
research.</span></font>
<br />> <font face="Arial" style="font-size: 14px;">
<br />> </font>
<br />> <font face="Arial" style="font-size: 14px;"><span style="vertical-align: baseline;">Elsevier’s
Director of Access & Policy, Alicia Wise states that they “have received
neutral-to-positive responses from research institutions and the wider research
community.” Yet, since the “</span><a style="text-decoration: none;" target="_blank" href="https://www.coar-repositories.org/activities/advocacy-leadership/petition-against-elseviers-sharing-policy/"><span style="text-decoration: underline; vertical-align: baseline;">Statement against
Elsevier’s sharing policy</span></a><span style="vertical-align: baseline;">”
was published just one week ago (on Wednesday May 20, 2015), it has been signed
by close to 700 organizations and individuals, demonstrating that there is
significant opposition to the policy.</span></font><font face="Arial" style="font-size: 14px;">
<br />> </font>
<br />> <span style="vertical-align: baseline; font-size: 14px;"><font face="Arial">Elsevier has
indicated that they “are always happy to have a dialogue to discuss these, or
any other, issues further.” We would like to offer the following concrete
recommendations to Elsevier to improve their policy:</font></span>
<ol style="margin-top: 0pt; margin-bottom: 0pt;">
<li style="list-style-type: decimal; vertical-align: baseline;" dir="ltr">
<br />> <span style="vertical-align: baseline; font-size: 14px;"><font face="Arial">Elsevier
should allow all authors to make their “author’s accepted manuscript”
openly available immediately upon acceptance through an OA repository or
other open access platform.</font></span></li>
<li style="list-style-type: decimal; vertical-align: baseline;" dir="ltr">
<br />> <span style="vertical-align: baseline; font-size: 14px;"><font face="Arial">Elsevier
should allow authors to choose the type of open license (from CC-BY to other
more restrictive licenses like the CC-BY-NC-ND) they want to attach to the
content that they are depositing into an open access
platform.</font></span></li>
<li style="list-style-type: decimal; vertical-align: baseline;" dir="ltr">
<br />> <span style="vertical-align: baseline; font-size: 14px;"><font face="Arial">Elsevier
should not attempt to dictate author’s practices around individual sharing of
articles. Individual sharing of journal articles is already a scholarly norm and
is protected by fair use and other copyright exceptions. Elsevier cannot, and
should not, dictate practices around individual sharing of
articles.</font></span></li>
</ol>
<br />> <font face="Arial" style="font-size: 14px;"><span style="vertical-align: baseline;">We strongly
encourage Elsevier to revise their policy in order to better align with the
interests of the research community. </span>We would also be pleased to meet to
discuss these recommendations with Elsevier at any time.</font><font face="Arial" style="font-size: 14px;">
<br />>
<br />> </font>
<br />> <span style="vertical-align: baseline; font-size: 14px;"><font face="Arial">Kathleen
Shearer, Executive Director, COAR</font></span>
<br />> <span style="line-height: 1.38; font-size: 14px;"><font face="Arial">
<br />>
</font></span>
<br />> <span style="line-height: 1.38; font-size: 14px;"><font face="Arial">Heather Joseph, Executive Director, SPARC</font></span>
<br />>
<br />> <blockquote type="cite">
<br />>
<br />> On Thu, May 21, 2015 at 12:05
PM, Wise, Alicia (ELS-OXF) <span dir="ltr"><<a target="_blank" href="mailto:A.Wise@elsevier.com">A.Wise@elsevier.com</a>></span> wrote:
<br />> <blockquote style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
<br />>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;">Hello
everyone –</span>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;"> </span>
<br />>
<br />>
<span style="font-size: 11pt; font-family: Calibri,sans-serif;">Just a quick note to
draw your attention to our article, posted today in Elsevier Connect and in
response to yesterday’s statement by COAR: <a target="_blank" href="http://www.elsevier.com/connect/coar-recting-the-record">http://www.elsevier.com/connect/coar-recting-the-record</a><span style="color: rgb(31, 73, 125);">. </span>I’ll also append the full text of
this response below.</span>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;"> </span>
<br />>
<br />>
<span style="font-size: 11pt; font-family: Calibri,sans-serif;">You might also be
interested in this Library Connect webinar on some of the new institutional
repository services we are piloting (<a target="_blank" href="http://libraryconnect.elsevier.com/articles/2015-01/webinar-institutional-research-repositories-characteristics-relationships-and-roles">http://libraryconnect.elsevier.com/articles/2015-01/webinar-institutional-research-repositories-characteristics-relationships-and-roles</a>)
and reading our policies for yourselves:</span>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;"> </span>
<br />>
<ul type="disc" style="margin-top: 0in;">
<li class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri,sans-serif;">Sharing – <a target="_blank" href="http://www.elsevier.com/about/policies/article-posting-policy">http://www.elsevier.com/about/policies/article-posting-policy</a></span></li>
<li class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri,sans-serif;">Hosting - <a target="_blank" href="http://www.elsevier.com/about/policies/hosting">http://www.elsevier.com/about/policies/hosting</a></span></li>
</ul>
<br />>
<span style="font-size: 11pt; font-family: Calibri,sans-serif;"> </span>
<br />>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;">With best
wishes,</span>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;">Alicia</span>
<br />>
<b><span style="font-size: 13.5pt; font-family: Arial,sans-serif;">COAR-recting the
record</span></b>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">We have received
neutral-to-positive responses from research institutions and the wider research
community. We are therefore a little surprised that COAR has formed such a
negative view, and chosen not to feedback their concerns directly to us. We
would like to correct the misperceptions.</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">Our sharing policy is more
liberal in supporting the dissemination and use of research: </span>
<ul type="disc">
<li><span style="font-size: 11pt; font-family: Verdana,sans-serif;">At
each stage of the publication process authors can share their research: before
submission, from acceptance, upon publication, and post
publication. </span></li>
<li><span style="font-size: 11pt; font-family: Verdana,sans-serif;">In institutional
repositories, which no longer require a formal agreement to host full text
content</span></li>
<li style="line-height: 15pt;"><span style="font-size: 11pt; font-family: Verdana,sans-serif;">Authors can also share on
commercial platforms such as social collaboration networks</span></li>
<li style="line-height: 15pt;"><span style="font-size: 11pt; font-family: Verdana,sans-serif;">We provide new services to
authors such as the share link which enables authors to post and share a
customized link for 50 days free access to the final published
article </span></li>
<li style="line-height: 15pt;"><span style="font-size: 11pt; font-family: Verdana,sans-serif;">For authors who want free
immediate access to their articles, we continue to give all authors a choice to
publish gold open access with a wide number of open access journals and over
1600 hybrid titles </span></li>
</ul>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">Unlike the claims in this
COAR document, the policy changes are based on feedback from our authors and
institutional partners, they are evidence-based, and they are in alignment with
the STM article sharing principles. They introduce absolutely no changes in
our embargo periods. And they are not intended to suddenly embargo and make
inaccessible content currently available to readers – as we have already
communicated in </span><span style="font-size: 11pt; font-family: Calibri,sans-serif;"><a target="_blank" href="http://www.elsevier.com/connect/elsevier-updates-its-policies-perspectives-and-services-on-article-sharing"><span style="font-family: Verdana,sans-serif;">Elsevier
Connect</span></a></span><span style="font-size: 11pt; font-family: Verdana,sans-serif;">.</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">In fact, we have been
developing services, in partnership with libraries, to help institutional
repositories track research output and display content to their users. This
includes:</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">•<span style="font-size: 7pt;"> </span></span><span style="font-size: 11pt; font-family: Verdana,sans-serif;">Sharing metadata: In order
to showcase an institutions’ work, an institutional repository must identify
their institution’s research output. By integrating the ScienceDirect metadata
API into the repository, this task becomes simple. Even in cases where the
repository doesn’t hold the full text manuscript, the article information and
abstract can be displayed..</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">•<span style="font-size: 7pt;"> </span></span><span style="font-size: 11pt; font-family: Verdana,sans-serif;">Sharing user access
information and embedding final articles: We are testing a workflow in which a
user’s access level to the full text is checked on the fly, and if full text
access is available, the user will be served the final published version,
instead of the preprint or manuscript hosted by the repository. Users who are
not entitled to view the full text of the final article will be led to the
version available in the repository, or- if this is not available- to a page
where they can view the first page of the article and options for accessing it
(including via interlibrary loan). This ensures that users will always be served
the best available version. This also enables the repository to display the best
available version to their users even if no self-archived manuscript is
available.</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">We have not only updated
our policies, we are active in developing and delivering technology that enables
research to be shared more widely.</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">COAR states that the
addition of a CC-BY-NC-ND license is unhelpful. Feedback suggests that clarity
about how manuscripts can be used is welcome, </span><span style="font-size: 11pt; font-family: Verdana,sans-serif;">when asked in surveys
often choose NC ND of their own volition (see the T&F study from 2014 at<a target="_blank" href="http://www.tandf.co.uk/journals/explore/open-access-survey-june2014.pdf">http://www.tandf.co.uk/journals/explore/open-access-survey-june2014.pdf</a> ),
and it works across a broad range of use cases.</span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">Our refreshed policies are
about green OA, and some elements of this – for example the use of embargo
periods – are specifically for green OA when it is operating in tandem with
the subscription business model. Here time is needed for the subscription
model to operate as libraries will understandably not subscribe if this material
is available immediately and for free. </span>
<br />> <span style="font-size: 11pt; font-family: Verdana,sans-serif;">In closing, we appreciate
an open dialogue and are always happy to have a dialogue to discuss these, or
any other, issues further. </span>
<br />> <span style="font-size: 10pt; font-family: Arial,sans-serif; color: rgb(127, 127, 127);">Dr
Alicia Wise</span>
<br />> <span style="font-size: 10pt; font-family: Arial,sans-serif; color: rgb(127, 127, 127);">Director
of Access and Policy</span>
<br />> <span style="font-size: 10pt; font-family: Arial,sans-serif; color: rgb(255, 153, 0);">Elsevier </span><span style="font-size: 10pt; font-family: Arial,sans-serif; color: gray;">I The Boulevard I
Langford Lane I Kidlington I Oxford I OX5 1GB</span><span style="font-family: Arial,sans-serif; color: gray;"></span>
<br />> <span style="font-size: 10pt; font-family: Arial,sans-serif; color: gray;">M: <a target="_blank" value="+447823536826" href="tel:%2B44%20%280%29%207823%20536%20826">+44 (0) 7823 536 826</a> I E: <a target="_blank" href="mailto:a.wise@elsevier.com">a.wise@elsevier.com</a></span>
<br />> <b><span style="font-size: 10pt; font-family: Arial,sans-serif; color: gray;">Twitter:
@wisealic</span></b>
<br />> <span style="font-size: 11pt; font-family: Calibri,sans-serif;"> </span>
<br />>
<br />>
<span style="font-size: 11pt; font-family: Calibri,sans-serif; color: rgb(31, 73, 125);"> </span>
<br />>
<br />>
<hr />
<br />> <span style="font-size: 10pt; font-family: Arial,sans-serif;">Elsevier Limited. Registered
Office: The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United
Kingdom, Registration No. 1982084, Registered in England and Wales.</span>
<br clear="none" /></blockquote>
<br />>
_______________________________________________
<br />> GOAL mailing
list
<br />> <a target="_blank" href="mailto:GOAL@eprints.org">GOAL@eprints.org</a>
<br />> <a target="_blank" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal</a>
<br />>
</blockquote>
<br />>
<br />>
_______________________________________________
<br />> GOAL mailing
list
<br />> <a href="mailto:GOAL@eprints.org">GOAL@eprints.org</a>
<br />> <a target="_blank" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal</a>
<br />>
<br />>
</blockquote>
<br />
<br />
<br />--------------------------------------------------------------------------------
<br />
Andras Holl / Holl Andras
e-mail: holl@konkoly.hu
<br />
Konkoly Observatory / MTA CsFK CsI Tel.: +36 1 3919368 Fax:
+36 1 2754668
<br />
IT advisor / Szamitastechn. koordinator Mail: H1525 POBox 67, Budapest,
Hungary
<br />
--------------------------------------------------------------------------------
<br />
<br />
</font>
</BODY>
</HTML>