Services and Fees 2.1. Subject to the terms of this Agreement, DST will perform, with reasonable care, skill, prudence and diligence, and in accordance with applicable Law, for the Fund and, if and to the extent specifically set forth therein, the Services set forth in Schedule B and such other service schedules as may be added to this Agreement by the Parties (collectively, the “Service Schedules”). DST shall be under no duty or obligation to perform any service except as specifically listed in the Service Schedules, or take any other action except as specifically listed in a Service Schedules to this Agreement, or this Agreement, and no other duties or obligations, including, valuation related, fiduciary or analogous duties or obligations, shall be implied. Fund requests to change the Services, will only be binding on DST when they are reflected in an amendment to the Service Schedules. For the avoidance of doubt DST agrees to amend the Service Schedules if necessitated by a change in applicable Law or a change to the Governing Documents of the Fund. For clarification, this will include costs related changes to the software, systems or processes used by DST to provide the Services necessitated by change in applicable Law; provided in such case the Fund will only be responsible for its pro-rata share of such cost.
2.2. In carrying out its duties and obligations pursuant to this Agreement, some or all Services may, with the Fund’s prior written consent, be delegated by DST to one or more of its Affiliates or other Persons (and any Fund consent to such delegation, if any, shall not be unreasonably revoked or withheld in respect of any such delegations), provided that such Persons are selected in good faith and with reasonable care and are monitored by DST. If DST delegates any Services, (i) such delegation shall not relieve DST of its duties and obligations hereunder, (ii) such delegation shall be subject to a written agreement obliging the delegate to comply with the relevant delegated duties and obligations of DST, and (iii) DST will identify such agents and the Services delegated and will update the Fund when making any material changes in sufficient detail to enable the Fund to revoke its consent to a particular arrangement.
2.3. [ ]
2.4. Charges attendant to the development of reasonable changes to the TA2000 System requested by the Fund (“Client Requested Software”) shall be at DST's standard rates and fees in effect at the time as set forth in the Fee Letter. If the cost to DST of operating the TA2000 System is increased by the addition of Client Requested Software, DST shall be entitled to increase its fees by an amount to be mutually agreed upon in the Fee Letter.
Points and Fees No Mortgagor was charged “points and fees” (whether or not financed) in an amount greater than (i) $1,000, or (ii) 5% of the principal amount of such Mortgage Loan, whichever is greater. For purposes of this representation, such 5% limitation is calculated in accordance with Xxxxxx Mae’s anti-predatory lending requirements as set forth in the Xxxxxx Xxx Guides and “points and fees” (x) include origination, underwriting, broker and finder fees and charges that the mortgagee imposed as a condition of making the Mortgage Loan, whether they are paid to the mortgagee or a third party; and (y) exclude bona fide discount points, fees paid for actual services rendered in connection with the origination of the Mortgage Loan (such as attorneys’ fees, notaries fees and fees paid for property appraisals, credit reports, surveys, title examinations and extracts, flood and tax certifications, and home inspections), the cost of mortgage insurance or credit-risk price adjustments, the costs of title, hazard, and flood insurance policies, state and local transfer taxes or fees, escrow deposits for the future payment of taxes and insurance premiums, and other miscellaneous fees and charges which miscellaneous fees and charges, in total, do not exceed 0.25% of the principal amount of such Mortgage Loan. This representation and warranty is a Deemed Material and Adverse Representation;
Dues and Fees Grantee certifies that it is not prohibited from receiving an Award because it pays dues or fees on behalf of its employees or agents, or subsidizes or otherwise reimburses them for payment of their dues or fees to any club which unlawfully discriminates (775 ILCS 25/1 et seq.).
Payment and Fees 3.1 In consideration for the Token, Royalty Rights and Creator Related Rights, First Acquirer hereby agrees to pay to the Seller the price set out under the Special Terms (“Fee”). Without limiting any of the foregoing, the valid execution of this Agreement, grant of rights stated herein, and the delivery of the Token, is conditioned upon (i) First Acquirer’s payment and Seller’s receipt of the entire Fee in the Escrow Account, and (ii) providing a compatible network wallet address in the manner as set out on the Website, as to where the Token will be delivered. The Seller shall retain the amount specified in the Special Terms as agency Fees.
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).
Payment and Billing (a) STATION will, from time to time at intervals following broadcasts hereunder, bill AGENCY on behalf of Advertiser. AGENCY shall deliver payment to STATION at the address on the invoice within 15 days of the date of the invoice.
(b) Any time of terrestrial radio broadcast on an invoice shall be accurate within 15 minutes. Any invoice identifying commercial announcements and their date and time of broadcasts, when sworn to by STATION, shall constitute an affidavit of performance or proof-of- performance. All invoices shall be deemed to be correct unless proven otherwise.
(c) In the event that payment on any contract becomes past due and STATION in its sole discretion refers the contract to a collection agency or attorney for collection, the discount accorded to AGENCY under this contract will become null and void.
(d) STATION is entitled to the maximum interest allowable by law on any past due balance.
(e) In the event that STATION, in its sole discretion, refers this contract to a collection agency or attorney for collection, AGENCY will be responsible for all costs, including, but not limited to, reasonable attorney’s fees and costs and court costs, incurred.
(f) Notwithstanding to whom invoices are rendered, AGENCY and Advertiser, jointly and severally, shall remain obligated to pay to STATION (i) the amount of any invoices rendered by STATION within the time specified and until payment in full is received by STATION; and
(ii) any other amounts payable to STATION hereunder. Payment by Advertiser to AGENCY shall not constitute payment to STATION.
(g) In the event any commercial announcements under this contract are purchased pursuant to a cooperative advertising arrangement, AGENCY is acknowledged to be the agent of the source of the cooperative advertising funds (hereinafter called “Vendor”) and Vendor shall be jointly and severally liable with AGENCY and Advertiser for payment in full of the entire cost of said announcements within the time specified and until payment in full is received by STATION. Payment by Vendor to AGENCY or Advertiser shall not constitute payment to STATION.
COURSE INFORMATION AND FEES 1.1 The PEI will deliver the Course as set out in Schedule A to the Student, towards conferment of the stated qualification upon successful Course completion.
1.2 The PEI confirms that the Course has been permitted by the Council for Private Education (CPE) and no amendments have been made to the Course as set out in Schedule A, unless otherwise permitted by CPE.
1.3 The Course Fees payable are set out in Schedule B and the optional Miscellaneous Fees in Schedule C.
1.4 The PEI considers payment made 7 days after the scheduled due date(s) in Schedule B as late. The PEI will explain to the Student its policy for late payment of Course Fees, including any late payment fee charged in Schedule C (if applicable) and any impact on Course/module completion (if applicable).
Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement.
(b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice).
(c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation.
(d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must:
(i) summarise any comments received on the proposal;
(ii) set out the proposed amendment to be made (if any);
(iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised;
(iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and
(v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection.
(e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must:
(i) notify all Members and the AER of the amendment; and
(ii) publish the amendment and the amended Exchange Agreement on its website.
(f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.
Fees and Billing As a condition of use, Subscriber agrees to pay when due all fees and charges for the service package it purchases including any new or additional services, any Custom Services, and for extensions or renewals of the Service Period (“Fees”). Payments shall be made in accordance with Subscriber’s ordering documents. All Fees are payable without offset or deduction and within thirty days of invoice date. All Fees are non-cancellable and non- refundable for the entirety of the Term, and the number or duration of users, storage, subscriptions, features, usage or other Metric purchased cannot be decreased during the Subscription Term. Fees are fixed only for the initial Service Period and Ricoh reserves the right to change the Fees and/or its fee structure in subsequent or renewal periods. Charges for any Custom Services may be invoiced separately by Ricoh. Nonpayment of any Fees shall be grounds for suspension of Services or termination of this Agreement.
Searchability Offering searchability capabilities on the Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section.
1.10.1 Registry Operator will offer searchability on the web-‐based Directory Service.
1.10.2 Registry Operator will offer partial match capabilities, at least, on the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-‐fields described in EPP (e.g., street, city, state or province, etc.).
1.10.3 Registry Operator will offer exact-‐match capabilities, at least, on the following fields: registrar id, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records).
1.10.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT.
1.10.5 Search results will include domain names matching the search criteria.
1.10.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws or policies.
