From: Gerald Pfeifer <gerald@pfeifer.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [libstdc++,doc] doc/xml/manual/profile_mode.xml: Update a paper reference
Date: Mon, 20 Feb 2017 13:56:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1702201411540.2410@anthias.pfeifer.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702102351350.25339@digraph.polyomino.org.uk>
On Fri, 10 Feb 2017, Joseph Myers wrote:
>> - <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://dx.doi.org/10.1109/CGO.2009.36">paper presented at
>> + <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://ieeexplore.ieee.org/document/4907670/">paper presented at
> dx.doi.org is specifically supposed to provide permanent URLs that
> continue to work even if e.g. a journal changes publisher and the
> old publisher fails to redirect for individual papers itself. I'm
> not convinced that replacing a link to such a URL with a link to the
> current redirection target is a good idea.
You make a good point, Joseph, though I'd argue that my trust in
ieee.org being around ten years from now exceed my trustin dx.doi.org
(especially after the citeseer cleanup I ended up working last weekend).
For now I am thinking to keep this link (to ieee.org), but have started
to convert all citeseer references to dx.doi.org and copied you on my
initial patch in that direction. Let's hope that service is going to
remain stable and reliable.
One aspect I do not like too much about such a forwarding service is
that it means one of the benefits of link checking (discovering a site
we point to going rogue) is quite reduced since every link to dx.doi.org
is going to redirect, by definition.
(Note, that is not an academic concern. We've had such cases in the
past.)
Gerald
prev parent reply other threads:[~2017-02-20 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 23:11 Gerald Pfeifer
2017-02-11 0:20 ` Joseph Myers
2017-02-20 13:56 ` Gerald Pfeifer [this message]
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=alpine.LSU.2.20.1702201411540.2410@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).