Implementation of Technical Specifications Sample Clauses

Implementation of Technical Specifications. The latency and availability in this Exhibit shall only apply provided that (a) Customer correctly implements the technical specifications concerning correct use of XML protocol arguments and correct handling of optional or new result fields set forth in the Google Data Protocol, (b) Customer’s DNS client implementation correctly observes the DNS TTL values returned by Google’s DNS servers, i.e., if Customer’s DNS client does not cache values beyond the TTL tima, and c) Customer sends Queries to the host name provided to customer by Google (e.g. XXX.xxxxxx.xxx) and Customer’s client implementation repeats the DNS lookups at least every 5 seconds in order to pick up any changes.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Implementation of Technical Specifications. As soon as reasonably possible after the Effective Date, Customer shall implement Ask Jeeves’ software code to the Site(s) so as to enable Customer to transmit Queries from the Site(s) to Ask Jeeves and for Ask Jeeves to respond with Search Services to the Site(s). The Search Services shall only be available to Customer provided that Customer complies in full with the following: (a) Customer shall correctly implement the Ask Jeeves’ technical specifications concerning correct use of XML protocol arguments and correct handling of optional or new result fields set forth by Ask Jeeves; (b) Customer’s DNS client implementation shall correctly observe the DNS TTL values returned by Ask Jeeves’ DNS servers, i.e., if Customer’s DNS client does not cache values beyond the TTL time; and (c) Customer shall send Queries to the host name provided to Customer by Ask Jeeves and Customer’s client implementation shall repeat the DNS lookups at least every five (5) seconds in order to pick up any changes.
Sample 1Sample 2
Implementation of Technical Specifications. The latency and availability in this Exhibit B-1 shall only apply provided that (a) CNN implements the technical specifications concerning correct use of XML protocol arguments and correct handling of optional or new result fields set forth in the Data Protocol, (b) CNN’s DNS client implementation correctly complies with the DNS TTL time values returned by the Third Party Provider’s DNS servers, i.e., CNN’s DNS client does not cache data beyond the TTL time, and (c) CNN sends Queries to the host name provided to CNN by the Third Party Provider (e.g., CXX.xxxxxx.xxx) and CNN’S client implementation repeats the DNS lookups at least every five seconds in order to pick up any changes. This Section 5(c) shall apply to any “backward compatible” updates to the Data Protocol unless CNN has consented to such updates and the date for their implementation, which consent will not be unreasonably withheld, where “backward compatible” updates means updates that do not require changes by CNN in order to maintain the same level of functionality that existed previous to the proposed update. Data Protocol updates that are backward compatible shall be considered to be a part of the Data Protocol to the extent that they are delivered by the Third Party Provider or AOL to CNN with reasonable notice and are concurrently generally required of the Third Party Provider’s commercial search customers.
Sample 1
Implementation of Technical Specifications. The [*] in this Schedule E shall only apply if: (a) Customer correctly implements the technical specifications concerning correct use of XML protocol arguments and correct handling of optional or new result fields set forth in the Google Data Protocol, (b) Customer's DNS client implementation correctly handles standard DNS protocol, which includes strict observation of DNS TTL values returned by Google's DNS servers, and (c) Customer sends Queries to the host name provided to Customer by Google (e.g. XXX.xxxxxx.xxx) and Customer's client implementation repeats the DNS lookups as specified by Google's DNS servers.
Sample 1
Implementation of Technical Specifications. The [***] in this Schedule shall only apply provided that (a) Customer correctly implements the technical specifications concerning correct use of XML protocol arguments and correct handling of optional or new result fields set forth in the Google Data Protocol, (b) Customer's DNS client implementation correctly observes the DNS TTL values returned by Google's DNS servers, i.e., if Customer's DNS client does not cache values beyond the TTL time, and c) Customer sends Queries to the host name provided to customer by Google (e.g. XXX.xxxxxx.xxx) and Customer's client implementation repeats the DNS lookups at least every [***] in order to pick up any changes.
Sample 1

Related to Implementation of Technical Specifications

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • Project Implementation The Borrower shall:

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Technical Safeguards 1. USAC and DSS will process the data matched and any data created by the match under the immediate supervision and control of authorized personnel to protect the confidentiality of the data, so unauthorized persons cannot retrieve any data by computer, remote terminal, or other means. 2. USAC and DSS will strictly limit authorization to these electronic data areas necessary for the authorized user to perform their official duties. All data in transit will be encrypted using algorithms that meet the requirements of the Federal Information Processing Standard (FIPS) Publication 140-2 or 140-3 (when applicable). 3. Authorized system users will be identified by User ID and password, and individually tracked to safeguard against the unauthorized access and use of the system. System logs of all user actions will be saved, tracked and monitored periodically. 4. USAC will transmit data to DSS via encrypted secure file delivery system. For each request, a response will be sent back to USAC to indicate success or failure of transmission.

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