Database File The Servicer will provide the Successor Servicer with a data file (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Cutoff Date, (ii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Servicing Transfer, and (iii) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Servicing Transfer.
Labels The Contractor shall provide fuel content labels/signs for each pumping station. These labels shall identify significant amounts of alcohols in the fuel and satisfy the requirements of 1NYCRR, Part 224 and 6NYCRR, Part
Proxy Materials The Custodian shall deliver, or cause to be delivered promptly, to the Fund proxy forms, notices of meeting, and any other notices or announcements materially affecting or relating to Investments received by the Custodian or any nominee.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, 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. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Filing of Materials All records related to a grievance shall be filed separately from the personnel files of the employees.
