Compliance with Warning Regulations The Parties agree that Xxxxxx Xxxxxx shall be deemed to be in compliance with this Settlement Agreement by either adhering to §§ 2.3 and 2.4 of this Settlement Agreement or by complying with warning requirements adopted by the State of California’s Office of Environmental Health Hazard Assessment (“OEHHA”) applicable to the product and the exposure at issue after the Effective Date.
COMPLIANCE WITH STATUTES AND REGULATIONS a) Contractor warrants and certifies that in the performance of this Contract, it will comply with all applicable statutes, rules, regulations and orders of the United States and the State of California and agrees to indemnify the State against any loss, cost, damage or liability by reason of Contractor’s violation of this provision.
Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
COMPLIANCE WITH LAWS, STATUTES, REGULATIONS During the term of this Master Contract, unless otherwise agreed, CONTRACTOR shall comply with all applicable federal, state, and local statutes, laws, ordinances, rules, policies, executive orders and regulations. CONTRACTOR shall also comply with all applicable LEA policies and procedures unless, taking into consideration all of the surrounding facts and circumstances, a policy or policies or a portion of a policy does not reasonably apply to CONTRACTOR. CONTRACTOR hereby acknowledges and agrees that it accepts all risks and responsibilities for its failure to comply with LEA policies and shall indemnify LEA under the provisions of Section 16 of this Agreement for all liability, loss, damage and expense (including reasonable attorneys’ fees) resulting from or arising out of CONTRACTOR’s failure to comply with applicable LEA policies (e.g., those policies relating to; the provision of special education and/or related services, facilities for individuals with exceptional needs, student enrollment and transfer, student inactive status, corporal punishment, student discipline, and positive behavior interventions). CONTRACTOR acknowledges and understands that XXX may report to the CDE any violations of the provisions of this Master Contract; and that this may result in the suspension and/or revocation of CDE nonpublic school/agency certification pursuant to California Education Code section 56366.4(a).
Compliance with Texas Privacy Laws and Regulations In performing their respective obligations under the Agreement, the LEA and the Provider shall comply with all Texas laws and regulations pertaining to LEA data privacy and confidentiality, including but not limited to the Texas Education Code Chapter 32, and Texas Government Code Chapter 560.
Governing Law, Regulatory Authority, and Rules The validity, interpretation and enforcement of this Agreement and each of its provisions shall be governed by the laws of the state of New York, without regard to its conflicts of law principles. This Agreement is subject to all Applicable Laws and Regulations. Each Party expressly reserves the right to seek changes in, appeal, or otherwise contest any laws, orders, or regulations of a Governmental Authority.
COMPLIANCE WITH THE CONTRACT WORK HOURS AND SAFETY STANDARDS ACT (1) Overtime requirements. No contractor or subcontractor contracting for any part of the contract work which may require or involve the employment of laborers or mechanics shall require or permit any such laborer or mechanic in any workweek in which he or she is employed on such work to work in excess of forty hours in such workweek unless such laborer or mechanic receives compensation at a rate not less than one and one-half times the basic rate of pay for all hours worked in excess of forty hours in such workweek.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
General Program Requirements Subrecipient shall adhere, but not be limited to, the following requirements for all programs:
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”).