We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

The Contact Element Sample Clauses

The Contact Element. The contact element has the property "id" and is a container consisting of the following elements: a. client-id: The id of the contact. b. name: The name of the contact. c. organization: The organization for the contact. d. street1: The first part of the street address of the contact. e. street2: The second part of the street address of the contact. f. street3: The third part of the street address of the contact. g. city: The name of the city of the contact. h. state-province: The name of the state/province of the contact. i. postal-code: The postal/zip code of the contact. j. geographic location: The two letter ISO 3166 code for the contact's geographic location. k. voice: The voice phone number of the contact in E164a format. l. fax: The fax number of the contact in E164a format. m. email: The e-mail address of the contact. n. authinfo: Authorization code. o. owned-by: An identification of the sponsoring registrar of the contact. p. created-by: An identification of the registrar that created the contact object. q. created-on: The date/time the contact object was originally created. r. updated-by: An identification of the registrar that last updated the contact object. s. updated-on: The date/time the contact object was last updated. t. transferred-on: The date/time when the contact object was last transferred. u. status: Contact status. An example contact container appears below: <contact id="1"> <client-id>jd1</client-id> <name>Xxxx Xxx</name> <organization>aol</organization> <street1>0000 Xxxx 00xx Xxxxxx</street1> <street2></street2> <street3></street3> <city>New York</city> <state-province>NY</state-province> <postal-code>12345</postal-code> <country>US</country> <voice>+212.1234567</voice> <fax>+212.1234568</fax> <email>xxxx@xxxxxxx.xxxx</email> <authinfo>62626rgfgffg72273</authinfo> <owned-by>42</owned-by> <created-by> 42</created-by> <created-on>2001-06-01 03:01:21</created-on> <updated-by>42</updated-by> <updated-on>2001-06-01 03:01:21</updated-on> <transferred-on></transferred-on> <status>ACTIVE</status> </contact>
The Contact Element. The contact element has the property "id" and is a container consisting of the following elements: a. name: The name of the contact. b. organization: The organization for the contact. c. street1: The first part of the street address of the contact. d. street2: The second part of the street address of the contact. e. street3: The third part of the street address of the contact. f. city: The name of the city of the contact. g. state-province: The name of the state/province of the contact. h. postal-code: The postal/zip code of the contact. i. country: The two letter ISO 3166 code for the contact's country. j. voice: The voice phone number of the contact in E164a format. k. fax: The fax number of the contact in E164a format. l. email: The e-mail address of the contact. m. owned-by: An identification of the sponsoring registrar of the contact. The sponsoring registrar is designated by a number uniquely assigned by the IANA. n. created-code: A reference to the transaction that created the contact object. o. created-by: An identification of the registrar that created the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. p. created-on: The date/time the contact object was originally created. q. updated-by: An identification of the registrar that last updated the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. r. updated-on: The date/time the contact object was last updated. s. transferred-by: An identification of the registrar that last transferred the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. t. transferred-on: The date/time when the contact object was last transferred. u. transferred-code: A reference to the transaction that last transferred the contact object. v. status: Contact status. An example contact container appears below: <contact id="1"> <name>Xxxx Xxx</name> <organization>aol</organization> <street1>1234 East 11th Xxxxxx</xxxxxx0> <xxxxxx0></xxxxxx0> <xxxxxx0></xxxxxx0> <city>New York</city> <state-province>NY</state-province> <postal-code>12345</postal-code> <country>US</country> <voice>+212.1234567</voice> <fax>+212.1234568</fax> <email>xxxx@xxxxxxx.xxx</email> <owned-by>42</owned-by> <created-code>12345680</created-code> <created-by>REG-042</created-by> <created-on>1-Jul-2001 12:42:22AM</created-on> <updated-by>42</updated-by> <updated-on>1-Jul-2001 12:42:22AM</updated-on> <transferred-by></trans...
The Contact Element. The contact element has the property "id" and is a container consisting of the following elements: a. name: The name of the contact. b. organization: The organization for the contact. c. street1: The first part of the street address of the contact. d. street2: The second part of the street address of the contact. e. street3: The third part of the street address of the contact.
The Contact Element. The contact element has the attribute "id" that will hold the unique identified of the contact object inside the registry. The contact element will have the following child elements: a. name: The name of the contact. b. organization: The organization for the contact. c. street1: The first part of the street address of the contact. d. street2: The second part of the street address of the contact. e. street3: The third part of the street address of the contact. f. city: The name of the city of the contact. g. state-province: The name of the state/province of the contact. h. postal-code: The postal/zip code of the contact. i. country: The two letter ISO 3166 code for the contact's country. j. voice: The voice phone number of the contact in E164a format. k. fax: The fax number of the contact in E164a format. l. email: The e-mail address of the contact. m. owned-by: An identification of the sponsoring registrar of the contact. The sponsoring registrar is designated by a number uniquely assigned by the IANA.
The Contact Element. The contact element has the propertyattribute "id" and is a container consisting of thethat will hold the unique identified of the contact object inside the registry. The contact element will have the following child elements: a. name: The name of the contact. b. organization: The organization for the contact. c. street1: The first part of the street address of the contact. d. street2: The second part of the street address of the contact. e. street3: The third part of the street address of the contact. f. city: The name of the city of the contact. g. state-province: The name of the state/province of the contact. h. postal-code: The postal/zip code of the contact. i. country: The two letter ISO 3166 code for the contact's country. j. voice: The voice phone number of the contact in E164a format. k. fax: The fax number of the contact in E164a format. l. email: The e-mail address of the contact. m. owned-by: An identification of the sponsoring registrar of the contact. The sponsoring registrar is designated by a number uniquely assigned by the IANA. n. created-code: A reference to the transaction that created the contact object. o. created-by: An identification of the registrar that created the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. p. created-on: The date/time the contact object was originally created. q. updated-by: An identification of the registrar that last updated the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. r. updated-on: The date/time the contact object was last updated. s. transferred-by: An identification of the registrar that last transferred the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. t. transferred-on: The date/time when the contact object was last transferred.
The Contact Element. The contact element has the property "id" and is a container consisting of the following elements: a. name: The name of the contact. b. organization: The organization for the contact. c. street1: The first part of the street address of the contact. d. street2: The second part of the street address of the contact. e. street3: The third part of the street address of the contact. f. city: The name of the city of the contact. g. state-province: The name of the state/province of the contact. h. postal-code: The postal/zip code of the contact. i. geographic location: The two letter ISO 3166 code for the contact's geographic location. j. voice: The voice phone number of the contact in E164a format. k. fax: The fax number of the contact in E164a format. l. email: The e-mail address of the contact. m. sponsoring registrar: An identification of the sponsoring registrar of the contact. The sponsoring registrar is designated by a number uniquely assigned by the IANA. n. created-by: An identification of the registrar that created the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. o. created-on: The date/time the contact object was originally created. p. updated-by: An identification of the registrar that last updated the contact object. The sponsoring registrar is designated by a number uniquely assigned by the IANA. q. updated-on: The date/time the contact object was last updated. r. transferred-on: The date/time when the contact object was last transferred. s. status: Contact status. t. contact authorization information. u. contact association status.
The Contact Element. The contact element has the attribute "id" and is a container consisting of the following elements: a. name: The name of the contact. b. organization: The organization for the contact. c. Within the "contact" container is a sub-container named "address" with the following elements: i. street1: The first part of the street address of the contact. ii. street2: The second part of the street address of the contact. iii. city: The name of the city of the contact. iv. state-province: The name of the state/province of the contact. v. postal-code: The postal/zip code of the contact. vi. country: The two-letter ISO 3166 code for the contact's country. d. voice: The voice phone number of the contact in E164a format. e. fax: The fax number of the contact in E164a format. f. email: The e-mail address of the contact.

