[TSG-Access-RD] Naming our final report

[Steve Crocker]

Ram, et al,

I was serious when I said there should be some sort of overall ICANN
document system.  In SSAC we made up our own nomenclature, and I think
other groups, e.g. RSSAC, have also invented their own.  However, unlike
SSAC and RSSAC, this technical study group -- lowercase used intentionally
-- has a limited lifetime, so there won't be any continuity.  Where will
this document be located and how will people find it?  These are questions
outside of our purview.  ICANN Org needs to step up at this point and
provide a place for the document.  And, in my view, they have to be
responsible for the numbering scheme.  Is the prefix "TSG" going to be used
by other groups?  It's ok with me if it is, but someone needs to make sure
the next technical study group doesn't decide its first document is also
TSG001.

Steve


On Wed, Apr 17, 2019 at 7:26 PM Steve Crocker <steve at shinkuro.com> wrote:

> Seems to me there should be some sort of overall ICANN document system.
> The archival and retrieval of these sorts of documents is a requirement
> that will last longer than the TSG.
>
> Steve
>
> Sent from my iPhone
>
> On Apr 17, 2019, at 7:21 PM, Ram Mohan <rmohan at afilias.info> wrote:
>
> Folks,
>
> Yesterday I was suggesting naming our final document something with a
> date. On further thought, and considering that there _*may*_ be instances
> where this document is referred to, I wonder if we are better off with a
> numbered doc instead. Of course, this means that a future TSG output would
> be expected to go to TSG002, etc.
>
>
>
> Something like: *TSG001, Technical Model for Access to Non-Public
> Registration**, published April 23, 2019*
>
>
>
> Any thoughts/objections/concerns?
>
>
>
> -Ram
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tsg-access-rd/attachments/20190419/67455f42/attachment-0001.html>