all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: emacs-devel@gnu.org
Subject: Re: some emacs history
Date: Fri, 30 Apr 2010 20:03:32 +0200	[thread overview]
Message-ID: <s2oe01d8a51004301103h378130f3xb7ff93d60d258d9a@mail.gmail.com> (raw)
In-Reply-To: <q2ke01d8a51004301102s4549eec2w284fe6ae1586aa69@mail.gmail.com>

Should of course be "It would not be a problem of DOIs if they wer
*NOT* used to point to scientific reports".


On Fri, Apr 30, 2010 at 8:02 PM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> On Fri, Apr 30, 2010 at 7:57 PM, Nelson H. F. Beebe <beebe@math.utah.edu> wrote:
>> Lennart Borgman <lennart.borgman@gmail.com> writes:
>>
>>>> This is a big problem with doi. It may point to hidden resources and
>>>> in fact be totally useless for those who does not have access.
>>
>> I don't view that as a problem peculiar to DOIs; it also applies to
>> URLs, as well as non-electronic services, such as private clubs.
>> Somethings in life are free, but most are not.
>
>
> It would not be a problem of DOIs if they were used to point to
> scientific reports.(I am very doubtful if anything that is not
> available for free should be used as references in scientific works,
> even more since abstracts can be very misleading. But I guess this is
> not the best place to discuss this ;-)
>




  reply	other threads:[~2010-04-30 18:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30  0:39 some emacs history Nelson H. F. Beebe
2010-04-30 13:01 ` Stefan Monnier
2010-04-30 13:30   ` Lennart Borgman
2010-04-30 17:57     ` Nelson H. F. Beebe
2010-04-30 18:02       ` Lennart Borgman
2010-04-30 18:03         ` Lennart Borgman [this message]
2010-04-30 20:58 ` Thomas Lord
2010-04-30 22:28   ` Nelson H. F. Beebe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s2oe01d8a51004301103h378130f3xb7ff93d60d258d9a@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=beebe@math.utah.edu \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.