Related to The Contact Element

  • CHANGES IN EMERGENCY AND SERVICE CONTACT PERSONS In the event that the name or telephone number of any emergency or service contact for the Competitive Supplier changes, Competitive Supplier shall give prompt notice to the Town in the manner set forth in Article 18.3. In the event that the name or telephone number of any such contact person for the Town changes, prompt notice shall be given to the Competitive Supplier in the manner set forth in Article 18.3.

  • Abuse Contact Registry Operator shall provide to ICANN and publish on its website its accurate contact details including a valid email and mailing address as well as a primary contact for handling inquiries related to malicious conduct in the TLD, and will provide ICANN with prompt notice of any changes to such contact details.

  • Emergency Contact Information Resident must complete and provide to University an emergency contact information form provided by University Housing before Resident will be allowed to move into the Residence Facility.

  • Customer Contact During the delivery phase of a Project Supplier may have direct communication with a Customer, limited solely to those communications necessary to affect provision of Services and/or Deliverables.

  • Customer Contacts CLEC, or CLEC's authorized agent, are the single point of contact for its End User Customers' service needs, including without limitation, sales, service design, order taking, Provisioning, change orders, training, maintenance, trouble reports, repair, post-sale servicing, Billing, collection and inquiry. CLEC will inform its End User Customers that they are End User Customers of CLEC. CLEC's End User Customers contacting Qwest will be instructed to contact CLEC, and Qwest's End User Customers contacting CLEC will be instructed to contact Qwest. In responding to calls, neither Party will make disparaging remarks about the other Party. To the extent the correct provider can be determined, misdirected calls received by either Party will be referred to the proper provider of Local Exchange Service; however, nothing in this Agreement shall be deemed to prohibit Qwest or CLEC from discussing its products and services with CLEC's or Qwest's End User Customers who call the other Party. 10.1 In the event Qwest terminates Service to CLEC for any reason, CLEC will provide any and all necessary notice to its End User Customers of the termination. In no case will Qwest be responsible for providing such notice to CLEC's End User Customers.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Operational Contacts Each Interconnection Party shall designate, and provide to each other Interconnection Party contact information concerning, a representative to be responsible for addressing and resolving operational issues as they arise during the term of the Interconnection Service Agreement.

  • Contact Points Each Party shall designate a contact point to facilitate communications between the Parties on any matter covered by this Agreement.

  • Project Manager The term “Project Manager” refers to the employee of the State who has been assigned responsibility for overseeing and managing the proper and timely implementation of the project.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following: