Datacom Note
Datacom Note Sample Clauses
Related to Datacom Note
Supplier Note Thank you for the opportunity
Term Note The Term Loan shall be evidenced by the Term Note. At the time of the disbursement of the Term Loan or a repayment made in whole or in part thereon, a notation thereof shall be made on the books and records of the Bank. All amounts recorded shall be, absent demonstrable error, conclusive and binding evidence of (i) the principal amount of the Term Loan advanced hereunder, (ii) any accrued and unpaid interest owing on the Term Loan and (iii) all amounts repaid on the Term Loan. The failure to record any such amount or any error in recording such amounts shall not, however, limit or otherwise affect the joint and several obligations of the Borrowers under the Term Note to repay the principal amount of the Term Loan, together with all interest accruing thereon.
Promissory Note The Promissory Note is enclosed. The Chief Financial Officer is required to sign it and return it to the OPWC Loan Officer, Xxxxx XxXxxx. It is preferable that you scan and email it to her at Xxxxx.XxXxxx@xxx.xxxxx.xx.xx but may also mail it to the address on our letterhead. Only use one method.
Compiler’s note On April 16, 2005 Section 705 was added and was effective upon adoption.
NOTE For Community-‐Based TLDs Only] Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]
System Security (a) If any party hereto is given access to the other party’s computer systems or software (collectively, the “Systems”) in connection with the Services, the party given access (the “Availed Party”) shall comply with all of the other party’s system security policies, procedures and requirements that have been provided to the Availed Party in advance and in writing (collectively, “Security Regulations”), and shall not tamper with, compromise or circumvent any security or audit measures employed by such other party. The Availed Party shall access and use only those Systems of the other party for which it has been granted the right to access and use. (b) Each party hereto shall use commercially reasonable efforts to ensure that only those of its personnel who are specifically authorized to have access to the Systems of the other party gain such access, and use commercially reasonable efforts to prevent unauthorized access, use, destruction, alteration or loss of information contained therein, including notifying its personnel of the restrictions set forth in this Agreement and of the Security Regulations. (c) If, at any time, the Availed Party determines that any of its personnel has sought to circumvent, or has circumvented, the Security Regulations, that any unauthorized Availed Party personnel has accessed the Systems, or that any of its personnel has engaged in activities that may lead to the unauthorized access, use, destruction, alteration or loss of data, information or software of the other party hereto, the Availed Party shall promptly terminate any such person’s access to the Systems and immediately notify the other party hereto. In addition, such other party hereto shall have the right to deny personnel of the Availed Party access to its Systems upon notice to the Availed Party in the event that the other party hereto reasonably believes that such personnel have engaged in any of the activities set forth above in this Section 9.2(c) or otherwise pose a security concern. The Availed Party shall use commercially reasonable efforts to cooperate with the other party hereto in investigating any apparent unauthorized access to such other party’s Systems.
DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.04, the parties acknowledge that the Direct Registration System (“DRS”) and Profile Modification System (“Profile”) shall apply to uncertificated American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC pursuant to which the Depositary may register the ownership of uncertificated American Depositary Shares, which ownership shall be evidenced by periodic statements issued by the Depositary to the Owners entitled thereto. Profile is a required feature of DRS which allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register such transfer. (b) In connection with and in accordance with the arrangements and procedures relating to DRS/Profile, the parties understand that the Depositary will not verify, determine or otherwise ascertain that the DTC participant which is claiming to be acting on behalf of an Owner in requesting a registration of transfer and delivery as described in subsection (a) has the actual authority to act on behalf of the Owner (notwithstanding any requirements under the Uniform Commercial Code). For the avoidance of doubt, the provisions of Sections 5.03 and 5.08 shall apply to the matters arising from the use of the DRS. The parties agree that the Depositary’s reliance on and compliance with instructions received by the Depositary through the DRS/Profile System and in accordance with this Deposit Agreement shall not constitute negligence or bad faith on the part of the Depositary.
Amendments to Purchase Agreement The parties agree that the Purchase Agreement shall be amended, solely with respect to the Mortgage Loans, as follows:
Receivables Not To Be Evidenced by Promissory Notes Except in connection with its enforcement or collection of an Account, the Servicer will take no action to cause any Receivable to be evidenced by an instrument (as defined in the UCC as in effect in the State of Delaware).
The Security Agreement The security interest granted pursuant to this Trademark Security Agreement is granted in conjunction with the security interest granted to the Collateral Agent pursuant to the Security Agreement and Grantor hereby acknowledges and affirms that the rights and remedies of the Collateral Agent with respect to the security interest in the Trademarks made and granted hereby are more fully set forth in the Security Agreement. In the event that any provision of this Trademark Security Agreement is deemed to conflict with the Security Agreement, the provisions of the Security Agreement shall control unless the Collateral Agent shall otherwise determine.
