Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).
Changes in Insurance Requirements Not more frequently than once annually, if in the opinion of District the amount of the foregoing insurance coverages is not adequate or the type of insurance or its coverage adequacy is deemed insufficient, Contractor shall amend the insurance coverage as required by District's Risk Manager or designee.
Compliance Requirements K. If using volunteers as provided for in this Contract during FY19, which encompasses the Contract term of July 1, 2019 to June 30, 2020, then the Grantee must either:
Use Guidelines 3.3.1. The JAGGAER Applications are provided to Client for use only as expressly set forth in the Agreement, and Client will not use the JAGGAER Applications in whole or in part for any other use or purpose. In particular, Client will not, and will not allow any third party to: (i) decompile, disassemble, reverse engineer or attempt to reconstruct, identify or discover any source code, underlying ideas, underlying user interface techniques or algorithms of the JAGGAER Applications by any means, or disclose any of the foregoing; (ii) except as expressly set forth in the Agreement, provide, rent, lease, lend, or use the JAGGAER Applications for timesharing, subscription, or service bureau purposes; (iii) sublicense, transfer or assign the JAGGAER Applications or any of the rights or licenses granted under the Agreement; or remove or obscure any trademark, product identification, proprietary marking, copyright or other notices provided with the JAGGAER Applications or related documentation.
Policies, Guidelines, Directives and Standards Either the LHIN or the MOHLTC will give the HSP Notice of any amendments to the manuals, guidelines or policies identified in Schedule C. An amendment will be effective in accordance with the terms of the amendment. By signing a copy of this Agreement the HSP acknowledges that it has a copy of the documents identified in Schedule C.
CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
Modifications to the Anti-Corruption Guidelines The modifications to the Anti-Corruption Guidelines are as follows:
Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
