Communications Xxxxxx Licence / Registration Allowance Sample Clauses

Communications Xxxxxx Licence / Registration Allowance. An employee who is required by the Employer to hold and utilise a current communications cabling registration (or the equivalent ACA Licence type) in the course of their employment will be paid an all purpose allowance as specified in Appendix A. Provided that this Clause will not act to disadvantage any employee who is already receiving a higher rate.
AutoNDA by SimpleDocs
Communications Xxxxxx Licence / Registration Allowance. An employee who is required by the Employer to hold and utilise a current communications cabling registration in the course of their employment will be paid an all purpose allowance as specified in Appendix E, but only in respect of the week for which the employee is engaged in duties for which registration is required. Provided that this clause will not act to disadvantage any employee who is already receiving a higher rate.

Related to Communications Xxxxxx Licence / Registration Allowance

  • 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.

  • 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.

  • 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.

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