Statutory and Regulatory Compliance Contractor shall comply with all laws and regulations applicable to the Community Development Block Grant-Disaster Recovery funds appropriated by the Disaster Relief Appropriations Act, 2013 (Pub. L. 113-2), including but not limited to the applicable Office of Management and Budget Circulars, which may impact the administration of funds and/or set forth certain cost principles, including the allowability of certain expenses.
Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the ▇▇▇ Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.
Statutory Compliance The Union and the Employer agree to cooperate fully in matters pertaining to the prevention of accidents and occupational disease and in the promotion of the health and safety of all employees. There shall be full compliance with all applicable statutes and regulations pertaining to the working environment.
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.
Standards Compliance 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”).