Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.
Contents of Personnel File A. Adverse statements prepared by the County shall not be included in an employee's official personnel file unless a copy is provided to the employee. B. An employee shall have the right to inspect and review the contents of his or her official personnel file at reasonable intervals. C. In addition, an employee shall have the right to inspect and review the contents of his or her official personnel file in any case where the employee has a grievance related to performance; to a performance evaluation; or is contesting his or her suspension or discharge from County service. D. Letters of reference and reports concerning criminal investigations concerning the employee shall be excluded from the provisions of B. and C., above. E. An employee shall have the right to respond in writing or personal interview to any information contained in his or her official personnel file, such reply to become a permanent part of such employee's official personnel file. F. Any contents of an employee's official personnel file may be destroyed pursuant to an agreement between the Chief of Employee Relations and the employee concerned or by an order of an arbitrator, court or impartial hearing officer unless the particular item is otherwise required by law to be kept.
The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.
White Pages Listings 5.1 BellSouth shall provide <<customer_name>> and their customers access to white pages directory listings under the following terms:
Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.