[rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elements and Attributes Deprecated from v2"
pkyzivat at alum.mit.edu (Paul Kyzivat) Wed, 16 March 2016 17:32 UTC
From: pkyzivat at alum.mit.edu (Paul Kyzivat)
Date: Wed, 16 Mar 2016 13:32:30 -0400
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-03,
"1.3.3 Elements and Attributes Deprecated from v2"
In-Reply-To: <56E992D4.1070303@gmx.de>
References: <56E85AA1.2060002@gmx.de>
<01B2F0F9-1664-43D9-B95A-883AC38B973F@cisco.com>
<E218CD5C-DDF6-4826-A983-EA2E305EDFF0@vpnc.org> <56E90FF5.2010003@gmx.de>
<C0F3698C-42E2-4BDB-B8C2-1C590130F152@vpnc.org> <56E992D4.1070303@gmx.de>
Message-ID: <56E998AE.2060407@alum.mit.edu>
On 3/16/16 1:07 PM, Julian Reschke wrote: > That said, I believe every Internet-Draft should have an editorial note > saying how feedback should be provided, and where the editor's copy > resides... (and yes, most authors don't, and I really have no idea why...) The point about feedback makes sense to me, but why is the location of the editor's copy relevant? IMO the transition from version -nn to -nn+1 can be viewed as an atomic action that occurs at the time version -nn+1 is submitted. I realize that there is an evolving practice of keeping the editor's copy on github and allowing multiple editors to contribute to it there, thus creating interim versions between -nn and -nn+1. *If* that is so, does it really need to be *public* if it is only for communication between the multiple listed authors/editors of the document? I find it somewhat disconcerting when a reference to the github version is made public. It feels like it is then serving as an alternative process to publishing new versions. But it then requires different techniques to figure out what is going on, and to comment on changes. Such comments are not tracked in the same way and don't get the same level of public scrutiny. *If* such a technique is to become mainstream then a documented set of tools, procedures, and policies should be created around it. Thanks, Paul
- [rfc-i] draft-iab-xml2rfc-03, "1.3.3 Elements and… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Joe Hildebrand jhildebr
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Joe Hildebrand jhildebr
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Paul Hoffman
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Paul Hoffman
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Paul Kyzivat
- [rfc-i] feedback note, was: [IAB] draft-iab-xml2r… Julian Reschke
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Joe Hildebrand jhildebr
- [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elemen… Julian Reschke