BY ABX Sample Clauses

BY ABX. Subject to JTA's compliance with Section 3.3, ABX agrees to indemnify, defend and hold JTA and its Affiliates and their directors, officers, employees, and agents harmless from and against any Liabilities arising from the breach of any representations, warranties, covenants or other obligations of ABX under this Agreement, except to the extent that such Liabilities arise from JTA's breach of any of its representations, warranties, covenants or other obligations under this Agreement.
AutoNDA by SimpleDocs
BY ABX. Subject to the terms and conditions of this Agreement, with respect to each Collaboration Antigen (other than Discontinued Antigens or Failed Antigens), prior to the designation of a Candidate Drug that binds to and is directed against such Collaboration Antigen, ABX and its Affiliates hereby grant to AZ an exclusive, worldwide right and license (without the right to grant sublicenses except as set forth in Section 4.2.3) under and to the Licensed ABX IP Rights applicable to such Collaboration Antigen, to conduct its obligations, and exercise its rights, under the applicable Research Program, Development Program and Articles 2 and 5; provided, however, that ABX retains the right to conduct its activities under such Research Program and, prior to the designation of a Candidate Drug that binds to and is directed against such Collaboration Antigen, such Development Program.
BY ABX. Subject to the terms and conditions of this Agreement and any applicable ABX In-License, with respect to each Discontinued Antigen, Failed Antigen and Non-Selected Antigen, ABX and its Affiliates hereby grant to AZ (a) the non-exclusive, worldwide right and license (with the right to grant sublicenses through multiple tiers of sublicensees) under the ABX Subsequent Antigen-Specific Know-How Rights and ABX Subsequent Antigen-Specific Patent Rights applicable to each such Antigen to Exploit Non-Licensed Products (other than Non-Antibody Products) that bind to and are directed against such Antigen for use in the Commercial Field, and (b) the exclusive, worldwide right and license (with the right to grant sublicenses through multiple tiers of sublicensees) under the ABX Subsequent Antigen-Specific Know-How Rights and ABX Subsequent Antigen-Specific Patent Rights applicable to each such Antigen to Exploit Non-Antibody Products with respect to such Antigen for use in the Commercial Field.
BY ABX. Subject to JTI's compliance with Section 8.3, ABX agrees to indemnify, defend and hold JTI and its Affiliates and their respective directors, officers, employees and agents harmless from and against any Liabilities arising from (a) any negligence or willful misconduct of ABX or its Affiliates (or their respective directors, officers, employees, agents or Affiliates) or (b) the breach of any representations, warranties, covenants or other obligations of ABX under this Agreement, except to the extent that such Liabilities arise from (i) the negligence or willful misconduct of JTI or its Affiliates or Sublicensees or their respective directors, officers, employees, agents, or (ii) the breach of any of the representations, warranties, covenants or other obligations of JTI under this Agreement.
BY ABX. Subject to the terms and conditions of this Agreement, ABX hereby grants to PSMA an exclusive license under the Licensed ABX IP Rights (a) to use the XenoMouse Animals provided by ABX solely for immunization with the Antigen for the generation, creation and identification of Antibodies that bind specifically to the Antigen, (b) to make, have made by permitted transferees specified in Section 4.1.2 and use (but not to transfer (except as provided in Section 4.1.2 below), sell, lease, offer to sell or lease, or otherwise transfer title to or an interest in) Antibody Cells that contain, express or secrete Antibodies that bind specifically to the Antigen, or Genetic Material that encodes such Antibodies, solely for use in the Research Field, (c) to make, have made by permitted transferees specified in Section 4.1.2 and use (but not to transfer (except as provided in Section 4.1.2 below), sell, lease, offer to sell or lease, or otherwise transfer title to or an interest in) Antibodies that bind specifically to the Antigen, or Genetic Material that encodes such Antibodies, and (d) to engage in such other research and development activities as may be reasonably incidental to the foregoing, in each case solely for the research and development of such Antibodies in the Research Field. Except as expressly set forth in Section 4.3 or 8.1 below, PSMA shall not use the Licensed ABX IP Rights, the ABX Technology or any materials or information derived therefrom (including, without limitation, Antibodies, Genetic Material encoding Antibodies, and Antibody Cells) for any other use.
BY ABX. Subject to JTI's compliance with Section 6.3, ABX agrees to indemnify, defend and hold JTI and its Affiliates and their directors, officers, employees and agents harmless from and against any Liabilities arising from (i) any negligence or willful misconduct of ABX (or its directors, officers, employees, or agents); (ii) the breach of any representations, warranties, covenants or other obligations of ABX under this Agreement, (iii) ABX's or its Affiliates' activities under the MRLOA after the Effective Date, and (iv) any failure by ABX to pay any withholding taxes due to a government authority in connection with ABX's performance of its obligations and exercise of its rights under this Agreement (whether such taxes are paid by ABX at the time of payment to JTI or imposed upon ABX by the relevant authority at a later date), except in each case to the extent that such Liabilities arise from JTI's negligence or willful misconduct or breach of any of its representations, warranties, covenants or other obligations under this Agreement.

Related to BY ABX

  • Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at xxxxxxx@xxx.xxxxxxxxx.xxx.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.

  • Procurement of Recovered Materials In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

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