3.3. Contacts

A contact contains information which represents a person or a company. See also the concept of contacts.

Namespace: http://www.nic.cz/xml/epp/contact-1.6
Schema: contact-1.6.2.xsd

Note

Contact mapping is based on the standard RFC 5733 but implemented with the following modifications:

  • addition of notification email, VAT-payer identification number, identity-document number and the type thereof,

  • replacement of two postal addresses with just one postal address.

3.3.1. Object attributes

In addition to the common attributes, contacts also have the following attributes:

id

The contact handle. See Handles of contacts, nssets and keysets.

postalInfo

Information for postal purposes, consisting of:

name

The contact name (person or company).

org

The name of an organization (use with a company). You may leave this empty to signify a natural person.

addr

The permanent address / company seat, consisting of:

street

1–3 street line(s).

city

City.

sp

State or province.

pc

Postal code.

cc

Country code.

voice

Phone number.

fax

Fax number.

email

A list of email addresses.

notifyEmail

A list of notification email addresses.

vat

VAT-payer identifier.

ident

Identity-document type and number. (A document that proves the contact’s identity.)

disclose

Disclosure preference for: addr, voice, fax, email, vat, ident, notifyEmail.

Note

The contact handle, name and organization are always disclosed.

mailing/addr extension

An additional mailing address, which consists of the same items as the permanent address (postalInfo/addr).

3.3.2. Object states

A contact can have one or more of the following statuses:

  • ok – no other states are set

  • linked – the contact has relation to other records in the Registry

  • serverDeleteProhibited – deletion of the contact is forbidden

  • serverTransferProhibited – transfer of the contact is forbidden

  • serverUpdateProhibited – update of the contact is forbidden

  • serverBlocked – the contact is blocked by administration

  • deleteCandidate – the contact is scheduled for deletion

  • conditionallyIdentifiedContact – the contact’s identity is partially verified

  • identifiedContact – the contact’s identity is fully verified

  • validatedContact – the contact is validated

  • mojeidContact – the contact is used in the mojeID extension and has more attributes and possibilities than a regular contact

3.3.3. Command-response mapping

For command-response mapping see a specific command syntax description:

3.3.4. Mailing address

Command & response extensions allow to manage an additional address with a contact.

Namespace: http://www.nic.cz/xml/epp/extra-addr-1.0
Schema: extra-addr-1.0.0.xsd

These extensions are used with the following commands:

and with responses to the contact:info command.