Legal Compliance Contractor represents and warrants that it shall secure all notices and comply with all applicable laws, ordinances, rules and regulations of any governmental entity in conjunction with the performance of obligations under the Contract. Prior to award and during the Contract term and any renewals thereof, Contractor must establish to the satisfaction of the Commissioner that it meets or exceeds all requirements of the Bid and Contract and any applicable laws, including but not limited to, permits, licensing, and shall provide such proof as required by the Commissioner. Failure to comply or failure to provide proof may constitute grounds for the Commissioner to terminate or suspend the Contract, in whole or in part, or to take any other action deemed necessary by the Commissioner. Contractor also agrees to disclose information and provide affirmations and certifications to comply with Sections 139-j and 139-k of the State Finance Law.
PUBLIC RECORDS COMPLIANCE Orange County is a public agency subject to Chapter 119, Florida Statutes. The Contractor agrees to comply with Florida’s Public Records Law. Specifically, the Contractor shall:
Litigation and Compliance (a) There are no actions, suits, claims or proceedings, whether in equity or at law or, any Governmental investigations pending or threatened:
OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.
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”).