Esri User Conference Registration Sample Clauses

Esri User Conference Registration. Esri shall provide Esri User Conference registrations to Customer annually during the term of this EA in the quantities set forth in the Proposal Letter. Customer is responsible for distributing the registrations internally and to Authorized Entities. Third parties may not represent or attend on behalf of Customer at any Esri User Conference.
AutoNDA by SimpleDocs
Esri User Conference Registration. Esri shall provide Esri User Conference registrations to City annually during the term of this EA in the quantities set forth in Appendix B. City is responsible for distributing the registrations. Third parties may not represent or attend on behalf of City or Eligible Agencies at any Esri User Conference.
Esri User Conference Registration. Esri shall provide Esri User Conference registrations to County annually during the term of this EA in the quantities set forth in Appendix B. County is responsible for distributing the registrations to Licensees. Third parties may not represent or attend on behalf of County at any Esri User Conference.

Related to Esri User Conference Registration

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

  • USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • NERC Registration The NTO shall register or enter into agreement with a NERC registered entity for all required NERC functions applicable to the NTO, that may include, without limitation, those functions designated by NERC to be: “Transmission Owner” and “Transmission Planner” and “Transmission Operator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-­‐to-­‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Delay of Registration; Furnishing Information (a) No Holder shall have any right to obtain or seek an injunction restraining or otherwise delaying any such registration as the result of any controversy that might arise with respect to the interpretation or implementation of this Section 2. (b) It shall be a condition precedent to the obligations of the Company to take any action pursuant to Section 2.2, 2.3 or 2.4 that the selling Holders shall furnish to the Company such information regarding themselves, the Registrable Securities held by them and the intended method of disposition of such securities as shall be required to effect the registration of their Registrable Securities. (c) The Company shall have no obligation with respect to any registration requested pursuant to Section 2.2 or Section 2.4 if the number of shares or the anticipated aggregate offering price of the Registrable Securities to be included in the registration does not equal or exceed the number of shares or the anticipated aggregate offering price required to originally trigger the Company’s obligation to initiate such registration as specified in Section 2.2 or Section 2.4, whichever is applicable.

  • Registration Procedure Unless such Exchange Shares are issued pursuant to an Issuer Registration Statement as provided in Section 2 hereof, then subject to Sections 3.1(c) and 3.2 hereof, if Holder desires to exercise its Registration Rights with respect to the Exchange Shares, Holder shall deliver to the Company a written notice (a "Registration Notice") informing the Company of such exercise and specifying the number of shares to be offered by such Holder (such shares to be offered being referred to herein as the "Registrable Securities"). Such notice may be given at any time on or after the date a notice of exchange is delivered by Holder to the Partnership pursuant to the Partnership Agreement, but must be given at least fifteen (15) Business Days prior to the anticipated consummation of the sale of Registrable Securities, which consummation shall in any event be subject to an effective Shelf Registration Statement (as hereinafter defined) or an effective New Registration Statement (as hereinafter defined). As used in this Agreement, a "Business Day" is any Monday, Tuesday, Wednesday, Thursday or Friday other than a day on which banks and other financial institutions are authorized or required to be closed for business in the State of New York or Michigan. Upon receipt of the Registration Notice, the Company, if it has not already caused the Registrable Securities to be included as part of an existing shelf registration statement (prior to the filing of which the Company shall have given ten (10) Business Days notice to Holder) and related prospectus that the Company than has on file with the Commission (the "Shelf Registration Statement") (in which event the Company shall be deemed to have satisfied its registration obligation under this Section 3), will cause to be filed with the Commission as soon as reasonably practicable after receiving the Registration Notice a new registration statement and related prospectus (a "New Registration Statement") that complies as to form in all material respects with applicable Commission rules providing for the sale by Holder of the Registrable Securities, and agrees (subject to Section 3.2 hereof) to use its best efforts to cause such New Registration Statement to be declared effective by the Commission as soon as practicable. (As used herein, "Registration Statement" and "Prospectus" refer to the Shelf Registration Statement and related prospectus (including any preliminary prospectus) or the New Registration Statement and related prospectus (including any preliminary prospectus), whichever is utilized by the Company to satisfy Holder's Registration Rights pursuant to this Section 3, including in each case any documents incorporated therein by reference.) Holder agrees to provide in a timely manner information regarding the proposed distribution by Holder of the Registrable Securities and such other information reasonably requested by the Company in connection with the preparation of and for inclusion in the Registration Statement. The Company agrees (subject to Section 3.2 hereof) to use its best efforts to keep the Registration Statement effective (including the preparation and filing of any amendments and supplements necessary for that purpose) until the earlier of (i) the date on which Holder consummates the sale of all of the Registrable Securities registered under the Registration Statement, or (ii) the date on which all of the Registrable Securities are eligible for sale pursuant to Rule 144(k) (or any successor provision) or in a single transaction pursuant to Rule 144(e) (or any successor provision) under the Securities Act of 1933, as amended (the "Act"), provided, that except with respect to any Shelf Registration, such period need to extend beyond nine months after the effective date of the Registration Statement; and provided further, that with respect to any Shelf Registration, such period need not extend beyond the time period provided in this Section 3.1(a), and which periods, in any event, shall terminate when all the Exchange Shares covered by such Registration Statement have been sold (but not before the expiration of the time period provided in Section 4(3) of the Act and Rule 174 thereunder, if applicable). The Company agrees to provide to Holder a reasonable number of copies of the final Prospectus and any amendments or supplements thereto. Notwithstanding the foregoing, the Company may at any time, in its sole discretion and prior to receiving any Registration Notice from Holder, include all of Holder's Exchange Shares or any portion thereof in any Shelf Registration Statement. In connection with any Registration Statement utilized by the Company to satisfy Holder Registration Rights pursuant to this Section 3, Holder agrees that it will respond within ten (10) Business Days to any request by the Company to provide or verify information regarding Holder or Holder's Registrable Securities as may be required to be included in such Registration Statement pursuant to the rules and regulations of the Commission.

  • Subsequent Registrations Other than pursuant to the Registration Statement, prior to the Effective Date, the Company may not file any registration statement (other than on Form S-8) with the Commission with respect to any securities of the Company.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!