Vendor Registration In order to complete any transaction between a Customer and the Contractor, the Contractor must be registered in MyFloridaMarketPlace.
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.
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.
Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.
(b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.
(c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b).
(d) Registry Operator shall provide public query-‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.
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.
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.
Requests for Registration (i) Subject to the following paragraphs of this Section 3(a), on or after the 180th day following the Initial Public Offering, a Demand Party shall have the right, by delivering a written notice to the Corporation, to require the Corporation to register, directly or indirectly, and pursuant to the terms of this Agreement, under and in accordance with the provisions of the Securities Act, the number of Registrable Securities requested to be so registered pursuant to the terms of this Agreement (any such written notice, a “Demand Notice” and any such registration, a “Demand Registration”); provided, however, that a Demand Notice may only be made prior to the expiration of the Coordination Committee if previously approved in writing by the Coordination Committee; provided, further that, the Corporation shall not be obligated to file a Registration Statement relating to any registration request under this Section 3(a) within a period of 180 days after the effective date of any other Registration Statement relating to any registration request under this Section 3(a) (except if the underwriters shall require a longer period, but in any event no more than 270 days). Following receipt of a Demand Notice for a Demand Registration in accordance with this Section 3(a), the Corporation shall use its reasonable best efforts to file a Registration Statement as promptly as practicable and shall use its reasonable best efforts to cause such Registration Statement to be declared effective under the Securities Act as promptly as practicable after the filing thereof.
(ii) No Demand Registration shall be deemed to have occurred for purposes of this Section 3 if the Registration Statement relating thereto (x) does not become effective, (y) is not maintained effective for the period required pursuant to this Section 3, or (z) the offering of the Registrable Securities pursuant to such Registration Statement is subject to a stop order, injunction, or similar order or requirement of the SEC during such period, in which case, such requesting holder of Registrable Securities shall be entitled to an additional Demand Registration in lieu thereof.
(iii) Within 10 days after receipt by the Corporation of a Demand Notice in accordance with this Section 3(a), the Corporation shall give written notice (the “Notice”) of such Demand Notice to all other holders of Registrable Securities and shall, subject to the provisions of Section 3(b) hereof, include in such registration all Registrable Securities with respect to which the Corporation received written requests for inclusion therein within 15 days after such Notice is given by the Corporation to such holders.
(iv) All requests made pursuant to this Section 3 will specify the number of Registrable Securities to be registered and the intended methods of disposition thereof.
(v) The Corporation shall be required to maintain the effectiveness of the Registration Statement with respect to any Demand Registration for a period of at least 180 days after the effective date thereof or such shorter period during which all Registrable Securities included in such Registration Statement have actually been sold; provided, however, that such period shall be extended for a period of time equal to the period the holders of Registrable Securities are required to refrain from selling any securities included in such Registration Statement at the request of the Corporation or an underwriter of the Corporation pursuant to the provisions 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.
GOVERNMENT APPROVAL OR REGISTRATION If this Agreement or any associated transaction is required by the law of any nation to be either approved or registered with any governmental agency, the Licensee will assume all legal obligations to do so. The Licensee will notify The Regents if it becomes aware that this Agreement is subject to a United States or foreign government reporting or approval requirement. The Licensee will make all necessary filings and pay all costs including fees, penalties and all other out-of-pocket costs associated with such reporting or approval process.
