<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 28, 2014, at 6:41 AM, Alan Barrett <<a href="mailto:apb@cequrux.com" class="">apb@cequrux.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Mon, 27 Oct 2014, Adam Nelson wrote:<br class=""><blockquote type="cite" class="">After much deliberation, we have come to agree on the following format for<br class="">all future policy proposals (where YYYY is the year, NNN is an incremental<br class="">number starting at 1 at the beginning of each year, and VVV is the version<br class="">of the proposal):<br class=""><br class="">afYYYY-NNN-vVVV<br class=""><br class="">For example, the 2nd draft of the 3rd proposal of next year would be:<br class=""><br class="">af2015-3-v2<br class=""><br class="">If the above policy proposal were to be finalized, the version would then<br class="">be dropped:<br class=""><br class="">af2015-3<br class=""></blockquote><br class="">Thank you! I have been asking for this for several years.<br class=""><br class="">Please also make the URLs reasonably short, like<br class="">http[s]://<a href="http://afrinic.net/policy/" class="">afrinic.net/policy/</a><number>, possibly with a language code<br class="">like "en" or "fr" between "<a href="http://afrinic.net" class="">afrinic.net</a>" and "policy”.<br class=""></div></blockquote><div><br class=""></div>It would also be nice if the URL without a version number would retrieve the current version, but all prior versions were accessible by version, so, for example, if v4 was the most recent version of 2014-8, a URL of <a href="http://afrinic.net/policy/draft/2014-8" class="">http://afrinic.net/policy/draft/2014-8</a> would get af2014-8-v4.</div><div><br class=""></div><div>I think that it is desirable to separate …/policy/<number> which should contain only adopted policies from …/policy/draft/<number> which should contain policies which are under development or history of policies which were adopted or abandoned. Obviously, each policy page should include a current state of the policy (Adopted/Abandoned/Under Discussion)</div><div><br class=""></div><div>I realize that the addition of a /draft/ level to the hierarchy is contrary to Alan’s request for short URLs, but I think it is a small amount of additional typing and that it is important to make it easy to distinguish drafts from policies.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>