Regulatory Applications (a) Western and PNB and their respective Subsidiaries shall cooperate and use their respective reasonable best efforts to prepare all documentation, to effect all filings and to obtain all permits, consents, approvals and authorizations of all third parties and Governmental Authorities necessary to consummate the transactions contemplated by this Agreement. Western and PNB shall use their reasonable best efforts to make all required bank regulatory filings, including the appropriate filing with the Regulatory Authorities. Each of Western and PNB shall have the right to review in advance, and to the extent practicable each will consult with the other, in each case subject to applicable laws relating to the exchange of information, with respect to all material written information submitted to any third party or any Governmental Authority in connection with the transactions contemplated by this Agreement. In exercising the foregoing right, each of the parties hereto agrees to act reasonably and as promptly as practicable. Each party hereto agrees that it will consult with the other party hereto with respect to the obtaining of all material permits, consents, approvals and authorizations of all third parties and Governmental Authorities necessary or advisable to consummate the transactions contemplated by this Agreement and each party will keep the other party appraised of the status of material matters relating to completion of the transactions contemplated hereby. (b) Each party agrees, upon request, to furnish the other party with all information concerning itself, its Subsidiaries, directors, officers and shareholders and such other matters as may be reasonably necessary or advisable in connection with any filing, notice or application made by or on behalf of such other party or any of its Subsidiaries to any third party or Governmental Authority.
Third-Party Applications Oracle or third party providers may offer Third Party Applications. Except as expressly set forth in the Estimate/Order Form, Oracle does not warrant any such Third Party Applications, regardless of whether or not such Third Party Applications are provided by a third party that is a member of an Oracle partner program or otherwise designated by Oracle as “Built For NetSuite,” "certified," "approved" or “recommended.” Any procurement by Customer of such Third Party Applications or services is solely between Customer and the applicable third party provider. Customer may not use Third Party Applications to enter and/or submit transactions to be processed and/or stored in the Cloud Service, unless Customer has procured the applicable subscription to the Cloud Service for such use and access.
Patent Applications It is understood by the parties that, pursuant to the Baylor Technology Transfer Agreement, MAS has the initial responsibility for filing, prosecution and maintenance of Patents and Patent Applications covering the Baylor Technology. The parties agree that, as between MAS and CTI, MAS shall be responsible for deciding whether and how to file, prosecute and maintain the Patents and Patent Applications, provided that: (a) all decisions of MAS (whether substantive or procedural) concerning whether and how to file, prosecute and/or maintain any Patents and Patent Applications shall be acceptable to CTI, such acceptance not to be unreasonably withheld; (b) with respect to any action permitted under Section 5.5 of the Baylor Technology Transfer Agreement or Section 5.5 of this Agreement, MAS will use legal counsel reasonably acceptable to CTI; (c) MAS will provide CTI with (i) drafts of all filings relating to the Patents and Patent Applications and (ii) drafts of all correspondence to be sent by MAS to Baylor, the Patent and Trademark Office (the “PTO”) or any third party relating to the Patents and Patent Applications. Final versions of all such filings and correspondence shall be acceptable to CTI, such acceptance not to be unreasonably withheld; (d) MAS will promptly provide CTI with copies of any notices and other correspondence received by CTI from Baylor, the PTO or any other third party relating to the Patents and Patent Applications, including, but not limited to, any notices received by MAS pursuant to Section 5.5 of the Baylor Technology Transfer Agreement; (e) MAS will, if requested by CTI, provide notice to Baylor under any of the circumstances permitting notice pursuant to Section 5.5 of the Baylor Technology Transfer Agreement; (f) MAS agrees to cooperate with CTI to whatever extent is reasonably necessary to procure patent protection of any rights regarding the Licensed Technology and agrees to execute any and all documents to give CTI the full benefit of the sublicenses and licenses granted herein; (g) MAS represents and warrants that, as of the Effective Date, it has not received any notices from Baylor pursuant to Section 5.5(c) or Section 5.5(d) of the Baylor Technology Transfer Agreement. In the event MAS receives any notices from Baylor pursuant to Section 5.5(c) or Section 5.5(d) of the Baylor Technology Transfer Agreement after the Effective Date. MAS will provide a copy of such notice to CTI within five (5) business days of receipt of such notice by MAS. MAS will then take all actions requested by CTI to allow CTI to retain its rights granted under this Agreement, including, but not limited to, promptly notifying Baylor in the event CTI wishes MAS to proceed with any actions in connection with the Patents or Patent Applications.
Provisional Application Upon signature of this Compact, and until this Compact has entered into force in accordance with Section 7.3, the Parties will provisionally apply the terms of this Compact; provided that, no MCC Funding, other than Compact Implementation Funding, will be made available or disbursed before this Compact enters into force.
Applications To the extent that any provision of any Application related to any Letter of Credit is inconsistent with the provisions of this Section 3, the provisions of this Section 3 shall apply.
File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.
Application for approval 3.1. The application for approval of a vehicle type with regard to the AEBS shall be submitted by the vehicle manufacturer or by his authorised representative. 3.2. It shall be accompanied by the documents mentioned below in triplicate: 3.2.1. A description of the vehicle type with regard to the items mentioned in paragraph 2.4., together with a documentation package which gives access to the basic design of the AEBS and the means by which it is linked to other vehicle systems or by which it directly controls output variables. The numbers and/or symbols identifying the vehicle type shall be specified. 3.3. A vehicle representative of the vehicle type to be approved shall be submitted to the Technical Service conducting the approval tests.
Application of Takeover Protections The Company and the Board of Directors have taken all necessary action, if any, in order to render inapplicable any control share acquisition, business combination, poison pill (including any distribution under a rights agreement) or other similar anti-takeover provision under the Company’s certificate of incorporation (or similar charter documents) or the laws of its state of incorporation that is or could become applicable to the Purchasers as a result of the Purchasers and the Company fulfilling their obligations or exercising their rights under the Transaction Documents, including without limitation as a result of the Company’s issuance of the Securities and the Purchasers’ ownership of the Securities.
Listing Application If shares of any class of stock of the Company shall be listed on a national securities exchange, the Company shall, at its expense, include in its listing application all of the shares of the listed class then owned by any Investor.
General Application The rules set forth below in this Article VI shall apply for the purposes of determining each Member’s allocable share of the items of income, gain, loss and expense of the Company comprising Net Income or Net Loss for each Fiscal Year, determining special allocations of other items of income, gain, loss and expense, and adjusting the balance of each Member’s Capital Account to reflect the aforementioned general and special allocations. For each Fiscal Year, the special allocations in Section 6.03 hereof shall be made immediately prior to the general allocations of Section 6.02 hereof.
