<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">All,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">the virtue of a document number is that
it makes it easier to correlate translations and give each
document a translated name. That might outweigh the downside of
having it so prominent in the first place.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Jim's comment about consistent
punctuation in document numbering is spot on.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I also like to second his suggestion
for structuring the path.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">A./</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">PS: Brochures, by their nature are
different from the kind of reports and formal documents that need
careful version tracking in the document. I disagree with Jim on
his reservation.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 1/24/2019 12:26 PM, Jim DeLaHunt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:23962120-92c9-bfc4-7b1d-f2a442155f17@jdlh.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>UASG Colleagues:<br>
[keeping list address, dropping redundant individual addresses]</p>
<p>I'm glad to see this discussion moving towards a convention
which addresses some of the issues raised. Some comments on
Don's proposal interleaved below.<br>
</p>
<div class="moz-cite-prefix">On 2019-01-24 08:23, Don Hollander
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:19d63c09e1f649abaf28713c1e9e6021@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:16.0pt;
font-family:"Calibri Light",sans-serif;
color:#2F5496;
mso-fareast-language:EN-US;
font-weight:normal;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.moz-txt-link-freetext
{mso-style-name:moz-txt-link-freetext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri Light",sans-serif;
color:#2F5496;
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1457330616;
mso-list-type:hybrid;
mso-list-template-ids:-822805222 336134145 336134147 336134149 336134145 336134147 336134149 336134145 336134147 336134149;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks
for comments. Here’s my proposal<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<h1>Document Naming and Storage Conventions<o:p></o:p></h1>
<p class="MsoNormal">From time to time the UASG will review
and revise documents. The UASG’s naming and storage policy
for the documents will be:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpFirst"
style="margin-left:0cm;mso-add-space:auto;mso-list:l0
level1 lfo1"> Document Number (e.g. UASG000) – this will
be maintained as a consistent reference name for a
document</li>
</ul>
</div>
</blockquote>
<p>This proposal seems to adopt a number and reject Asmus'
proposal for a short title phrase as the consistent reference
name. I see the value of having a document number, but I think
having a consistent short title phrase is also valuable.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:19d63c09e1f649abaf28713c1e9e6021@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
<div class="WordSection1">
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpMiddle"
style="margin-left:0cm;mso-add-space:auto;mso-list:l0
level1 lfo1"><o:p></o:p>Document Revision – (e.g. UASG000
– 2019-01-25) This will be based on the publication date
and represented in the file name as yyyy-mm-dd. It will
also be included within the document.</li>
</ul>
</div>
</blockquote>
<p><br>
</p>
<p>I like using a date in yyyy-mm-dd format as a document revision
code.</p>
<blockquote type="cite"
cite="mid:19d63c09e1f649abaf28713c1e9e6021@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
<div class="WordSection1">
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpMiddle"
style="margin-left:0cm;mso-add-space:auto;mso-list:l0
level1 lfo1"><o:p></o:p>Document Link – (e.g. <span
style="color:#ED7D31">English</span> <a
href="https://uasg.tech/wp-content/uploads/UASG-000-Inventory-of-Material.pdf"
moz-do-not-send="true">
https://uasg.tech/wp-content/uploads/UASG-000-Inventory-of-Material.pdf</a>
) This will be based on the language of the document and
is what’s published on the UASG.Tech website and will
retrieve the latest official version of the document. </li>
</ul>
</div>
</blockquote>
<p><br>
</p>
<p>I have reservations about embedding text like
"wp-content/uploads/" in the official document link for our
documents. It seems to be an artifact of our current website
technology, which has no place in the official link. <br>
</p>
<p>I would suggest a link authored solely for being a clear
reference, e.g. <br>
</p>
<blockquote>
<p><a class="moz-txt-link-freetext"
href="https://uasg.tech/publications/UASG000-Inventory-of-Material/"
moz-do-not-send="true">https://uasg.tech/publications/UASG000-Inventory-of-Material/</a>
<br>
</p>
</blockquote>
<p>If we are using document numbers, we should use them
consistency. Note "UASG-000" in the proposed document link
differs from "UASG000", the proposed document number. They
should be the same. <br>
</p>
<p>It might be good to insert a language code in our URLs. I hope
in good time we will have our website and our important
publications in several different languages. The document link
might be, <br>
</p>
<blockquote>
<p><a class="moz-txt-link-freetext"
href="https://uasg.tech/en/publications/UASG000-Inventory-of-Material/"
moz-do-not-send="true">https://uasg.tech/en/publications/UASG000-Inventory-of-Material/</a>
</p>
</blockquote>
<p>The same document can be published in different formats.
Additionally, there is a need to refer to metadata about the
document. Metadata includes: a list of links to different
revisions of the document, a list of links to different language
versions of the same document, an abstract, revision details,
and so on. <br>
</p>
<p>So, I propose we make a Document Link structure which can
consistently refer to:</p>
<ul>
<li>the PDF representation of a current revision of a document,
e.g. <a class="moz-txt-link-freetext"
href="https://uasg.tech/en/publications/UASG000-Inventory-of-Material.pdf"
moz-do-not-send="true">https://uasg.tech/en/publications/UASG000-Inventory-of-Material.pdf</a>,
<br>
</li>
<li>the HTML representation of a current revision of a document,
e.g. <a class="moz-txt-link-freetext"
href="https://uasg.tech/en/publications/UASG000-Inventory-of-Material.html"
moz-do-not-send="true">https://uasg.tech/en/publications/UASG000-Inventory-of-Material.html</a>,</li>
<li>the HTML representation of metadata revision of a document,
e.g. <a class="moz-txt-link-freetext"
href="https://uasg.tech/en/publications/UASG000-Inventory-of-Material"
moz-do-not-send="true">https://uasg.tech/en/publications/UASG000-Inventory-of-Material</a>,
</li>
<li>the (PDF or other format) representation of a specific
revision of a document, e.g.
<a class="moz-txt-link-freetext"
href="https://uasg.tech/en/publications/UASG000-Inventory-of-Material/2019-01-24/UASG000-Inventory-of-Material.pdf"
moz-do-not-send="true">https://uasg.tech/en/publications/UASG000-Inventory-of-Material/2019-01-24/UASG000-Inventory-of-Material.pdf</a>,
</li>
<li>all of the above in a different language, e.g. <a
class="moz-txt-link-freetext"
href="https://uasg.tech/ja/文書/UASG000-文書一覧.pdf"
moz-do-not-send="true">https://uasg.tech/ja/文書/UASG000-文書一覧.pdf</a>
[Example only; I am not a skilled speaker of Japanese, I
probably made bad choices for the translation into Japanese.
—Jim]</li>
</ul>
<br>
<blockquote type="cite"
cite="mid:19d63c09e1f649abaf28713c1e9e6021@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
<div class="WordSection1">
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpMiddle"
style="margin-left:0cm;mso-add-space:auto;mso-list:l0
level1 lfo1"><o:p></o:p>Archives: The UASG.tech website
will include a repository of deprecated versions of
documents that will be stored and displayed based on its
file name (which will include the published date)</li>
</ul>
</div>
</blockquote>
<p><br>
</p>
<p>Agreed. I am proposing that one link to the deprecated version
of documents be in the metadata page for that document, and that
our document link convention specify the document link format
for deprecated versions also.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:19d63c09e1f649abaf28713c1e9e6021@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
<div class="WordSection1">
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraphCxSpLast"
style="margin-left:0cm;mso-add-space:auto;mso-list:l0
level1 lfo1"><o:p></o:p>Revision Details: For most
documents we will maintain a table at the end showing a
summary of revisions. Where a document is used a
brochure, this will not be done.<o:p></o:p></li>
</ul>
<span style="mso-fareast-language:EN-US"><o:p> </o:p></span></div>
</blockquote>
<p><br>
</p>
<p>Agreed. I am also proposing that the metadata page for a
document include a summary of revisions, even for brochures.<br>
</p>
<p>Other comments?<br>
—Jim DeLaHunt, Vancouver, Canada</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:19d63c09e1f649abaf28713c1e9e6021@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
lang="EN-US"> UA-discuss <a
class="moz-txt-link-rfc2396E"
href="mailto:ua-discuss-bounces@icann.org"
moz-do-not-send="true"><ua-discuss-bounces@icann.org></a>
<b>On Behalf Of </b>Asmus Freytag (c)<br>
<b>Sent:</b> Wednesday, 9 January 2019 2:09 PM<br>
<b>To:</b> Mike Hemp <a class="moz-txt-link-rfc2396E"
href="mailto:mikehamp1971@mail.com"
moz-do-not-send="true"><mikehamp1971@mail.com></a><br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated"
href="mailto:ua-discuss@icann.org"
moz-do-not-send="true">ua-discuss@icann.org</a><br>
<b>Subject:</b> Re: [UA-discuss] Proposal: Handling
Numbering of the UASG Documents<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 1/8/2019 3:58 PM, Mike Hemp wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">For
the god sake do not make it complicated for people.
RFC/IETF is only for highly technical community not
for website and general application developers. Keep
complications behind and keep the things simple for
general audience. UASG is for everyone and must be
understood very easily. Asmus idea is great. Get rid
of numbers please. People who make money from
technical stuff make issues complicated and would
come up with such ideas. <o:p></o:p></span></p>
</div>
</div>
</blockquote>
<p>W3C manages without numbers.<o:p></o:p></p>
<p>But that requires short names like "CSS" or "HTML" or
something.<o:p></o:p></p>
<p>Having to always cite documents by a full title like "<span
class="moz-txt-link-freetext">email address
internationalization EAI a technical_overview</span>" gets
pretty old. However, changing the title around a bit to
something like EAI Overview: Email Address
Internationalization (EAI), would allow "EAI Oveview" or
"UASG EAI Overview" as shorthand, which arguably would be
more self-explanatory than UASG 02.<o:p></o:p></p>
<p>A./<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">
<o:p></o:p></span></p>
<div style="border:none;border-left:solid #C3D9E5
1.5pt;padding:0cm 0cm 0cm
8.0pt;margin-left:7.5pt;margin-top:7.5pt;margin-right:3.75pt;margin-bottom:3.75pt;word-wrap:
break-word;-webkit-nbsp-mode:
space;-webkit-line-break: after-white-space"
name="quote">
<div style="margin-bottom:7.5pt">
<p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">Sent:</span></b><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> Wednesday,
January 09, 2019 at 3:01 AM<br>
<b>From:</b> "Asmus Freytag" <a
href="mailto:asmusf@ix.netcom.com"
moz-do-not-send="true"><asmusf@ix.netcom.com></a><br>
<b>To:</b> <a
href="mailto:ua-discuss@icann.org"
moz-do-not-send="true">ua-discuss@icann.org</a><br>
<b>Subject:</b> Re: [UA-discuss] Proposal:
Handling Numbering of the UASG Documents<o:p></o:p></span></p>
</div>
<div name="quoted-content">
<div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">For
comparison, the Unicode Standard has the
model where a link generally would get you
the latest version of a document, but each
document contains a header with a link to
the previous revision of the document.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">That
way, if you want to point people to the
latest version of a document you can use
an "evergreen" link, but if you need to be
sure that the link goes to a specific
version, there's that option as well.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"><a
href="http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/"
target="_blank" moz-do-not-send="true">http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">or<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"><a
href="http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/latest"
target="_blank" moz-do-not-send="true">http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/latest</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">would
get the latest version and<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"><a
href="http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/2018-05-12/"
target="_blank" moz-do-not-send="true">http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/2018-05-12/</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">would
be a specific version. Each version
remaining unaltered once posted.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">A./<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">On
1/8/2019 12:54 PM, Jim DeLaHunt wrote:<o:p></o:p></span></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">UA
Colleagues:<br>
<br>
I think the problem Michael points out is
a real one, and worthy of attention.<br>
<br>
On 2019-01-08 07:03, Michael Casadevall
wrote: <o:p></o:p></span></p>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"
style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">So
currently, the UASG publishes various
documents such as UASG 0005 and<br>
0007 and occasionally updates these
documents to reflect best current<br>
practices. For example, the UA Quick
Guide was on Version 9 before it<br>
was removed for revision.<br>
<br>
One thing I'm concerned on is that it's
not clear that a document has<br>
been updated, nor what has changed from
version to version. Furthermore,<br>
when dealing with old discussions, a
document may have changed from a<br>
message or posted....<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">Michael
proposes one alternative, <o:p></o:p></span></p>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"
style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif">…to
change the numbering and management of
UASG documentation<br>
to model it around the RFC/IETF where a
document is static once<br>
published (with errata linked), and is
obsoleted/superseded by future<br>
documents.…<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"><br>
Another alternative is to keep the
document number unchanged, but to have a
clearly-defined revision date for each
version of a document, and to always cite
a revision date along with the document
number. So, we would say "UASG012 Email
Address Internationalization (EAI): A
Technical Overview (v 2018-05-12)" instead
of "UASG012" or "Email Address
Internationalization (EAI): A Technical
Overview".<br>
<br>
Whichever we do, I believe we should set
editorial standards that each document has
a) document title, b) UASG number, and c)
revision date clearly on the front cover
and in the file name of each document
issued. Looking through some existing
documents, we seem to be inconsistent
about this. It makes documents harder to
find and harder to cite.<br>
<br>
I believe we should also define standard,
persistent URLs for each document,
something like:<br>
<br>
<a
href="http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/2018-05-12/"
target="_blank" moz-do-not-send="true">http://uasg.tech/document/uasg012/email_address_internationalization_EAI_a_technical_overview/2018-05-12/</a><br>
<br>
and ensure that visiting such a URL with a
web browser returns either the document
file itself, or a page describing the
document and allowing one to download it.
I find it hard to put links to UASG
documents into presentations, because it's
difficult to figure out which URL to use,
and how much to trust it to stay usable
over time.<br>
<br>
Best regard,<br>
—Jim DeLaHunt, Vancouver, Canada<br>
<o:p></o:p></span></p>
</blockquote>
<p style="background:white"><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p><o:p> </o:p></p>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
--Jim DeLaHunt, <a class="moz-txt-link-abbreviated" href="mailto:jdlh@jdlh.com" moz-do-not-send="true">jdlh@jdlh.com</a> <a class="moz-txt-link-freetext" href="http://blog.jdlh.com/" moz-do-not-send="true">http://blog.jdlh.com/</a> (<a class="moz-txt-link-freetext" href="http://jdlh.com/" moz-do-not-send="true">http://jdlh.com/</a>)
multilingual websites consultant
355-1027 Davie St, Vancouver BC V6E 4L2, Canada
Canada mobile +1-604-376-8953
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>