Implementation of Technical Specifications Clause Samples
The 'Implementation of Technical Specifications' clause defines the obligation of a party, typically a contractor or supplier, to carry out work or deliver products in strict accordance with detailed technical requirements set forth in the contract. This clause ensures that all materials, processes, and outcomes meet predefined standards, such as engineering drawings, performance criteria, or industry norms. By mandating adherence to these specifications, the clause helps prevent disputes over quality or suitability, ensuring that the delivered work aligns with the client's expectations and contractual requirements.
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. ▇▇▇.▇▇▇▇▇▇.▇▇▇) and Customer’s client implementation repeats the DNS lookups at least every 5 seconds in order to pick up any changes.
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.
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. ▇▇▇.▇▇▇▇▇▇.▇▇▇) and Customer's client implementation repeats the DNS lookups as specified by Google's DNS servers.
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. ▇▇▇.▇▇▇▇▇▇.▇▇▇) and Customer's client implementation repeats the DNS lookups at least every [***] in order to pick up any changes.
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., C▇▇.▇▇▇▇▇▇.▇▇▇) 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.