Public Use The Recipient will ensure that Infrastructure resulting from any Eligible Project that is not sold, leased, encumbered, or otherwise disposed of, remains primarily for public use or benefit.
Developer’s Attachment Facilities (“DAF”). Developer shall, at its expense, design, procure, construct, own and install the DAF, as set forth in Appendix A hereto.
Service Areas HHSC authorizes the MA Dual SNP to add the MA Product to Texas service areas that are not identified in Attachment C, Proposed MA Product Service Areas, provided it receives prior CMS approval and complies with the notice requirements specified in this Agreement.
Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.
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.
Service Area (a) SORACOM shall provide the SORACOM Air Global Service within the area designated on the web site of SORACOM (the “Service Area”), provided, that, the Service Area may be different if stated otherwise as specified by SORACOM separately. However, within the Service Area, you may not use the SORACOM Air Global Service in places where transmissions are difficult to send or receive. (b) The parties of this Agreement acknowledge that there may be countries or locations within which SORACOM may be restricted from providing the SORACOM Air Global Service due to applicable laws, regulations, decisions, rules or orders (“Restrictions”). During the Term, SORACOM will use reasonable efforts to monitor whether there are any such Restrictions. SORACOM may in its sole discretion and at any time, suspend, discontinue, limit, or modify the SORACOM Air Global Service or impose additional requirements on the provision of the SORACOM Air Global Service, as may be reasonably required to comply with any such Restrictions. (c) In no event will SORACOM be required to provide the SORACOM Air Global Service in countries or locations, or in a manner that would be in violation of the Restrictions and its failure to provide the SORACOM Air Global Service due to the Restrictions will not be deemed to be a breach of its obligations under this Agreement. (d) In the event that any Restriction, or any change in applicable law, regulation, decision, rule or order materially or adversely affects the delivery of the SORACOM Air Global Service (including the economic viability thereof), SORACOM will notify Subscribers in writing and the parties will negotiate in good faith regarding changes to this Agreement. If the parties cannot reach agreement within 30 days after notification from SORACOM requesting renegotiation, SORACOM may terminate the Agreement upon 30 days’ written notice to the Subscriber.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
COMMERCIAL REUSE OF SERVICES The member or user herein agrees not to replicate, duplicate, copy, trade, sell, resell nor exploit for any commercial reason any part, use of, or access to 's sites.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.