Regulation of Ciliary Activity Sample Clauses

Regulation of Ciliary Activity. The remainder of the work that is performed under the auspices of this contract will relate top the regulation of [CONFIDENTIAL TREATMENT REQUESTED] Dates of Contracted Studies 1 April 1999 to 31 December 1999
Sample 1
AutoNDA by SimpleDocs

Related to Regulation of Ciliary Activity

  • Regulation M Notice Unless the exceptive provisions set forth in Rule 101(c)(1) of Regulation M under the Exchange Act are satisfied with respect to the Shares, the Company shall give the Manager at least one Business Day’s prior notice of its intent to sell any Shares in order to allow the Manager time to comply with Regulation M.

  • Regulation M Compliance The Company has not, and to its knowledge no one acting on its behalf has, (i) taken, directly or indirectly, any action designed to cause or to result in the stabilization or manipulation of the price of any security of the Company to facilitate the sale or resale of any of the Securities, (ii) sold, bid for, purchased, or, paid any compensation for soliciting purchases of, any of the Securities, or (iii) paid or agreed to pay to any Person any compensation for soliciting another to purchase any other securities of the Company, other than, in the case of clauses (ii) and (iii), compensation paid to the Company’s placement agent in connection with the placement of the Securities.

  • REGULATION GG Each Fund represents and warrants that it does not engage in an “Internet gambling business,” as such term is defined in Section 233.2(r) of Federal Reserve Regulation GG (12 CFR 233) and covenants that it shall not engage in an Internet gambling business. In accordance with Regulation GG, each Fund is hereby notified that “restricted transactions,” as such term is defined in Section 233.2(y) of Regulation GG, are prohibited in any dealings with the Custodian pursuant to this Agreement or otherwise between or among any party hereto.

  • Exchange Act Compliance; Regulations T, U and X None of the transactions contemplated herein or in the other Transaction Documents (including, without limitation, the use of proceeds from the sale of the Collateral Portfolio) will violate or result in a violation of Section 7 of the Exchange Act, or any regulations issued pursuant thereto, including, without limitation, Regulations T, U and X of the Board of Governors of the Federal Reserve System, 12 C.F.R., Chapter II. The Borrower does not own or intend to carry or purchase, and no proceeds from the Advances will be used to carry or purchase, any “margin stock” within the meaning of Regulation U or to extend “purpose credit” within the meaning of Regulation U.

  • Regulations T, U and X No Loan Party is or will be engaged in the business of extending credit for the purpose of purchasing or carrying margin stock (within the meaning of Regulation T, U or X), and no proceeds of any Loan will be used to purchase or carry any margin stock or to extend credit to others for the purpose of purchasing or carrying any margin stock or for any purpose that violates, or is inconsistent with, the provisions of Regulation T, U and X.

  • Common Areas - Rules and Regulations Lessor or such other person(s) as Lessor may appoint shall have the exclusive control and management of the Common Areas and shall have the right, from time to time, to establish, modify, amend and enforce reasonable rules and regulations (“Rules and Regulations”) for the management, safety, care, and cleanliness of the grounds, the parking and unloading of vehicles and the preservation of good order, as well as for the convenience of other occupants or tenants of the Building and the Project and their invitees. Lessee agrees to abide by and conform to all such Rules and Regulations, and to cause its employees, suppliers, shippers, customers, contractors and invitees to so abide and conform. Lessor shall not be responsible to Lessee for the non-compliance with said Rules and Regulations by other tenants of the Project.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Regulations U and X No portion of any Loan is to be used, and no portion of any Letter of Credit is to be obtained, for the purpose of purchasing or carrying any "margin security" or "margin stock" as such terms are used in Regulations U and X of the Board of Governors of the Federal Reserve System, 12 C.F.R. Parts 221 and 224.

  • Margin Regulations; Investment Company Act; Public Utility Holding Company Act (a) The Borrower is not engaged and will not engage, principally or as one of its important activities, in the business of purchasing or carrying margin stock (within the meaning of Regulation U issued by the FRB), or extending credit for the purpose of purchasing or carrying margin stock. (b) None of the Borrower, any Person Controlling the Borrower, or any Subsidiary (i) is a “holding company,” or a “subsidiary company” of a “holding company,” or an “affiliate” of a “holding company” or of a “subsidiary company” of a “holding company,” within the meaning of the Public Utility Holding Company Act of 1935, or (ii) is or is required to be registered as an “investment company” under the Investment Company Act of 1940.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

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