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.
Registration, etc Each Pledgor agrees that, upon the occurrence and during the continuance of an Event of Default hereunder, if for any reason the Collateral Agent desires to sell any of the Pledged Securities of the Borrower at a public sale, it will, at any time and from time to time, upon the written request of the Collateral Agent, use its best efforts to take or to cause the issuer of such Pledged Securities to take such action and prepare, distribute and/or file such documents, as are required or advisable in the reasonable opinion of counsel for the Collateral Agent to permit the public sale of such Pledged Securities. Each Pledgor further agrees to indemnify, defend and hold harmless the Collateral Agent, each other Secured Party, any underwriter and their respective officers, directors, affiliates and controlling persons from and against all loss, liability, expenses, costs of counsel (including, without limitation, reasonable fees and expenses to the Collateral Agent of legal counsel), and claims (including the costs of investigation) that they may incur insofar as such loss, liability, expense or claim arises out of or is based upon any alleged untrue statement of a material fact contained in any prospectus (or any amendment or supplement thereto) or in any notification or offering circular, or arises out of or is based upon any alleged omission to state a material fact required to be stated therein or necessary to make the statements in any thereof not misleading, except insofar as the same may have been caused by any untrue statement or omission based upon information furnished in writing to such Pledgor or the issuer of such Pledged Securities by the Collateral Agent or any other Secured Party expressly for use therein. Each Pledgor further agrees, upon such written request referred to above, to use its best efforts to qualify, file or register, or cause the issuer of such Pledged Securities to qualify, file or register, any of the Pledged Securities under the Blue Sky or other securities laws of such states as may be requested by the Collateral Agent and keep effective, or cause to be kept effective, all such qualifications, filings or registrations. Each Pledgor will bear all costs and expenses of carrying out its obligations under this Section 12. Each Pledgor acknowledges that there is no adequate remedy at law for failure by it to comply with the provisions of this Section 12 and that such failure would not be adequately compensable in damages, and therefore agrees that its agreements contained in this Section 12 may be specifically enforced.
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.
Ship’s name and registration Each Borrower shall keep the Ship owned by it registered in its name under an Approved Flag; shall not do, omit to do or allow to be done anything as a result of which such registration might be cancelled or imperilled; and shall not change the name or port of registry of the Ship owned by it.
Registration Compliance; No Stop Order No order suspending the effectiveness of the Registration Statement shall be in effect, and no proceeding for such purpose, pursuant to Rule 401(g)(2) or pursuant to Section 8A under the Securities Act shall be pending before or threatened by the Commission; the Prospectus and each Issuer Free Writing Prospectus shall have been timely filed with the Commission under the Securities Act (in the case of an Issuer Free Writing Prospectus, to the extent required by Rule 433 under the Securities Act) and in accordance with Section 4(a) hereof; and all requests by the Commission for additional information shall have been complied with to the reasonable satisfaction of the Representatives.
Transfer and Registration Subject to the provisions of Section 8 of this Warrant, this Warrant may be transferred on the books of the Company, wholly or in part, in person or by attorney, upon surrender of this Warrant properly endorsed, with signature guaranteed. This Warrant shall be canceled upon such surrender and, as soon as practicable thereafter, the person to whom such transfer is made shall be entitled to receive a new Warrant or Warrants as to the portion of this Warrant transferred, and the Holder of this Warrant shall be entitled to receive a new Warrant or Warrants as to the portion hereof retained.
LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.
Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.
Segregation and Registration Except as otherwise provided herein, and except for securities to be delivered to any subcustodian appointed pursuant to Sections 14.2 or 14.3 hereof, the Bank as custodian will receive and hold pursuant to the provisions hereof, in a separate account or accounts and physically segregated at all times from those of other persons, any and all Portfolio Securities which may now or hereafter be delivered to it by or for the account of the Fund. All such Portfolio Securities will be held or disposed of by the Bank for, and subject at all times to, the instructions of the Fund pursuant to the terms of this Agreement. Subject to the specific provisions herein relating to Portfolio Securities that are not physically held by the Bank, the Bank will register all Portfolio Securities (unless otherwise directed by Proper Instructions or an Officers' Certificate), in the name of a registered nominee of the Bank as defined in the Internal Revenue Code and any Regulations of the Treasury Department issued thereunder, and will execute and deliver all such certificates in connection therewith as may be required by such laws or regulations or under the laws of any state. The Fund will from time to time furnish to the Bank appropriate instruments to enable it to hold or deliver in proper form for transfer, or to register in the name of its registered nominee, any Portfolio Securities which may from time to time be registered in the name of the Fund.
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.
