Agreement alignment Sample Clauses

Agreement alignment. Keeping the sap–3rd person asymmetry in mind, I will propose in this section an Optimality Theory based approach to the Inuit agreement system, adapted from Xxxxxxxx (2000). Inuit both has clitics and true agreement morphemes. In order to ever have overt agreement morphology we need the following constraint.
Sample 1
AutoNDA by SimpleDocs

Related to Agreement alignment

  • Arrangement Agreement This Plan of Arrangement is made pursuant to, and is subject to the provisions of, the Arrangement Agreement, except in respect of the sequence of the steps comprising the Arrangement, which shall occur in the order set forth herein.

  • Modification of the Small Generating Facility The Interconnection Customer must receive written authorization from the NYISO and Connecting Transmission Owner before making any change to the Small Generating Facility that may have a material impact on the safety or reliability of the New York State Transmission System or the Distribution System. Such authorization shall not be unreasonably withheld. Modifications shall be done in accordance with Good Utility Practice. If the Interconnection Customer makes such modification without the prior written authorization of the NYISO and Connecting Transmission Owner, the Connecting Transmission Owner shall have the right to temporarily disconnect the Small Generating Facility. If disconnected, the Small Generating Facility will not be reconnected until the unauthorized modifications are authorized or removed.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Agreement Modification 15.1 Any agreement to change the terms of this Agreement in any way shall be valid only if the change is made in writing and approved by mutual agreement of authorized representatives of the parties hereto.

  • Agreement Modifications Neither this Agreement nor the Protocol may be altered, amended or modified except by written document signed by the parties. 20.

  • Provisioning Line Splitting and Splitter Space 3.8.1 The Data LEC, Voice CLEC or BellSouth may provide the splitter. When EZ Phone or its authorized agent owns the splitter, Line Splitting requires the following: a non-designed analog Loop from the serving wire center to the NID at the End User’s location; a collocation cross connection connecting the Loop to the collocation space; a second collocation cross connection from the collocation space connected to a voice port; the high frequency spectrum line activation, and a splitter. The Loop and port cannot be a Loop and port combination (i.e. UNE-P), but must be individual stand-alone Network Elements. When BellSouth owns the splitter, Line Splitting requires the following: a non designed analog Loop from the serving wire center to the NID at the End User’s location with CFA and splitter port assignments, and a collocation cross connection from the collocation space connected to a voice port.

  • PJM Agreement Modifications (a) If the PJM Agreements are amended or modified so that any schedule or section references herein to such agreements is changed, such schedule or section references herein shall be deemed to automatically (and without any further action by the Parties) refer to the new or successive schedule or section in the PJM Agreements which replaces that originally referred to in this Agreement.

  • Agreement; Amendment If either party hereto requests to amend this agreement, it shall notify the other party in writing, and the other party shall respond within one week. All amendments of this agreement must be made in writing by both parties, and such amendments shall be deemed as inseverable parts of this agreement.

  • INTEGRATION/MODIFICATION This Agreement constitutes the entire understanding and agreement between the Company and the Executive regarding its subject matter and supersedes all prior negotiations and agreements, whether oral or written, between them with respect to its subject matter. This Agreement may not be modified except by a written agreement signed by the Executive and a duly authorized officer of the Company.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

Time is Money Join Law Insider Premium to draft better contracts faster.