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.
Voter Registration When designated by the Secretary of State, the Contractor agrees to become a voter registration agency as defined by 17 V.S.A. §2103 (41), and to comply with the requirements of state and federal law pertaining to such agencies.
Vendor Registration In order to complete any transaction between a Customer and the Contractor, the Contractor must be registered in MyFloridaMarketPlace.
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.
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.
SEC Registration The Parties mutually agree to use commercially reasonable efforts to maintain effective registration statements with the Securities and Exchange Commission with respect to the long-term incentive awards to the extent any such registration statement is required by applicable Law.
BROKER-DEALER REGISTRATION; FINRA MEMBERSHIP The Dealer Manager is, and during the term of this Agreement will be, (i) duly registered as a broker-dealer pursuant to the provisions of the Exchange Act, (ii) a member in good standing of FINRA, and (iii) a broker or dealer duly registered as such in those states where the Dealer Manager is required to be registered in order to carry out the Offering as contemplated by this Agreement. Each of the Dealer Manager’s employees and representatives has all required licenses and registrations to act under this Agreement. There is no provision in the Dealer Manager’s FINRA membership agreement that would restrict the ability of the Dealer Manager to carry out the Offering as contemplated by this Agreement.
Request for Registration Subject to the provisions of subsection 2.1.4 and Section 2.4 hereof, at any time and from time to time on or after the date the Company consummates the Business Combination, the Holders of at least a majority in interest of the then-outstanding number of Registrable Securities (the “Demanding Holders”) may make a written demand for Registration of all or part of their Registrable Securities, which written demand shall describe the amount and type of securities to be included in such Registration and the intended method(s) of distribution thereof (such written demand a “Demand Registration”). The Company shall, within ten (10) days of the Company’s receipt of the Demand Registration, notify, in writing, all other Holders of Registrable Securities of such demand, and each Holder of Registrable Securities who thereafter wishes to include all or a portion of such Holder’s Registrable Securities in a Registration pursuant to a Demand Registration (each such Holder that includes all or a portion of such Holder’s Registrable Securities in such Registration, a “Requesting Holder”) shall so notify the Company, in writing, within five (5) days after the receipt by the Holder of the notice from the Company. Upon receipt by the Company of any such written notification from a Requesting Holder(s) to the Company, such Requesting Holder(s) shall be entitled to have their Registrable Securities included in a Registration pursuant to a Demand Registration and the Company shall effect, as soon thereafter as practicable, but not more than forty five (45) days immediately after the Company’s receipt of the Demand Registration, the Registration of all Registrable Securities requested by the Demanding Holders and Requesting Holders pursuant to such Demand Registration. Under no circumstances shall the Company be obligated to effect more than an aggregate of three (3) Registrations pursuant to a Demand Registration under this subsection 2.1.1 with respect to any or all Registrable Securities; provided, however, that a Registration shall not be counted for such purposes unless a Form S-1 or any similar long-form registration statement that may be available at such time (“Form S-1”) has become effective and all of the Registrable Securities requested by the Requesting Holders to be registered on behalf of the Requesting Holders in such Form S-1 Registration have been sold, in accordance with Section 3.1 of this Agreement.
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.
Other Registrations If the Company has previously filed a registration statement with respect to Registrable Securities pursuant to Section 1 or pursuant to this Section 2, and if such previous registration has not been withdrawn or abandoned, the Company shall not file or cause to be effected any other registration of any of its equity securities or securities convertible or exchangeable into or exercisable for its equity securities under the Securities Act (except on Form S-8 or any successor form), whether on its own behalf or at the request of any holder or holders of such securities, until a period of at least 180 days has elapsed from the effective date of such previous registration.
