Ownership and use of Reference Images and Query Images Sample Clauses

Ownership and use of Reference Images and Query Images. As between ViSenze and the Customer, ViSenze does not claim ownership over any Reference Images or any Query Images. However, the Customer grants permission for ViSenze to use the Reference Images and, where relevant, the Query Images:
AutoNDA by SimpleDocs

Related to Ownership and use of Reference Images and Query Images

  • OWNERSHIP AND USE OF DELIVERABLES The City shall own all rights, titles, and interests throughout the world in and to the deliverables.

  • Access to and Use of Content Customer has the right to access and use applicable Content subject to the terms of applicable Order Forms, this Agreement and the Documentation.

  • OWNERSHIP AND USE OF WORK PRODUCT All reports, studies, information, data, statistics, forms, designs, plans, procedures, systems and any other materials or properties produced in whole or in part under this Agreement in connection with the performance of the Required Services (collectively “Work Product”) shall be the sole and exclusive property of City. No such Work Product shall be subject to private use, copyrights or patent rights by Consultant in the United States or in any other country without the express, prior written consent of City. City shall have unrestricted authority to publish, disclose, distribute, and otherwise use, copyright or patent, in whole or in part, any such Work Product, without requiring any permission of Consultant, except as may be limited by the provisions of the Public Records Act or expressly prohibited by other applicable laws. With respect to computer files containing data generated as Work Product, Consultant shall make available to City, upon reasonable written request by City, the necessary functional computer software and hardware for purposes of accessing, compiling, transferring and printing computer files.

  • Exclusions and Limitations for Third Party Software SUBJECT TO THE EXCLUSION OF DAMAGES STATED IN SECTION 9.2 AND WITH RESPECT TO THIRD PARTY SOFTWARE, UNDER NO CIRCUMSTANCES AND REGARDLESS OF THE NATURE OF ANY CLAIM SHALL SAP OR ITS LICENSORS’ BE LIABLE FOR AN AMOUNT IN EXCESS OF THE PAID LICENSE FEES FOR THE THIRD PARTY SOFTWARE DIRECTLY CAUSING THE DAMAGES.

  • Ownership and License in Deliverables Unless otherwise specified in a specific Purchase Order concerning procurement of a SaaS product:

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

  • Ownership and Publication of Materials All reports, information, data, and other materials prepared by the Consultant pursuant to this agreement are the property of the City. The City has the exclusive and unrestricted authority to release, publish or otherwise use, in whole or part, information relating thereto. Any re-use without written verification or adaptation by the Consultant for the specific purpose intended will be at the City’s sole risk and without liability or legal exposure to the Consultant. No material produced in whole or in part under this agreement may be copyrighted or patented in the United States or in any other country without the prior written approval of the City.

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

  • Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

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