Discussion Paper Sample Clauses

Discussion Paper. Proceedings of the Workshop on Space Law in the Twenty- first Century, UNISPACE III Technical Forum, July 1999, Doc. A/CONF 194/7, pp. 11-19. Cited from Xxxxxx-Xxxxx & Xxxxxxx (2019), supra note 7, p. 15. 63 Art. 27, VCLT.
Sample 1Sample 2
AutoNDA by SimpleDocs
Discussion Paper a) The University shall initiate a consultation process which will include issuing a discussion paper to those staff likely to be directly affected that describes the proposed workplace change, or options under consideration and the rationale for change. The discussion paper shall include all relevant details of the changes proposed, the effects the changes are likely to have on staff, timeframes for consultation and implementation where relevant and measures to avert or minimise any adverse effects on staff. b) The University shall provide the discussion paper to affected staff and the relevant union(s) at least ten (10) working days prior to a management initiated meeting to consult on the change proposals. Affected staff should be provided with reasonable opportunity to attend the meeting. Staff present at the meeting will have the opportunity to raise issues and have them identified and acknowledged.
Sample 1Sample 2
Discussion Paper. 217 218As soon as practicable after deciding to hold a public inquiry under Section 149 into any matter, the Commission shall cause to be prepared a discussion paper that–
Sample 1
Discussion Paper. 42.4.1 The Guild will issue documentation (the Discussion Paper) to employees likely to be directly affected and to the NTEU, if it is anticipated that one or more of the following will occur: (i) Relocating employees to another campus of the University; or (ii) Restructuring; or (iii) Outsourcing. 42.4.2 The Discussion Paper will address the following points: (i) The proposed time frame for examination of the change proposal; and (ii) The nature of the change proposal; and (iii) The reasons/aims for making the change; and (iv) Relevant financial information including cost benefits; and (v) Anticipated redundancies; and (vi) Relevant staffing matters including organisational charts and proposed changes to duties and position descriptions; and (vii) Any workload implications; and (viii) Equity and OSH implications; and (ix) Where identified, training requirements. The Discussion Paper will be discussed at a Change Management Committee if there are to be significant effects on five or more staff.
Sample 1

Related to Discussion Paper

  • Discussions Within 14 days of the date of the notice under Clause 23.2 (Advance Notice) of this article, the Union and the Employer will commence discussions for the purpose of reaching agreement as to the effects of the technological change and in what way, if any, this agreement should be amended.

  • Discussion of Differences If a difference arises between the Employer and an employee(s) or between the Employer and the Union concerning the interpretation, application, operation or any alleged violation of the Agreement, the employee(s) shall continue to work in accordance with the Agreement until the difference is settled.

  • Discussion Staff has reviewed the proposal relative to all relevant policies and advise that it is reasonably consistent with the intent of the MPS. Attachment B provides an evaluation of the proposed development agreement in relation to the relevant MPS policies.

  • Negotiations At the written request of a Party, each Party will appoint a knowledgeable, responsible representative to meet and negotiate in good faith to resolve any dispute arising out of or relating to this Agreement. The Parties intend that these negotiations be conducted by non-lawyer, business representatives. The location, format, frequency, duration, and conclusion of these discussions shall be left to the discretion of the representatives. Upon agreement, the representatives may utilize other alternative dispute resolution procedures such as mediation to assist in the negotiations. Discussions and correspondence among the representatives for purposes of these negotiations shall be treated as confidential information developed for purposes of settlement, exempt from discovery, and shall not be admissible in the arbitration described below or in any lawsuit without the concurrence of all Parties. Documents identified in or provided with such communications, which are not prepared for purposes of the negotiations, are not so exempted and may, if otherwise discoverable, be discovered or otherwise admissible, be admitted in evidence, in the arbitration or lawsuit.

  • Mutual Discussions The Employer and the Union acknowledge the mutual benefits to be derived from dialogue between the parties and are prepared to discuss matters of common interest.

  • Ongoing Compliance of the Offering Memorandum If at any time prior to the completion of the initial offering of the Securities (i) any event shall occur or condition shall exist as a result of which the Offering Memorandum as then amended or supplemented would include any untrue statement of a material fact or omit to state any material fact necessary in order to make the statements therein, in the light of the circumstances existing when the Offering Memorandum is delivered to a purchaser, not misleading or (ii) it is necessary to amend or supplement the Offering Memorandum to comply with law, the Company will immediately notify the Initial Purchasers thereof and forthwith prepare and, subject to paragraph (b) above, furnish to the Initial Purchasers such amendments or supplements to the Offering Memorandum (or any document to be filed with the Commission and incorporated by reference therein) as may be necessary so that the statements in the Offering Memorandum as so amended or supplemented (including such document to be incorporated by reference therein) will not, in the light of the circumstances existing when the Offering Memorandum is delivered to a purchaser, be misleading or so that the Offering Memorandum will comply with law.

  • Negotiated Agreement (1) This Settlement Agreement has been the subject of negotiations and discussions among the undersigned, each of which has been represented and advised by competent counsel, so that any statute, case law, or rule of interpretation or construction that would or might cause any provision to be construed against the drafter of this Settlement Agreement shall have no force and effect. The Parties further agree that the language contained in or not contained in previous drafts of this Settlement Agreement, or any agreement in principle, shall have no bearing upon the proper interpretation of this Settlement Agreement.

  • Agreement Review If, pursuant to section 25.10 (Review of Agreement) of the Bilateral Agreement, the Bilateral Agreement is reviewed after three or five years, or both, of the effective date of the Bilateral Agreement, and any changes to the Bilateral Agreement are required as a result, the Parties agree to amend the Agreement as necessary and in a manner that is consistent with such changes.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Investment Representation Statement Unless the rights under this Warrant are exercised pursuant to an effective registration statement under the Securities Act that includes the Shares with respect to which the Warrant was exercised, it shall be a condition to any exercise of the rights under this Warrant that the Holder shall have confirmed to the satisfaction of the Company in writing, substantially in the form of Exhibit A-1, that the Shares so purchased are being acquired solely for the Holder’s own account and not as a nominee for any other party, for investment and not with a view toward distribution or resale and that the Holder shall have confirmed such other matters related thereto as may be reasonably requested by the Company.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!