Compliance Additional Requirements
Compliance Additional Requirements Sample Clauses
Related to Compliance Additional Requirements
Additional Requirements As a condition precedent to the execution and Delivery, the registration of issuance, transfer, split-up, combination or surrender, of any ADS, the delivery of any distribution thereon, or the withdrawal of any Deposited Property, the Depositary or the Custodian may require (i) payment from the depositor of Shares or presenter of ADSs or of an ADR of a sum sufficient to reimburse it for any tax or other governmental charge and any stock transfer or registration fee with respect thereto (including any such tax or charge and fee with respect to Shares being deposited or withdrawn) and payment of any applicable fees and charges of the Depositary as provided in Section 5.9 and Exhibit B, (ii) the production of proof reasonably satisfactory to it as to the identity and genuineness of any signature or any other matter contemplated by Section 3.1, and (iii) compliance with (A) any laws or governmental regulations relating to the execution and Delivery of ADRs or ADSs or to the withdrawal of Deposited Securities and (B) such reasonable regulations as the Depositary and the Company may establish consistent with the provisions of the representative ADR, if applicable, the Deposit Agreement and applicable law.
Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.
CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
Compliance Requirements K. If using volunteers as provided for in this Contract during FY19, which encompasses the Contract term of July 1, 2019 to June 30, 2020, then the Grantee must either:
Compliance with Governmental Requirements Grantor shall comply promptly with all laws, ordinances, rules and regulations of all governmental authorities, now or hereafter in effect, applicable to the ownership, production, disposition, or use of the Collateral. Grantor may contest in good faith any such law, ordinance or regulation and withhold compliance during any proceeding, including appropriate appeals, so long as Lender's interest in the Collateral, in Lender's opinion, is not jeopardized.
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
Compliance with Environmental Requirements 50.1 The Contractor shall provide the goods and/or Services required under the Contract in accordance with applicable laws and the Authority’s environmental policy, which is to conserve energy, water and other resources, reduce waste and phase out the use of ozone depleting substances and minimise the release of greenhouse gases, volatile organic compounds and other substances damaging to health and the environment.
General Requirements The Contractor hereby agrees:
FEDERAL REQUIREMENTS In the event this Contract is paid in whole or in part from any federal government agency or source, the specific terms, regulations and requirements governing the disbursement of these funds shall be specified herein and become a part of this clause.
Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
