Any transport protocol would seem fine provided that the author's active
consent is incorporated into the process for each personal request.
Unfortunately, HTTP doesn't work that way. I suppose the system could
instead send a unique authentication code by email to the person who
wanted to see it by HTTP whereas normally it would be restricted, but it
would have to work only once in case they shared it against the author's
wishes - so what would be the advantage over sending it by email? Unless
of course one has an account on the repository or another linked
service, again requiring the author's permission - but are people really
going to use one FB-type service for academia and request/give
permissions through it? Isn't it simpler to use email?
Ian Stuart wrote:
> Ricky Rankin wrote:
>> Sorry to return to this.
>>
>> As I understand the arguement goes that by including a eprint request
>> link/button it is OK to email the publishers pdf as this is the same
>> as sending a copy through the post.
>>
>> A computing colleague has asked why is ths different than displaying
>> the pdf on the screen of the requester's screen as http is just
>> another transport protocol?
> The difference is that the paper is not Openly available: The author
> of the paper makes a concious decision to produce a copy for a fellow
> academic
>
> An Open Access (true Open Access) article would have the paper
> available without restriction.
>
--
Dr Talat Chaudhri
------------------------------------------------------------
Research Officer
UKOLN, University of Bath, Bath BA2 7AY, Great Britain
Telephone: +44 (0)1225 385105 Fax: +44 (0)1225 386838
E-mail: [log in to unmask] Skype: talat.chaudhri
Web: http://www.ukoln.ac.uk/ukoln/staff/t.chaudhri/
------------------------------------------------------------
|