Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following taxonomies provide definitions of terminology relating to the translation and transliteration of contact information and to registration data directory services in general.

Contact Information as Defined in the Final Issue Report on the Translation and Transliteration of Contact Information based on the definition in the Registrar Accreditation Agreement (RAA), http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13-en.pdf

"In the context of these issues, “contact information” is a subset of Domain Name Registration Data.  It is the information that enables someone using a Domain Name Registration Data Directory Service (such as WHOIS) to contact the domain name registration holder.  It includes the name, organization, and postal address of the registered name holder, technical contact, as well as administrative contact.  Domain Name Registration Data is accessible to the public via a Directory Service (also known as the WHOIS service). The Registrar Accreditation Agreement (RAA 3.3.1) specifies the data elements that must be provided by registrars (via Port 43 and via web-based services) in response to a query, but it does not require that data elements, such as contact information, must be translated or transliterated."

Contact Information as Defined by the Expert Working Group on gTLD Directory Services in its Status Update Report (page 11), published on 11 November 2013 at: https://community.icann.org/download/attachments/43983053/status-update-11nov13-en.pdf?version=1&modificationDate=1384213897000&api=v2.

To meet basic domain control needs, it should be mandatory for Registries and Registrars to collect and Registrants to provide the following data elements when a domain name is registered; this data would not necessarily all be sent to the RDS:

...

g. Registrant Email Address, Registrant Telephone Number: Includes the following data elements: Number, Extension (when applicable)

From the Final Report of the Internationalized Registration Data Working Group 07 May 2012 at http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf:

2.2     Terminology

The term “WHOIS” in the ICANN environment could refer to various components of the WHOIS system. To avoid confusion and bring precision to the discussion, we use the following terms as proposed in SAC 051.[1]

...

 Thin | Thick Registry: A thin registry only includes data sufficient to identify the sponsoring registrar, status of the registration, nameserver, creation, and expiration dates for a domain registration. Registrars maintain the complete set of registration data for those domains they sponsor. .COM and .NET are examples of thin registries. Thick registries maintain fields to store and display the registrant's contact information and designated administrative and technical information, in addition to sponsoring registrar and registration status information, with the DNRD usually provided by the sponsoring registrar..INFO and .BIZ are examples of thick registries.

From SAC051: SSAC Report on Domain Name WHOIS Terminology and Structure, 19 September 2011, http://www.icann.org/en/groups/ssac/documents/sac-051-en.pdf:

2.      Taxonomy of Terms

...



[1] ICANN Security and Stability Advisory Committee (2011), SSAC Advisory on Domain Name WHOIS Terminology and Structure (SAC 051). Available: < http://www.icann.org/en/committees/security/sac051.pdf

[2] ICANN, “IDNs Glossary,” Retrieved August 10, 2010, <http://www.icann.org/en/topics/idn/idn-glossary.htm>.

[3] P. Hoffman and J. Klensin.,.“Terminology Used in Internationalisation in the IETF”, RFC 6365, September 2011..

[4] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010.

From SAC058: SSAC report on Domain Name Registration Data, 27 March 2013, http://www.icann.org/en/groups/ssac/documents/sac-058-en.pdf

3. Taxonomy of Validation
Verification, validation and resolution have been used interchangeably in various literature on this topic. We choose “validation” to refer to the assessment of data as described by this document. Verification in this document refers to the process of validating. Resolution has an entirely different technical meaning that is out of scope for this document. The SSAC asserts there are three types of validation for elements of the registration data.

...

3. Identity validation refers to the assessment that the data corresponds to the real world identity of the entity. It involves checking that a data item correctly represents the real world identity for the registrant. In general, identity validation checks are expected to require some manual intervention.

The United Nation Group of Experts on Geographic Names (UNGEGN) suggests the following relevant terminology: 

Exonym is the name used in a specific language for a geographical feature situated outside the area where that language has official status, and differing in its form from the name used in the official language or languages of the area where the geographical feature is situated. Examples: Warsaw is the English exonym for Warszawa; Londres is French for London; Mailand is German for Milano. The officially romanized endonym Moskva for Москва is not an exonym, nor is the Pinyin form Beijing, while Peking is an exonym. 

...