Guidelines for Reimbursement of Registration, Test Fees, and Study Guide. 1. All employees may be reimbursed for educational expenses in accordance with Article 4, Section 1 of the GMEA labor agreement.
Guidelines for Reimbursement of Registration, Test Fees, and Study Guide Sample Clauses
Related to Guidelines for Reimbursement of Registration, Test Fees, and Study Guide
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
DECLARATION OF COMPLIANCE WITH APPLICABLE STANDARDS 1. Does the Work report experiments involving human subjects? [ ] YES [ ] NO If Yes, were the reported experiments in accordance with the ethical standards of the committee responsible for human experimentation (institutional and national), and with the Helsinki Declaration of 1975, as revised in 2013 (xxxx://xxxxxx.xxx.xxx/ecodes/node/3931 )? [ ] YES [ ] NO (If Yes, the Assignor must submit a copy of the approval and consent-to-disclose form to Xxxxxxx Science Publishers by fax or email.) Please state whether Ethical Approval was given, by whom and the relevant Judgement’s reference number. (If No, the Assignor must mention an institutional or regional guideline.) 2. Does the Work report experiments involving animals? [ ] YES [ ] NO If Yes, were the reported experiments in accordance with the standards set forth in one of below national guidelines and regulations: o The US National Research Council's "Guide for the Care and Use of Laboratory Animals," o The US Public Health Service's "Policy on Humane Care and Use of Laboratory Animals," and "Guide for the Care and Use of Laboratory Animals." o UK : the Animals (Scientific Procedures) Act 1986 Amendment Regulations (SI 2012/3039). [ ] YES [ ] NO 6 [v.122016] CONFLICTS OF INTEREST Conflicts of interest arise when authors, reviewers, or editors have interests (such as financial or personal interests) that are not made clear and that may influence their judgment on the content of their work. Authors and editors who submit work for publication with Xxxxxxx Science are required to disclose and acknowledge all forms of financial support relating to the work to be published, all commercial or financial involvement that might present an appearance of a conflict of interest in respect of the work, and all agreements relating to sponsorship of any research upon which the work is based. Are there any actual, or potential, conflicts of interest? [ ] YES [ ] NO If Yes, details of the actual or potential conflicts of interest must be set-out in the spaces provided below. DISCLOSURE REGARDING ACTUAL OR POTENTIAL CONFLICTS OF INTEREST: [INSERT] DISCLOSURE REGARDING THIRD PARTY FINANCIAL CONTRIBUTIONS: [INSERT] LANGUAGE AND EDITING: Does Assignor require assistance in having the English grammar and style of the Work checked and improved by Xxxxxxx Science? [ ] YES [ ] NO If Yes, Xxxxxxx Science will provide a quote in respect of the same.
Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:
Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.
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.
Transfer or Deletion of Student Data The Provider shall review, on an annual basis, whether the Student Data it has received pursuant to the DPA continues to be needed for the purpose(s) of the Service Agreement and this DPA. If any of the Student Data is no longer needed for purposes of the Service Agreement and this DPA, the Provider will provide written notice to the LEA as to what Student Data is no longer needed. The Provider will delete or transfer Student Data in readable form to the LEA, as directed by the LEA (which may be effectuated through Exhibit D of the DPA), within 30 calendar days if the LEA requests deletion or transfer of the Student Data and shall provide written confirmation to the LEA of such deletion or transfer. Upon termination of the Service Agreement between the Provider and LEA, Provider shall conduct a final review of Student Data within 60 calendar days. If the LEA receives a request from a parent, as that term is defined in 105 ILCS 10/2(g), that Student Data being held by the Provider be deleted, the LEA shall determine whether the requested deletion would violate State and/or federal records laws. In the event such deletion would not violate State or federal records laws, the LEA shall forward the request for deletion to the Provider. The Provider shall comply with the request and delete the Student Data within a reasonable time period after receiving the request. Any provision of Student Data to the LEA from the Provider shall be transmitted in a format readable by the LEA.
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
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).
LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.
