Service counted for Long Service Leave Sample Clauses

Service counted for Long Service Leave. (a) For the purpose of these conditions “service” means service as an employee of a Western Australian Public Sector employer and will be deemed to include:
AutoNDA by SimpleDocs
Service counted for Long Service Leave. (a) For the purpose of these conditions “service” means service as an employee of a Public Authority and will be deemed to include:-
Service counted for Long Service Leave. (a) For the purpose of this clause
Service counted for Long Service Leave. 43.4.1 For the purpose of these conditions

Related to Service counted for Long Service Leave

  • Long Service Leave All employees shall be entitled to long service leave in accordance with the relevant State Legislation. The employer will ensure that any registration necessary for the purposes of portable long service schemes will be undertaken.

  • COMMERCIAL REUSE OF SERVICES The member or user herein agrees not to replicate, duplicate, copy, trade, sell, resell nor exploit for any commercial reason any part, use of, or access to 's sites.

  • Maintenance of Services 5.1 Services resold pursuant to this Attachment and BellSouth’s General Subscriber Service Tariff and Private Line Service Tariff and facilities and equipment provided by BellSouth shall be maintained by BellSouth.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Military Service Leave The Employer and the Union agree that the matter of leave of absence for an employee during the period of his/her military service with the armed forces of the United States, and of his/her reinstatement thereafter, shall be governed by applicable statutes.

  • DEPENDENT PERSONAL SERVICES 1. Subject to the provisions of Articles 16, 18, 19, 20 and 21, salaries, wages and other similar remuneration derived by a resident of a Contracting State in respect of an employment shall be taxable only in that State unless the employment is exercised in the other Contracting State. If the employment is so exercised, such remuneration as is derived therefrom may be taxed in that other State.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

Time is Money Join Law Insider Premium to draft better contracts faster.