Interface Information Sample Clauses

Interface Information. From time to time at the request of TWC, Seller shall promptly disclose to TWC (subject to Seller’s confidentiality obligations to third parties and TWC’s confidentiality obligations under this Agreement) all Equipment external interface specifications, APIs, protocols and other tangible interface information not defined or otherwise provided by TWC that TWC or a third party manufacturer would reasonably require to have TWC’s head-end and other System equipment conform to such interfaces for the sole purpose of being interoperable with the Equipment (“Interface Information”). All Interface Information shall sufficiently describe the details of the external interfaces not defined or otherwise provided by TWC to the Equipment in order to allow TWC and its third party manufacturer to understand such interfaces for the sole purpose of being interoperable with the Equipment. Seller hereby grants to the Purchasers a world-wide, non-exclusive, perpetual, irrevocable (except for a material breach of this Agreement), non-transferable (except as permitted under Section 27.5), royalty-free, fully paid-up license, under any of Seller’s IP Rights embodied in the Interface Information, if any, that are necessary to access, copy, disclose, modify and create derivative works directly from such Interface Information for the sole purpose of maintaining interoperability of TWC’s head-end and other System equipment with the Equipment in order to use the Equipment. During the Term, upon TWC’s request, Seller shall provide technical support and consultation to assist TWC in understanding and applying the Interface Information. Such technical support and consultation shall be provided at Seller’s then-current, standard consulting rates. Except for the express licenses granted in this Agreement, there are no other rights or licenses to any IP Rights conveyed under this Agreement by reason of implication, estoppel or otherwise.
Sample 1Sample 2
AutoNDA by SimpleDocs
Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
Sample 1Sample 2
Interface Information. During the Term of this Agreement, Supplier will provide WaMu with appropriate interface information to enable WaMu to develop or replace any Software that is not commercially available. After the termination or expiration of each Service Agreement, Supplier will provide WaMu with appropriate interface information to enable WaMu to develop or replace any Supplier Software if necessary for WaMu to exercise any of the rights granted to it under such Service Agreement.
Sample 1
Interface Information. 39 20.5 Residual Information..................................................................... 39 ARTICLE 21. DATA................................................................................... 39 21.1 Ownership of Xxxx Data................................................................... 39 21.2 Return of Data........................................................................... 39 ARTICLE 22. CONFIDENTIALITY........................................................................ 39 22.1 Use and Disclosure....................................................................... 39
Sample 1
Interface Information. During the Term of this Agreement, Service Provider will provide Xxxx with appropriate interface information to enable Xxxx to develop or replace any Software used to provide the Services that is not commercially available. After the termination or expiration of this Agreement, Service Provider will provide Xxxx with appropriate interface information available from Service Provider to enable Xxxx to develop or replace any Service Provider Software if necessary for Xxxx to exercise any of the rights granted to it under this Agreement.
Sample 1
Interface Information. During the Term of this Agreement, Service Provider will provide Dxxx with appropriate interface information to enable Dxxx to develop or replace any Software used to provide the Services that is not commercially available. After the termination or expiration of this Agreement, Service Provider will provide Dxxx with appropriate interface information available from Service Provider to enable Dxxx to *** indicates where a confidential portion has been omitted and filed separately with the Commission develop or replace any Service Provider Software if necessary for Dxxx to exercise any of the rights granted to it under this Agreement.
Sample 1

Related to Interface Information

  • Service Information Service Visit Date

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Accurate Information All information heretofore, herein or hereafter supplied to Secured Party by or on behalf of Debtor with respect to the Collateral is and will be accurate and complete in all material respects.

  • CONTRACT INFORMATION 1. The State of Arkansas may not contract with another party: a. Upon default, to pay all sums to become due under a contract. b. To pay damages, legal expenses or other costs and expenses of any party. c. To conduct litigation in a place other than Pulaski County, Arkansas d. To agree to any provision of a contract; which violates the laws or constitution of the State of Arkansas. 2. A party wishing to contract with the State of Arkansas should: a. Remove any language from its contract which grants to it any remedies other than: i. The right to possession. ii. The right to accrued payments. iii. The right to expenses of de-installation. iv. The right to expenses of repair to return the equipment to normal working order, normal wear and tear excluded. v. The right to recover only amounts due at the time of repossession and any unamortized nonrecurring cost as allowed by Arkansas Law. b. Include in its contract that the laws of the State of Arkansas govern the contract. c. Acknowledge that contracts become effective when awarded by the State Procurement Official.

  • Notice Information Notice identifier/version: 557b600a-d52f-4303-8110-b3d46b2b781b - 01 Form type: Competition Notice type: Contract or concession notice – standard regime Notice dispatch date: 26/07/2024 10:09 +01:00 Languages in which this notice is officially available: English

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment. 5.2 If a ECI Customer is served by resold Verizon dial tone line Telecommunications Service or a Verizon Local Switching UNE, to the extent reasonably feasible, Verizon will route Voice Information Service Traffic originating from such Service or UNE to the appropriate Voice Information Service connected to Verizon’s network unless a feature blocking such Voice Information Service Traffic has been installed. For such Voice Information Service Traffic, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its Customer. 5.3 ECI shall have the option to route Voice Information Service Traffic that originates on its own network to the appropriate Voice Information Service connected to Verizon’s network. In the event ECI exercises such option, ECI will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow ECI to route Voice Information Service Traffic originated on its network to Verizon. For such Voice Information Service Traffic, unless ECI has entered into a written agreement with Verizon under which ECI will collect from ECI’s Customer and remit to Verizon the Voice Information Service provider’s charges, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its own Customer.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • SITE INFORMATION General description

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

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