Provisions for Developer
Provisions for Developer Sample Clauses
Related to Provisions for Developer
PROVISIONS FOR NON UNITED STATES FEDERAL ENTITY PROCUREMENTS UNDER UNITED STATES FEDERAL AWARDS OR OTHER AWARDS Participating Entities that use United States federal grant or FEMA funds to purchase goods or services from this Contract may be subject to additional requirements including the procurement standards of the Uniform Administrative Requirements, Cost Principles and Audit Requirements for Federal Awards, 2 C.F.R. § 200. Participating Entities may have additional requirements based on specific funding source terms or conditions. Within this Article, all references to “federal” should be interpreted to mean the United States federal government. The following list only applies when a Participating Entity accesses Supplier’s Equipment, Products, or Services with United States federal funds.
Provisions governing staff and subcontractors A. To require any subcontractor to execute documents that binds the subcontractor to comply with the provisions of this Contract. Subcontractor means an individual or entity to which the Contractor has contracted with or delegated some of its management functions or responsibilities of providing all or a part of the services required of the Contractor under this Contract.
Motions for Directions (1) Class Counsel or the Settling Defendants may apply to the Ontario Court and/or such other courts as may be required by the Courts for directions in respect of the interpretation, implementation and administration of this Settlement Agreement. Unless the Courts order otherwise, motions for directions that do not relate specifically to the matters affecting the Quebec Action shall be determined by the Ontario Court.
Contract Provisions for Orders Utilizing Federal Funds Pursuant to Appendix II to 2 Code of Federal Regulations (CFR) Part 200, Contract Provisions for Non-Federal Entity Contracts Under Federal Awards, Orders funded with federal funds may have additional contractual requirements or certifications that must be satisfied at the time the Order is placed or upon delivery. These federal requirements may be proposed by Participating Entities in Participating Addenda and Purchasing Entities for incorporation in Orders placed under this Master Agreement.
Instructions for Operators This agreement is intended to be provided to an Operator from a LEA. The Operator should fully read the agreement and is requested to complete the below areas of the agreement. Once the Operator accepts the terms of the agreement, the Operator should wet sign the agreement and return it to the LEA. Once the LEA signs the agreement, the LEA should provide a signed copy of the agreement to the Operator. Article/Exhibit Box # Description Cover Page Box # 3 Official Name of Operator Cover Page Box # 4 Date Signed by Operator Recitals Box #5 Contract Title for Service Agreement Recitals Box #6 Date of Service Agreement Article 7 Boxes #7-10 Operator’s designated representative Signature Page Boxes #15-19 Authorized Operator’s representative signature Exhibit A Box #25 Description of services provided Exhibit B All Applicable Boxes Operator notates if data is collected to provide the described services. Defines the schedule of data required for the Operator to provide the services outlined in Exhibit A Exhibit D All Applicable Boxes (Optional Exhibit): Defines deletion or return of data expectations by LEA Exhibit E All Applicable Boxes (Optional Exhibit): Operator may, by signing the Form of General Offer of Privacy Terms (General Offer, attached as Exhibit E), be bound by the terms of this DPA to any other Subscribing LEA who signs the acceptance in said Exhibit. Exhibit F Boxes # 25-29 A list of all Subprocessors used by the Operator to perform functions pursuant to the Service Agreement, list security programs and measures, list Operator’s security measures
Decisions by Members Whenever in this Agreement reference is made to the decision, consent, approval, judgment, or action of the Members, unless otherwise expressly provided in this Agreement, such decision, consent, approval, judgment, or action shall mean a Majority of the Members.
Attachment C, Standard State Provisions for Contracts and Grants Attachment C is hereby deleted in its entirety and replaced by the Attachment C December 15, 2017 attached to this Amendment. Taxes Due to the State. Contractor certifies under the pains and penalties of perjury that, as of the date this contract amendment is signed, the Contractor is in good standing with respect to, or in full compliance with a plan to pay, any and all taxes due the State of Vermont. Child Support (Applicable to natural persons only; not applicable to corporations, partnerships or LLCs). Contractor is under no obligation to pay child support or is in good standing with respect to or in full compliance with a plan to pay any and all child support payable under a support order as of the date of this amendment.
General Provisions for all Insurance Coverage 8.24.1 Without limiting Contractor's indemnification of County, and in the performance of this Contract and until all of its obligations pursuant to this Contract have been met, Contractor shall provide and maintain at its own expense insurance coverage satisfying the requirements specified in Paragraphs 8.24 and 8.25 of this Contract. These minimum insurance coverage terms, types and limits (the “Required Insurance”) also are in addition to and separate from any other contractual obligation imposed upon Contractor pursuant to this Contract. The County in no way warrants that the Required Insurance is sufficient to protect the Contractor for liabilities which may arise from or relate to this Contract.
Reasons for Layoff Layoff shall occur only for lack of work or lack of funds.
Reservations for Registry Operations 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
