Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.
Financial Viability and Regulatory Compliance 2.6.1 Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. Contractor further warrants and represents that it owes no outstanding delinquent federal, state or local taxes or business assessments. 2.6.2 Contractor agrees to promptly disclose to the MPHA any IRS liens or licensure suspension or revocation that may adversely affect its capacity to perform the services outlined within this contract. The failure by Contractor to disclose such issue to the MPHA in writing within 5 days of such notification received will constitute a material breach of this contract. 2.6.3 Contractor further agrees to promptly disclose to the MPHA any change of more than 50% of its ownership and/or any declaration of bankruptcy that Contractor may undergo during the term(s) of this contract. The failure of Contractor to disclose any change of more than 50% of its ownership and/or its declaration of bankruptcy within 5 days of said actions shall constitute a material breach of this contract. 2.6.4 All disclosures made pursuant to this section of the contract shall be made in writing and submitted to MPHA within the time periods required herein.
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.
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.
Year 2000 Compatibility Take all action necessary to assure that its computer based systems are able to operate and effectively process data including dates on and after January 1, 2000, and, at the reasonable request of the Administrative Agent or the Required Lenders, provide evidence to the Lenders of such year 2000 compatibility.
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.
Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.
Use of Software Any software that is available on the Services ("Software") is the copyrighted work of Red Hat and/or its licensors. Copying or reproducing the Software to any other server or location for further reproduction or redistribution is strictly prohibited, unless such reproduction or redistribution is permitted by a license agreement accompanying such Software. You may not create derivative works of the Software, or attempt to decompile or reverse-engineer the Software unless otherwise permitted by law. Use of the Software is subject to the license terms of any license agreement that may accompany or is provided with the Software. You may not download any Software until you have read and accepted the terms of the accompanying software license. WITHOUT LIMITING THE FOREGOING, THE SOFTWARE IS WARRANTED, IF AT ALL, ONLY ACCORDING TO THE TERMS OF THE SEPARATE LICENSE AGREEMENT ACCOMPANYING THE SOFTWARE. EXCEPT AS WARRANTED IN SUCH LICENSE AGREEMENT, RED HAT, ITS PARENT, SUBSIDIARY, AND AFFILIATE COMPANIES, AND ITS LICENSORS DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THE SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, TO THE MAXIMUM EXTENT PERMITTED BY LAW.
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.
