Design Standards Most recent edition of the “Owner’s Design Standards,” including any partial updates as may be directed by the Owner.
Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.
Common Areas - Rules and Regulations Lessor or such other person(s) as Lessor may appoint shall have the exclusive control and management of the Common Areas and shall have the right, from time to time, to establish, modify, amend and enforce reasonable rules and regulations (“Rules and Regulations”) for the management, safety, care, and cleanliness of the grounds, the parking and unloading of vehicles and the preservation of good order, as well as for the convenience of other occupants or tenants of the Building and the Project and their invitees. Lessee agrees to abide by and conform to all such Rules and Regulations, and to cause its employees, suppliers, shippers, customers, contractors and invitees to so abide and conform. Lessor shall not be responsible to Lessee for the non-compliance with said Rules and Regulations by other tenants of the Project.
Construction Standards The Developer shall construct the Subdivision in accordance with the Subdivision Plan, as approved by the Planning Commission, and if applicable, the requirements of the Design Review Committee, and in accordance with the requirements of
(a) the Millington Subdivision Regulations; (b) standards and specifications contained in “Local Public Works Standard, and Specifications”, as amended to include specific requirements for construction in Millington, TN; (c) the Building Code (as adopted by Shelby County); (d) the Fire Code (as adopted by Shelby County); (e) the Millington Zoning Ordinance; and (f) the applicable Ordinances of the City. Items (a) through (f) are hereby made a part of this Agreement by reference and are hereinafter referred to collectively as the “Codes”. References herein to the Codes are to those in effect on the Effective Date unless amendments are hereafter made which apply to all improvements or subdivisions regardless of their date of commencement and/or completion of construction. The Conditions of Approval established by the Planning Commission, and, as applicable, the Design Review Committee (any or all of which as may have been modified by the Board of Mayor and Aldermen) are set forth in Exhibit “A” to this Agreement and are incorporated herein by reference and made a part hereof.
Procurement Standards For projects being managed by the Local Government and on the State highway system or that include state funding, the Local Government must obtain approval from the State for its proposed procurement procedure for the selection of a professional services provider, a contractor for a construction or maintenance project, or a materials provider.
Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).
OMB Standards Unless specified otherwise within this agreement, the Subrecipient shall procure all materials, property, or services in accordance with the requirements of 24 CFR 84.40−48.
Property Standards Owner must maintain the Unit, and any common areas of the property accessible to the Tenant under the Lease, in decent, safe and sanitary condition and comply with all applicable state or local codes and requirements for rental properties. Upon notice by the Program Administrator following any inspection (whether conducted in-person or virtually in accordance with the Program guidelines), Owner will promptly correct any violations of Program requirements and this Contract. If the Owner fails to correct such violations, the Program Administrator may terminate this Contract and the Rental Assistance Payment even if the Tenant continues occupancy under the Lease. Owner/Representative Initials:
Content Standards You agree that you will not upload or provide content or otherwise post, transmit, distribute, or disseminate through the Zelle® Payment Service any material that: (1) is false, misleading, unlawful, obscene, indecent, lewd, pornographic, defamatory, libelous, threatening, harassing, hateful, abusive, or inflammatory; (2) encourages conduct that would be considered a criminal offense or gives rise to civil liability; (3) breaches or infringes any duty toward or rights of any person or entity, including rights of publicity, privacy or intellectual property; (4) contains corrupted data or any other harmful, disruptive, or destructive files; (5) advertises products or services competitive with Zelle®, as determined by Zelle® in its sole discretion; or (6) in Zelle®’s or our sole judgment, is objectionable, restricts or inhibits any person or entity from using or enjoying any portion of the Zelle® Payment Service, or which may expose us, Zelle® or our respective affiliates or customers to harm or liability of any nature.
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”).
