[rfc-i] DOIs
duerst at it.aoyama.ac.jp ( "Martin J. Dürst" ) Wed, 27 January 2010 03:18 UTC
From: "duerst at it.aoyama.ac.jp"
Date: Wed, 27 Jan 2010 12:18:10 +0900
Subject: [rfc-i] DOIs
In-Reply-To: <4B5F9B11.9060509@gmx.de>
References: <4B5F50B7.2080104@gmx.de> <D4F73C27-8249-4149-9C6D-10F4F1FC5095@cs.columbia.edu> <4B5F5C2D.1080404@isi.edu> <A287BB9F-B035-4A08-A313-E8A31098E2F9@cs.columbia.edu> <4B5F619C.9090602@gmail.com> <40912775-8116-49AC-B4E0-7C3B2DC4B3DE@cs.columbia.edu> <4B5F8DC4.9050007@gmx.de> <FDC4DEF6-7467-453F-A111-67CD265DB351@cs.columbia.edu> <4B5F977F.5010300@gmx.de> <7419D8B2-D277-4A3D-83FD-9D2E88EB43CE@cs.columbia.edu> <4B5F9B11.9060509@gmx.de>
Message-ID: <4B5FB072.2080307@it.aoyama.ac.jp>
I'm working in an academic context in Japan. I'd say that most of our faculty and even more of our students never heard about DOI. When searching, it's first everyday search engines, then maybe Google scholar, then the library-specific stuff. For me personally, as mentioned, DOIs are associated with bean counting, and we don't need bean counting for RFCs. I wouldn't mind if somebody worked on getting DOIs for RFCs for those who like DOIs, but I'd oppose to declaring them as "canonical" for RFCs. I once attended a talk by Bob Kahn. Very interesting, but there was one thing where I couldn't disagree more. He presented the way content should be dealt with as if bean counting in doi: style were the correct thing, and open accessibility as the Web brought it was mostly a mistake. I'm not sure I remember correctly, but I think he pointed to DOI as the way to fix things. I don't mind some people or organizations using the bean counting style, but Somebody mentioned urn: doesn't work on Safari. I guess doi: won't either. Looking at https://datatracker.ietf.org/idtracker/draft-paskin-doi-uri/, it seems an attempt to get a doi: URI scheme failed, but I might be wrong, and I don't know why. doi: is mentioned in a few places, e.g. http://en.wikipedia.org/wiki/URI_scheme. On 2010/01/27 10:46, Julian Reschke wrote: > Henning Schulzrinne wrote: >> I don't know where you work, and this may well be more of a US/North >> American thing than a European one (although Springer, being more of a >> European publisher, uses them for their journals, too), but they are >> pretty standard currency in academic research, which is presumably the >> area where long-term-useful citations matter. >> ... > > I'm working on Internet stuff. Surprise. > > The question that triggered my request was raised by the W3C, btw. For W3C purposes, what I would currently recommend is http://tools.ietf.org/html/rfc[0-9]+. This is really great in that it shows a faithful representation of the official ASCII version while also providing a bit of metadata and linking wherever possible (inside the document, to other documents, and from other documents to specific pieces of the document). It also prints very nicely with a lot of software (even modern stuff that no longer knows about form feeds). There are still however some problems with this: - It's on the 'tools' site, which is getting more and more convenient but doesn't have that much of an official standing. - It has /html/ in the path, which is as wrong as .txt in the extension. - It's created by a mechanical process that not always gets things 100% right. So in my view, the ideal would be: - http://www.ietf.org/rfc/rfc[0-9]+ and/or http://www.rfc-editor/rfc/rfc[0-9]+ serve the format currently served at tools.ietf.org together with the .txt format with content negotiation. - This (these) are declared canonical locations Regards, Martin. -- #-# Martin J. D?rst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Henning Schulzrinne
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Henning Schulzrinne
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] DOIs Brian E Carpenter
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] DOIs Keith Moore
- [rfc-i] "canonical" URI for RFCs, BCPs Brian E Carpenter
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Tim Bray
- [rfc-i] DOIs Henning Schulzrinne
- [rfc-i] DOIs Julian Reschke
- [rfc-i] DOIs Henning Schulzrinne
- [rfc-i] DOIs Julian Reschke
- [rfc-i] DOIs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] DOIs Henning Schulzrinne
- [rfc-i] DOIs Tim Bray
- [rfc-i] DOIs Julian Reschke
- [rfc-i] DOIs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] DOIs "Martin J. Dürst"
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] DOIs Colin Perkins
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Brian E Carpenter
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Brian E Carpenter
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Brian E Carpenter
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Brian E Carpenter
- [rfc-i] "canonical" URI for RFCs, BCPs John Levine
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs John R Levine
- [rfc-i] "canonical" URI for RFCs, BCPs Paul Hoffman
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs Tim Bray
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs Tim Bray
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs John R Levine
- [rfc-i] "canonical" URI for RFCs, BCPs Tim Bray
- [rfc-i] "canonical" URI for RFCs, BCPs Joe Touch
- [rfc-i] "canonical" URI for RFCs, BCPs John R Levine
- [rfc-i] "canonical" URI for RFCs, BCPs John R Levine
- [rfc-i] "canonical" URI for RFCs, BCPs Alfred Hönes
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke
- [rfc-i] "canonical" URI for RFCs, BCPs "Martin J. Dürst"
- [rfc-i] "canonical" URI for RFCs, BCPs "Martin J. Dürst"
- [rfc-i] "canonical" URI for RFCs, BCPs Bob Braden
- [rfc-i] "canonical" URI for RFCs, BCPs Julian Reschke