Use the Appropriate ® or ™ Symbol Sample Clauses

Use the Appropriate ® or ™ Symbol. Customer must reproduce any CyberSource Trademarks exactly as shown in Appendix A, including the exact reproduction of any proprietary markings or legends and including the appropriate ® or ™ symbol at the first and most prominent reference, or as soon as practicable thereafter.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Use the Appropriate ® or ™ Symbol. Company must reproduce any Xxxxxxxxx.Xxx Marks exactly as shown on Appendix A, including the exact reproduction of any proprietary markings or legends and including the appropriate ® or ™ symbol at the first and most prominent reference, or as soon as practicable thereafter.
Sample 1Sample 2Sample 3See All (4)
Use the Appropriate ® or ™ Symbol. Customer must reproduce any Xxxxxxxxx.Xxx Trademarks exactly as shown in Appendix A, including the exact reproduction of any proprietary markings or legends and including the appropriate ® or ™ symbol at the first and most prominent reference, or as soon as practicable thereafter.
Sample 1Sample 2Sample 3See All (4)
Use the Appropriate ® or ™ Symbol. Reseller must reproduce any Xxxxxxxxx.Xxx Marks exactly as shown on Appendix B, including the exact reproduction of any proprietary markings or legends and including the appropriate ® or ™ symbol at the first and most prominent reference, or as soon as practicable thereafter.
Sample 1Sample 2See All (4)
Use the Appropriate ® or ™ Symbol. Customer must reproduce any GSPAYTECH Trademarks exactly as shown in Appendix A, including the exact reproduction of any proprietary markings or legends and including the appropriate ® or ™ symbol at the first and most prominent reference, or as soon as practicable thereafter.
Sample 1Sample 2
Use the Appropriate ® or ™ Symbol. Customer must reproduce any Cloud9 Trademarks exactly as shown in Appendix A, including the exact reproduction of any proprietary markings or legends and including the appropriate ® or ™ symbol at the first and most prominent reference, or as soon as practicable thereafter.
Sample 1

Related to Use the Appropriate ® or ™ Symbol

  • Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location.

  • Unbundled Sub Loop shall be equal to or better than each of the applicable requirements set forth in the applicable industry standard technical references.

  • Unbundled Copper Loops (UCL) 2.4.1 BellSouth shall make available Unbundled Copper Loops (UCLs). The UCL is a copper twisted pair Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters) and is not intended to support any particular telecommunications service. The UCL will be offered in two types – Designed and Non-Designed.

  • Unbundled Copper Sub-Loop (UCSL) is a copper facility of any length provided from the cross-box in the field up to and including the End User’s point of demarcation. If available, this facility will not have any intervening equipment such as load coils between the End User and the cross-box.

  • Unbundled Copper Loop Designed (UCL-D)

  • Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and its cross-box (or other access point) that serves an end user location.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters).

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

  • INFORMATION OF LOCKHEED XXXXXX (a) Information provided by LOCKHEED XXXXXX to SELLER remains the property of LOCKHEED XXXXXX. XXXXXX agrees to comply with the terms of any proprietary information agreement with LOCKHEED XXXXXX and to comply with all proprietary information markings and restrictive legends applied by LOCKHEED XXXXXX to anything provided hereunder to SELLER. XXXXXX agrees not to use any LOCKHEED XXXXXX provided information for any purpose except to perform this Contract and agrees not to disclose such information to third parties without the prior written consent of LOCKHEED XXXXXX. SELLER shall maintain data protection processes and systems sufficient to adequately protect LOCKHEED XXXXXX provided information and comply with any law or regulation applicable to such information.

  • Actions under the Program The actions taken by the Recipient under the Program include the following:

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