FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:
CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.
ADA Compliance Compliance with the Americans with Disabilities Act of 1990 (“ADA”) shall be the sole responsibility of the Contractor. The Contractor shall defend and hold APS harmless from any expense or liability arising from the Contractor’s non-compliance therewith. The Contractor’s responsibilities related to ADA compliance shall include, but not be limited to, the following:
Xxxxxx Compliance The Union shall comply with the requirements set forth in Chicago Teachers Union x. Xxxxxx, 475 U.S. 292 (1986) for the deduction of agency shop fees. Annually, the Union shall certify in writing to the City that the Union has complied with the requirements set forth in this section and in Xxxxxx, 475 U.S. 292.
Public safety compliance The Hirer shall comply with all conditions and regulations made in respect of the premises by the Fire Authority, Local Authority, the Licensing Authority or otherwise, particularly in connection with any event which constitutes regulated entertainment, at which alcohol is sold or provided or which is attended by children.
Xxxxx-Xxxxx Act compliance IF proposing on PART 2, Texas Statute requires compliance with Xxxxx-Xxxxx Act, as amended (40 U.S.C. 3141- 3148). When required by Federal program legislation, all prime construction contracts in excess of $2,000 awarded by non-Federal entities must include a provision for compliance with the Xxxxx-Xxxxx Act (40 U.S.C. 3141-3144, and 3146-3148) as supplemented by Department of Labor regulations (29 CFR Part S, "Labor Standards Provisions Applicable to Contracts Covering Federally Financed and Assisted Construction"). In accordance with the statute, contractors must be required to pay wages to laborers and mechanics at a rate not less than the prevailing wages specified in a wage determination made by the Secretary of Labor. In addition, contractors must be required to pay wages not less than once a week. The non-Federal entity must place a copy of the current prevailing wage determination issued by the Department of Labor in each solicitation. The decision to award a contract or subcontract must be conditioned upon the acceptance of the wage determination. The non-Federal entity must report all suspected or reported violations to the Federal awarding agency. The contracts must also include a provision for compliance with the Xxxxxxxx "Anti-Kickback" Act {40 U.S.C. 314S), as supplemented by Department of Labor regulations (29 CFR Part 3, "Contractors and Subcontractors on Public Building or Public Work Financed in Whole or in Part by Loans or Grants from the United States"). The Act provides that each contractor or subrecipient must be prohibited from inducing, by any means, any person employed in the construction, completion, or repair of public work, to give up any part of the compensation to which he or she is otherwise entitled. The non-Federal entity must report all suspected or reported violations to the Federal awarding agency. BY SUBMITTING A PROPOSAL FOR PART 2 OF THIS SOLICITATION, the Vendor agrees, AS REQUIRED BY LAW, to comply with the Xxxxx Xxxxx Act, IF APPLICABLE and if proposing on PART 2 of this solicitation.
PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.
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”).
