[Gnso-newgtld-dg] Draft Issue Categorization

[David Payne]

Hello all

I'm joining this group a little later than most, but I've now read all the
meeting transcripts and many of the email threads to catch up. And
according to the GAC, I have plenty of time to contribute!

I visualize the work of this group falling into 3 phases (this was probably
described by Bret during the session in Los Angeles): Collecting,
organizing, and framing the issues. Collecting issues has already gone
well. I think we're almost done with the organizing phase.

The mind map is great. I like that it has multiple levels so many issues
can be grouped under a manageable number of headers. I'm concerned,
though, that there are so many issues still to uncover that it could become
overwhelming. I've also had trouble finding only one place for several of
the issues.

I'd like to suggest a different style of mind map: the wheel chart. It has
more spaces and a logic that's easy to follow. The inner layer contains the
stakeholders, and the outer layer contains the procedures. At the center of
it all is the TLD string. The top half of the stakeholders circle are those
who are seeking to obtain rights to the string. The bottom half of
stakeholders are those who wish to block the string. The location of a
procedure aligns with the stakeholders who can use it. For example, an
applicant who wishes to obtain a string must undergo evaluation. A rights
holder who wishes to block the string must bring an objection. Issues that
concern the string itself, such as IDNs, would be grouped directly in the
middle.

I've noticed that most issues relate either to the string at the top level
or strings at the second level. For example, a legal rights objection is
about rights to the top level string, while the TMCH is about rights to
second level domains. So I've created a different wheel for second level
issues, with the same division of stakeholders (those seeking to obtain and
those seeking to block).

Between the two wheels, it's easy to sort all of the issues that will
arise. I've found I can find a clear location for almost any issue by
following the three steps in the diagram:

1. Is the issue about the top level string or domains at the second level?
1. Who is the proponent of the issue? Is the stakeholder seeking to obtain
a string or block it?
3. Which procedure would that stakeholder currently use to do so?

Like the current mind map, this one can unwrap into a standard outline. The
two wheels become two pillars (or articles). The inner layer (stakeholders)
would be the main headings and the outer layer (procedures) make up the
subheadings. That will be more practical when we move beyond this
discussion group.

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-dg/attachments/20141024/e249ff13/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Subsequent round_wheel chart_string layer.pdf
Type: application/pdf
Size: 51213 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-dg/attachments/20141024/e249ff13/Subsequentround_wheelchart_stringlayer-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Subsequent round_wheel chart_second level.pdf
Type: application/pdf
Size: 49865 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-dg/attachments/20141024/e249ff13/Subsequentround_wheelchart_secondlevel-0001.pdf>