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.
Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation
SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.
End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).
NO HARDSTOP/PASSIVE LICENSE MONITORING Unless an Authorized User is otherwise specifically advised to the contrary in writing at the time of order and prior to purchase, Contractor hereby warrants and represents that the Product and all Upgrades do not and will not contain any computer code that would disable the Product or Upgrades or impair in any way its operation based on the elapsing of a period of time, exceeding an authorized number of copies, advancement to a particular date or other numeral, or other similar self-destruct mechanisms (sometimes referred to as “time bombs,” “time locks,” or “drop dead” devices) or that would permit Contractor to access the Product to cause such disablement or impairment (sometimes referred to as a “trap door” device). Contractor agrees that in the event of a breach or alleged breach of this provision that Authorized User shall not have an adequate remedy at law, including monetary damages, and that Authorized User shall consequently be entitled to seek a temporary restraining order, injunction, or other form of equitable relief against the continuance of such breach, in addition to any and all remedies to which Authorized User shall be entitled.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
Permitted License Uses and Restrictions (a) This Order Form Supplement allows you, as an authorized User under the Master Subscription Agreement, to use the Software on any Supported Device and on no other devices.
(b) You may not distribute or make the Software available over a network where it could be used by multiple devices at the same time.
(c) With respect to updates to the Software that xxxxxxxxxx.xxx may make available for download, this Order Form Supplement allows you to download such Software updates to update or restore the Software on any Supported Device.
(d) Except as and only to the extent permitted by applicable law, or by licensing terms governing use of open-sourced components included with the Software, neither you nor any other Customer personnel may copy, decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of the Software or Software updates, or any part thereof. Any attempt to do so is a violation of the rights of xxxxxxxxxx.xxx and its licensors. If you or any other Customer personnel violate this restriction, you or they, and the Customer, may be subject to prosecution and damages.
(e) Neither you nor the Customer may rent, lease, lend, redistribute or sublicense the Software. The Customer may, however, allow other authorized Users under the Master Subscription Agreement to use the Software in connection with a re-assignment of the Supported Device to another authorized User under the Master Subscription Agreement.
(f) The Software is available only for Supported Devices, and is not available for all devices. Please check xxx.xxxxxxxxxx.xxx or contact your xxxxxxxxxx.xxx representative to determine whether a specific device-iOS software combination is supported by the Software.
(g) In addition to mobile applications offered by xxxxxxxxxx.xxx (and for purposes of this section 5(g), “xxxxxxxxxx.xxx” shall include any Affiliates of xxxxxxxxxx.xxx), xxxxxxxxxx.xxx may offer platforms for the creation of third-party mobile applications, including but not limited to the Salesforce1 platform. Third parties may obtain information from, or access data stored on, Users’ mobile devices to provide services associated with any third-party mobile applications that Users download, install, use, or otherwise interact with over a xxxxxxxxxx.xxx platform. Xxxxxxxxxx.xxx’s mobile applications may also contain links or integrations to other mobile applications provided by third parties. Xxxxxxxxxx.xxx is not responsible for the security and privacy of data collected through third-party mobile applications or the privacy and security practices of the foregoing third parties.
(h) Without limiting the generality of anything herein, you acknowledge and agree that the Software may collect user or device data for the purposes of providing services or functions that are relevant to use of the Software.
Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (“DAMLs”), and may have up to 6,000 feet of bridged tap between the end user’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For loops less than 18,000 feet and with less than 1300 Ohms resistance, the loop will provide a voice grade transmission channel suitable for loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point.
2.4.3.2 The UCL-ND facilities may be mechanically assigned using BellSouth’s assignment systems. Therefore, the Loop Make Up process is not required to order and provision the UCL-ND. However, Talk America can request Loop Make Up for which additional charges would apply.
2.4.3.3 At an additional charge, BellSouth also will make available Loop Testing so that Talk America may request further testing on the UCL-ND.
2.4.3.4 UCL-ND loops are not intended to support any particular service and may be utilized by Talk America to provide a wide-range of telecommunications services so long as those services do not adversely affect BellSouth’s network. The UCL- ND will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the loop to the customer’s inside wire.
2.4.3.5 Order Coordination (OC) will be provided as a chargeable option and may be utilized when the UCL-ND provisioning is associated with the reuse of BellSouth facilities. Order Coordination -Time Specific (OC-TS) does not apply to this product.
2.4.3.6 Talk America may use BellSouth’s Unbundled Loop Modification (ULM) offering to remove bridge tap and/or load coils from any loop within the BellSouth network. Therefore, some loops that would not qualify as UCL-ND could be transformed into loops that do qualify, using the ULM process.
Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.
2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.
Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.
