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 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).
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
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”).