RECOGNITION OF RECOGNIZED DOMAIN NAMES Sample Clauses

RECOGNITION OF RECOGNIZED DOMAIN NAMES. Throughout the Term, Xxx.xxx shall cause the Xxx.xxx DNS Network to recognize Queries containing Recognized Domain Names made by Internet users who can access Xxx.xxx Domain Names generally (via a Xxx.xxx supporting ISP or the Client Application). Xxx.xxx shall provide a service level in the Xxx.xxx DNS Network's resolution of Queries containing Recognized Domain Names that is no worse than the service level generally achieved in the Xxx.xxx DNS Network's resolution of Queries for other Xxx.xxx Names.
AutoNDA by SimpleDocs

Related to RECOGNITION OF RECOGNIZED DOMAIN NAMES

  • Protection of Reputation During Executive’s employment with the Company and thereafter, Executive agrees that he will take no action which is intended, or would reasonably be expected, to harm the reputation of the Company or any of its affiliates or which would reasonably be expected to lead to unwanted or unfavorable publicity to the Company or its affiliates. Nothing herein shall prevent Executive from making any truthful statement in connection with any investigation by the Company or any governmental authority or in any legal proceeding.

  • Inventions Assigned to the United States I agree to assign to the United States government all my right, title, and interest in and to any and all Inventions whenever such full title is required to be in the United States by a contract between the Company and the United States or any of its agencies.

  • Federal Government End Use Provisions We provide the Services, including related software and technology, for ultimate federal government end use solely in accordance with the following: Government technical data and software rights related to the Services include only those rights customarily provided to the public as defined in this Agreement. This customary commercial license is provided in accordance with FAR 12.211 (Technical Data) and FAR 12.212 (Software) and, for Department of Defense transactions, DFAR 252.227-7015 (Technical Data – Commercial Items) and DFAR 227.7202-3 (Rights in Commercial Computer Software or Computer Software Documentation). If a government agency has a need for rights not granted under these terms, it must negotiate with Us to determine if there are acceptable terms for granting those rights, and a mutually acceptable written addendum specifically granting those rights must be included in any applicable agreement.

  • Abuse and Neglect of Children and Vulnerable Adults: Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer.

  • License of Data; Warranty; Termination of Rights A. The valuation information and evaluations being provided to the Trust by USBFS pursuant hereto (collectively, the “Data”) are being licensed, not sold, to the Trust. The Trust has a limited license to use the Data only for purposes necessary to valuing the Trust’s assets and reporting to regulatory bodies (the “License”). The Trust does not have any license nor right to use the Data for purposes beyond the intentions of this Agreement including, but not limited to, resale to other users or use to create any type of historical database. The License is non-transferable and not sub-licensable. The Trust’s right to use the Data cannot be passed to or shared with any other entity. The Trust acknowledges the proprietary rights that USBFS and its suppliers have in the Data. B. THE TRUST HEREBY ACCEPTS THE DATA AS IS, WHERE IS, WITH NO WARRANTIES, EXPRESS OR IMPLIED, AS TO MERCHANTABILITY OR FITNESS FOR ANY PURPOSE OR ANY OTHER MATTER. C. USBFS may stop supplying some or all Data to the Trust if USBFS’s suppliers terminate any agreement to provide Data to USBFS. Also, USBFS may stop supplying some or all Data to the Trust if USBFS reasonably believes that the Trust is using the Data in violation of the License, or breaching its duties of confidentiality provided for hereunder, or if any of USBFS’s suppliers demand that the Data be withheld from the Trust. USBFS will provide notice to the Trust of any termination of provision of Data as soon as reasonably possible.

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

  • Monopolies and Exclusive Service Suppliers 1. Each Party shall ensure that any monopoly supplier of a service in its territory does not, in the supply of the monopoly service in the relevant market, act in a manner inconsistent with that Party's Schedule of specific commitments. 2. Where a Party's monopoly supplier competes, either directly or through an affiliated company, in the supply of a service outside the scope of its monopoly rights and which is subject to that Party's Schedule of specific commitments, the Party shall ensure that such a supplier does not abuse its monopoly position to act in its territory in a manner inconsistent with such commitments. 3. If a Party has reason to believe that a monopoly supplier of a service of the other Party is acting in a manner inconsistent with paragraphs 1 or 2 above, it may request that Party establishing, maintaining or authorising such supplier to provide specific information concerning the relevant operations. 4. The provisions of this Article shall also apply to cases of exclusive service suppliers, where a Party, formally or in effect: (a) authorises or establishes a small number of service suppliers; and (b) substantially prevents competition among those suppliers in its territory.

  • LIABILITY FOR UNAUTHORIZED USE-LOST/STOLEN CARD NOTIFICATION You agree to notify Credit Union immediately, orally or in writing at Florida Credit Union, X.X. Xxx 0000, Xxxxxxxxxxx, XX 00000 or telephone (000) 000-0000 twenty four

  • Transition of Registry upon Termination of Agreement Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, Registry Operator shall provide ICANN or any successor registry operator that may be designated by ICANN for the TLD in accordance with this Section 4.5 with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process; provided, however, that (i) ICANN will take into consideration any intellectual property rights of Registry Operator (as communicated to ICANN by Registry Operator) in determining whether to transition operation of the TLD to a successor registry operator and (ii) if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (A) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator or its Affiliates for their exclusive use, (B) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (C) transitioning operation of the TLD is not necessary to protect the public interest, then ICANN may not transition operation of the TLD to a successor registry operator upon the expiration or termination of this Agreement without the consent of Registry Operator (which shall not be unreasonably withheld, conditioned or delayed). For the avoidance of doubt, the foregoing sentence shall not prohibit ICANN from delegating the TLD pursuant to a future application process for the delegation of top-­‐level domains, subject to any processes and objection procedures instituted by ICANN in connection with such application process intended to protect the rights of third parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument for the maintenance and operation of the TLD, regardless of the reason for termination or expiration of this Agreement.

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