More Specific Basis Sample Clauses

More Specific Basis. For and Manner of Use of" IBM San Francisco" -The trademark "IBM San Francisco" consists of two portions "IBM," which is a registered trademark, and "San Francisco," which, as of the date of this Agreement, is not registered. Under no circumstances are YOU permitted to use the trademark "IBM" in a design or logotype form or as a trademark separate and apart from the words "San Francisco."
AutoNDA by SimpleDocs

Related to More Specific Basis

  • State Specific Provisions N/A. ATTACHED EXHIBIT. The Exhibit noted below, if marked with an "X" in the space provided, is attached to this Note: X Exhibit A Modifications to Multifamily Note

  • ESTIMATED / SPECIFIC QUANTITY CONTRACTS Estimated quantity contracts, also referred to as indefinite delivery / indefinite quantity contracts, are expressly agreed and understood to be made for only the quantities, if any, actually ordered during the Contract term. No guarantee of any quantity is implied or given. With respect to any specific quantity stated in the contract, the Commissioner reserves the right after award to order up to 20% more or less (rounded to the next highest whole number) than the specific quantities called for in the Contract. Notwithstanding the foregoing, the Commissioner may purchase greater or lesser percentages of Contract quantities should the Commissioner and Contractor so agree. Such agreement may include an equitable price adjustment.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • State Specific Contract Form Observe the state of the Seller on the Contract, if the Seller lists an address in Alaska, Arkansas, Delaware, North Carolina, Virginia, Maryland, Montana, Connecticut, Vermont, Louisiana or Mississippi, confirm the form number on the Contract is on the List of Approved Contract Forms, for the corresponding state.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:

  • Country-Specific Provisions The Award shall be subject to any special provisions set forth in Exhibit A for your country, if any. If you relocate to one of the countries included in Exhibit A during the life of the Award or while holding Shares acquired upon vesting of the Restricted Share Units, the special provisions for such country shall apply to you, to the extent the Company determines that the application of such provisions is necessary or advisable in order to comply with applicable laws with regard to the acquisition, issuance or sale of the Shares or facilitate the administration of the Plan. Exhibit A constitutes part of this Agreement.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Measuring DNS parameters Every minute, every DNS probe will make an UDP or TCP “DNS test” to each of the public-­‐DNS registered “IP addresses” of the name servers of the domain name being monitored. If a “DNS test” result is undefined/unanswered, the tested IP will be considered unavailable from that probe until it is time to make a new test.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Product Specific Terms these terms apply to specific Products referenced in this section.

Time is Money Join Law Insider Premium to draft better contracts faster.