Removal of Reserved Antigens from Reserved Antigen List Sample Clauses

Removal of Reserved Antigens from Reserved Antigen List. If (a) any Target Selection Right expires without having been exercised by Xxxxxxx pursuant to Section 3.2.5 or (b) a Target Selection Date occurs following the exercise of Xxxxxxx’x exercise of its Target Selection Right pursuant to Section 3.2, then (in each case (a) or (b)) Xxxxxxx shall remove from the Reserved Antigen List such number of Reserved Antigens as is necessary so that the Reserved Antigens do not exceed the Maximum Reserved Antigen Amount. Under (a) or (b) above, unless a Proposed Target was a Reserved Antigen, Xxxxxxx will provide written notice to Mersana of the Reserved Antigens to be removed from the Reserved Antigen List in the applicable Proposed Target Notice or within [**] following the expiration of the Target Selection Right or the Target Selection Date, as applicable; [**]. The Reserved Antigens specified in Xxxxxxx’x notice [**] will automatically be deemed to be removed from the Reserved Antigen List upon receipt of the applicable notification by Mersana [**], and will no longer be deemed Reserved Antigens. Under (b) above, if a Proposed Target was a Reserved Antigen, then the Reserved Antigen that was selected as a Target will be automatically removed from the Reserved Antigen List upon the occurrence of the Target Selection Date, and will no longer be deemed a Reserved Antigen. For clarity, the Reserved Antigens removed from the Reserved Antigen List will no longer be subject to exclusivity under Section 5.5.1.
AutoNDA by SimpleDocs

Related to Removal of Reserved Antigens from Reserved Antigen List

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • SCHEDULE OF RESERVED NAMES Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-­‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Completion of Concrete Pours and Emergency Work (a) Except as provided in this sub-clause an Employee shall nor work or be required to work in the rain. (b) Employees shall not be required to start a concrete pour in Inclement Weather. (c) Where a concrete pour has been commenced prior to the commencement of a period of Inclement Weather Employees may be required to complete such concrete pour to a practical stage and for such work shall be paid at the rate of double time calculated to the next hour, and in the case of wet weather shall be provided with adequate wet weather gear. (d) If an Employee’s clothes become wet as a result of working in the rain during a concrete pour the Employee shall, unless the Employee has a change of dry working clothes available, be allowed to go home without loss of pay. (e) The provisions of clauses 32.7(c) and 32.7(d) hereof shall also apply in the case of emergency work where the Employees concerned and their delegates agree that the work is of an emergency nature and can start and/or proceed.

  • Reserved Names Except to the extent that ICANN otherwise expressly authorizes in writing, Registry Operator shall comply with the requirements set forth in Specification 5 attached hereto (“Specification 5”). Registry Operator may at any time establish or modify policies concerning Registry Operator’s ability to reserve (i.e., withhold from registration or allocate to Registry Operator, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within the TLD at its discretion. Except as specified in Specification 5, if Registry Operator is the registrant for any domain names in the registry TLD, such registrations must be through an ICANN accredited registrar, and will be considered Transactions (as defined in Section 6.1) for purposes of calculating the Registry-­‐level transaction fee to be paid to ICANN by Registry Operator pursuant to Section 6.1.

  • CONDITIONS FOR EMERGENCY/HURRICANE OR DISASTER - TERM CONTRACTS It is hereby made a part of this Invitation for Bids that before, during and after a public emergency, disaster, hurricane, flood, or other acts of God that Orange County shall require a “first priority” basis for goods and services. It is vital and imperative that the majority of citizens are protected from any emergency situation which threatens public health and safety, as determined by the County. Contractor agrees to rent/sell/lease all goods and services to the County or other governmental entities as opposed to a private citizen, on a first priority basis. The County expects to pay contractual prices for all goods or services required during an emergency situation. Contractor shall furnish a twenty-four (24) hour phone number in the event of such an emergency.

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • Reserved for Future Use Reserved for Future Use

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