Re: [rfc-i] Referencing RFCs
"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Tue, 13 June 2017 21:03 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65C12128B90 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 13 Jun 2017 14:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OsHmIqWQUnNS for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 13 Jun 2017 14:03:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DCD81286D6 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 13 Jun 2017 14:03:38 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BAE6DB80D4A; Tue, 13 Jun 2017 14:03:26 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 38F94B80D4A for <rfc-interest@rfc-editor.org>; Tue, 13 Jun 2017 14:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yT8D3sFVqvGq for <rfc-interest@rfc-editor.org>; Tue, 13 Jun 2017 14:03:24 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 130F5B80D48 for <rfc-interest@rfc-editor.org>; Tue, 13 Jun 2017 14:03:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6D2591C52E7 for <rfc-interest@rfc-editor.org>; Tue, 13 Jun 2017 14:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FcDtkuaHwkZI for <rfc-interest@rfc-editor.org>; Tue, 13 Jun 2017 14:03:25 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (c-50-159-75-65.hsd1.wa.comcast.net [50.159.75.65]) by c8a.amsl.com (Postfix) with ESMTPSA id 417251C5013 for <rfc-interest@rfc-editor.org>; Tue, 13 Jun 2017 14:03:25 -0700 (PDT)
To: rfc-interest@rfc-editor.org
References: <148916689952.6827.6792653811413720687.idtracker@ietfa.amsl.com> <383fa41c-e289-8045-7c1f-fcdcd8cc8445@rfc-editor.org> <eeb2d9b5-a28a-df26-7f7e-0dbe92a263f8@gmx.de> <ed8e0bd3-0b54-2ca5-2069-ce7460a5c981@gmx.de>
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Message-ID: <ae5dd220-0301-2d8b-1517-c3364f199d6c@rfc-editor.org>
Date: Tue, 13 Jun 2017 14:03:34 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <ed8e0bd3-0b54-2ca5-2069-ce7460a5c981@gmx.de>
Content-Language: en-US
Subject: Re: [rfc-i] Referencing RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
On 3/11/17 7:43 AM, Julian Reschke wrote: > On 2017-03-11 16:04, Julian Reschke wrote: >> <https://tools.ietf.org/html/draft-flanagan-7322bis-00#section-4.8.6.2>: >> >>> [RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core," >>> IETF, RFC 3080, DOI 10.17487/RFC3080, March 2001, http://www.rfc- >>> editor.org/info/rfc3080 . >> >> I see two chaanges from RFC 7322 here: >> >> 1) The addition of the stream name (which I believe is a good change). >> In V3, this could be implemented using (a) >> <https://greenbytes.de/tech/webdav/rfc7991.html#element.refcontent> or >> (b) using >> <https://greenbytes.de/tech/webdav/rfc7991.html#element.seriesInfo.attribute.stream>: >> >> >> >> a) would look like: >> >> <reference anchor='RFC3080' >> target='http://www.rfc-editor.org/info/rfc3080'> >> <front> >> <title>The Blocks Extensible Exchange Protocol Core</title> >> <author initials='M.' surname='Rose' fullname='M. Rose'/> >> <date year='2001' month='March' /> >> </front> >> <refcontent>IETF</refconfent> >> <seriesInfo name='RFC' value='3080'/> >> <seriesInfo name='DOI' value='10.17487/RFC3080'/> >> </reference> >> >> b) would look like: >> >> <reference anchor='RFC3080' >> target='http://www.rfc-editor.org/info/rfc3080'> >> <front> >> <title>The Blocks Extensible Exchange Protocol Core</title> >> <author initials='M.' surname='Rose' fullname='M. Rose'/> >> <date year='2001' month='March' /> >> </front> >> <seriesInfo name='RFC' value='3080' stream='IETF'/> >> <seriesInfo name='DOI' value='10.17487/RFC3080'/> >> </reference> >> >> Both format require changes to the citations library. >> >> Format (b) has the drawback of being ambiguous, because multiple >> seriesInfo elements might carry conflicting information. We'd also have >> to define the special cases, both for the vocabulary (what if a W3C >> document says stream="IETF"???) and the HTML spec. >> >> 2) The URI appears without angle brackets. I'll guess that's a >> formatting error caused by xml2rfc not processing the <eref> in the >> source as intended. > > and 3): what exactly should go in for the independent stream? > > "independent" (the same thing we have in submissionType) -Heather _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Fwd: New Version Notification for draft-f… Heather Flanagan (RFC Series Editor)
- [rfc-i] Errata Reference Format Julian Reschke
- [rfc-i] Referencing Emails Julian Reschke
- [rfc-i] Placement of Index Julian Reschke
- [rfc-i] Referencing Internet Drafts Julian Reschke
- [rfc-i] Referencing RFCs Julian Reschke
- [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing RFCs Julian Reschke
- Re: [rfc-i] Placement of Index Martin J. Dürst
- Re: [rfc-i] Fwd: New Version Notification for dra… Julian Reschke
- Re: [rfc-i] Fwd: New Version Notification for dra… Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Julian Reschke
- Re: [rfc-i] Errata Reference Format Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Emails Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Placement of Index Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing RFCs Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing Emails Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Carsten Bormann
- Re: [rfc-i] Referencing Internet Drafts Brian E Carpenter
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Bob Hinden
- Re: [rfc-i] Referencing STDs and BCPs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Emails Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing RFCs Julian Reschke
- Re: [rfc-i] Referencing Emails Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Jim Schaad
- Re: [rfc-i] Referencing Internet Drafts Paul Kyzivat
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing STDs and BCPs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Emails Carsten Bormann
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Bob Hinden
- Re: [rfc-i] Referencing Internet Drafts Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Referencing Internet Drafts Paul Kyzivat
- Re: [rfc-i] Referencing STDs and BCPs Julian Reschke
- Re: [rfc-i] Referencing Internet Drafts Brian E Carpenter
- Re: [rfc-i] Referencing Internet Drafts Andrew Sullivan
- Re: [rfc-i] Referencing Internet Drafts Brian E Carpenter
- Re: [rfc-i] Referencing Internet Drafts Bob Hinden
- Re: [rfc-i] Fwd: New Version Notification for dra… Julian Reschke
- Re: [rfc-i] Fwd: New Version Notification for dra… Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Martin Thomson
- Re: [rfc-i] Errata Reference Format Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Errata Reference Format Julian Reschke