Meets Standard The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to financial reporting requirements, including but not limited to: • Complete and on-time submission of financial reports, including annual budget, revised budgets (if applicable), periodic financial reports as required by the authorizer and any reporting requirements if the board contracts with an Education Service Provider (ESP) • On-time submission and completion of the annual independent audit and corrective action plans, if applicable • No charging of tuition • Adequate management and financial controls • All reporting requirements related to the use of public funds
Applicable Standards The requirements and guidelines of NERC, the Applicable Regional Entity, and the Control Area in which the Customer Facility is electrically located; the PJM Manuals; and Applicable Technical Requirements and Standards.
Minimum Necessary Standard Business Associate shall apply the HIPAA Minimum Necessary standard to any Use or disclosure of PHI necessary to achieve the purposes of this Contract. See 45 CFR 164.514 (d)(2) through (d)(5).
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.
Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.
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.
Minimum Standard of Treatment 1. Each Party shall accord to a covered investment treatment in accordance with the customary international law minimum standard of treatment of aliens, including fair and equitable treatment and full protection and security. 2. The concepts of “fair and equitable treatment” and “full protection and security” in paragraph 1 do not require treatment in addition to or beyond that which is required by the customary international law minimum standard of treatment of aliens. 3. A breach of another provision of this Agreement, or of a separate international agreement, does not establish that there has been a breach of this Article.
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
Good Industry Practice all applicable Standards; and
Reformulation Standard “Reformulated Products” shall mean Products that contain concentrations less than or equal to 0.1% (1,000 parts per million (ppm)) of DEHP when analyzed pursuant to U.S. Environmental Protection Agency testing methodologies 3580A and 8270C or other methodology utilized by federal or state government agencies for the purpose of determining the phthalate content in a solid substance.