CERTIFICATION REGARDING BOYCOTTING CERTAIN ENERGY COMPANIES (Texas law as of September 1, 2021) By submitting a proposal to this Solicitation, you certify that you agree, when it is applicable, to the following required by Texas law as of September 1, 2021: If (a) company is not a sole proprietorship; (b) company has ten (10) or more full-time employees; and (c) this contract has a value of $100,000 or more that is to be paid wholly or partly from public funds, the following certification shall apply; otherwise, this certification is not required. Pursuant to Tex. Gov’t Code Ch. 2274 of SB 13 (87th session), the company hereby certifies and verifies that the company, or any wholly owned subsidiary, majority-owned subsidiary, parent company, or affiliate of these entities or business associations, if any, does not boycott energy companies and will not boycott energy companies during the term of the contract. For purposes of this contract, the term “company” shall mean an organization, association, corporation, partnership, joint venture, limited partnership, limited liability partnership, or limited liability company, that exists to make a profit. The term “boycott energy company” shall mean “without an ordinary business purpose, refusing to deal with, terminating business activities with, or otherwise taking any action intended to penalize, inflict economic harm on, or limit commercial relations with a company because the company (a) engages in the exploration, production, utilization, transportation, sale, or manufacturing of fossil fuel-based energy and does not commit or pledge to meet environmental standards beyond applicable federal and state law, or (b) does business with a company described by paragraph (a).” See Tex. Gov’t Code § 809.001(1).
Provisional Application Upon signature of this Compact, and until this Compact has entered into force in accordance with Section 7.3, the Parties will provisionally apply the terms of this Compact; provided that, no MCC Funding, other than Compact Implementation Funding, will be made available or disbursed before this Compact enters into force.
File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.
NATIONAL JOINT COUNCIL AGREEMENTS 22.1 Subject to the National Joint Council By-Laws, agreements concluded by the National Joint Council of the Public Service on items which may be included in a collective agreement, and which the parties to this agreement have endorsed after December 6, 1978, will form part of this collective agreement, subject to the Federal Public Sector Labour Relations Act (FPSLRA) and any legislation by Parliament that has been or may be, as the case may be, established pursuant to any Act prescribed in Section 113(b) of the PSLRA.
22.2 NJC items which may be included in a collective agreement are those items which the parties to the NJC agreements have designated as such or upon which the Chairman of the Federal Public Sector Labour Relations Board has made a ruling pursuant to (c) of the NJC Memorandum of Understanding which became effective December 6, 1978
22.3 The following directives, as amended from time to time by National Joint Council recommendation and which have been approved by the National Research Council Canada, form part of this Agreement: - Bilingualism Bonus Directive - Commuting Assistance Directive - Occupational Health and Safety Directive - Relocation Directive - Travel Directive - First Aid to the General Public – Allowances for Employees - Public Service Health Care Plan - Uniforms Directive
22.4 During the term of this Agreement, other directives may be added to the above noted list.
22.5 Grievances in regard to the above directives shall be presented in accordance with clause 19.1 of the Grievance Procedure article of this Agreement.
General Application The rules set forth below in this Article VI shall apply for the purposes of determining each Member’s allocable share of the items of income, gain, loss and expense of the Company comprising Net Income or Net Loss for each Fiscal Year, determining special allocations of other items of income, gain, loss and expense, and adjusting the balance of each Member’s Capital Account to reflect the aforementioned general and special allocations. For each Fiscal Year, the special allocations in Section 6.03 hereof shall be made immediately prior to the general allocations of Section 6.02 hereof.
STATE MEAL MANDATE When CONTRACTOR is a nonpublic school, CONTRACTOR and LEA shall satisfy the State Meal Mandate under California Education Code sections 49530, 49530.5 and 49550.
Union Conventions Leave of Absence without pay and without loss of seniority shall be granted upon request to the Employer, to employees elected or appointed to represent the Union at Union Conventions or seminars. The total of such time off for all causes and for all employees in this unit combined shall not exceed fifteen (15) working days in any calendar year.
Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements
Mobile Application If Red Hat offers products and services through applications available on your wireless or other mobile Device (such as a mobile phone) (the "Mobile Application Services"), these Mobile Application Services are governed by the applicable additional terms governing such Mobile Application Service. Red Hat does not charge for these Mobile Application Services unless otherwise provided in the applicable additional terms. However, your wireless carrier's standard messaging rates and other messaging, data and other rates and charges will apply to certain Mobile Application Services. You should check with your carrier to find out what plans your carrier offers and how much the plans cost. In addition, the use or availability of certain Mobile Application Services may be prohibited or restricted by your wireless carrier, and not all Mobile Application Services may work with all wireless carriers or Devices. Therefore, you should check with your wireless carrier to find out if the Mobile Application Services are available for your wireless Device, and what restrictions, if any, may be applicable to your use of such Mobile Application Services.
FIPPA The HSP acknowledges that the LHIN is bound by FIPPA and that any information provided to the LHIN in connection with this Agreement may be subject to disclosure in accordance with FIPPA.
