Minimum Conditions for Using Shared Patent Library Sample Clauses

Minimum Conditions for Using Shared Patent Library. Any arrangement entered into by the patent owner, requesting member and COPA (if applicable) must include at least the following requirements: (1) patent owner will join any defensive legal proceeding initiated by or for the benefit of the requesting member as necessary, (2) patent owner will provide reasonable cooperation and assistance, (3) if the patent owner needs to use the patent, the requesting member and COPA (if applicable) will provide reasonable cooperation and assistance, (4) the requesting member will diligently enforce and defend the requested crypto-technology patents, (5) the requesting member will be responsible for all costs, and (6) damages will be pooled and applied first to reimburse the requesting member for the costs it incurred, with the remaining to be transferred to the patent owner. The Parties agree that any arrangement entered into between the Owner Member, Defending Member and COPA (if applicable) under Section 4 of this Exhibit C will include at least the following conditions:
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Minimum Conditions for Using Shared Patent Library

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • 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.

  • GEOGRAPHIC AREA AND SECTOR SPECIFIC ALLOWANCES, CONDITIONS AND EXCEPTIONS The following allowances and conditions shall apply where relevant: Where the company does work which falls under the following headings, the company agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

  • 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.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • 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:

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Secondary / Post-Secondary Program Alignment Welding HIGH SCHOOL COURSE SEQUENCE 9th Grade 10th Grade 11th Grade 12th Grade English 9 Algebra I World History/Geography Biology World Language Phys Ed/Health English 10 Geometry U.S. History/Geography Physics or Chemistry World Language Visual/Performing/Applied Arts English 11 Algebra II Civics/Economics Welding English 12 Math Credit Science Credit Welding WASHTENAW COMMUNITY COLLEGE Welding Associate in Applied Science Semester 1 Math Elective(s)* 3 WAF 105 Introduction to Welding Processes 2 WAF 111 Oxy-fuel Welding 4 WAF 112 Shielded Metal Arc Welding 4 Semester Total 13 Semester 2 Speech Elective(s) 3 WAF 106 Blueprint Reading for Welders 3 WAF 123 Advanced Oxy-fuel Welding 4 WAF 124 Advanced Shielded Metal Arc Welding 4 Semester Total 14 Semester 3 Arts/Human. Elective(s) 3 Computer Lit. Elective(s) 3 WAF 215 Advanced Gas Tungsten Arc Welding 4 WAF 288 Gas Metal Arc Welding 4 Semester Total 14 Semester 4 WAF 200 Layout Theory Welding 3 WAF 210 Welding Metallurgy 3 Soc. Sci. Elective(s) 3 WAF 226 Specialized Welding Procedures 4 Semester Total 13 Semester 5 Nat. Sci. Elective(s) 4 WAF 227 Basic Fabrication 3 WAF 229 Shape Cutting Operations 3 Writing Elective(s) 3 Semester Total 13 Program Totals 67

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