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”.
Answer Within twenty (20) days after receipt of the Complaint, each respondent shall serve on the BCBSA and on the complaining party (or parties) and on the Chairman of the Mediation Committee; i. a full Answer to the aforesaid Complaint;
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.
FURNITURE CLASSIFICATIONS Furniture classifications include but not limited to: Cafeteria, Dormitory, Library Shelving and Library Related, Lounge, Systems (Modular), School (Classroom), Freestanding, Seating, Filing Systems and Equipment, and Technology Support.
Personal Protective Clothing 11.1 On commencement of employment with the Employer each employee will be issued with the following; 11.2 Where the employee requires prescription glasses, the Employer shall ensure that appropriate eye protection is issued or where the employee has had his/her glasses hardened, reimburse the employee for the cost, provided that such glasses meet appropriate safety standards. 11.3 The above mentioned equipment will be maintained by the employee and replaced by the Employer on a fair wear and tear basis. 11.4 Intentionally left blank
Resubmission If terminated, resolved or withdrawn, a grievance cannot be resubmitted.
DHS Seal, Logo, and Flags The Contractor shall not use the Department of Homeland Security (DHS) seal(s), logos, crests, or reproductions of flags or likeness of DHS agency officials without specific FEMA pre-approval.
Motion Within fifteen (15) days after the Agreement Date, Plaintiffs shall submit to the Court a motion requesting entry of an order substantially in the form attached hereto as Exhibit G (the “Scheduling Order”) (a) preliminarily approving the Settlement; (b) approving the content and plan for publication and dissemination of Notice; (c) setting the date by which any objection to the Settlement or this Agreement must be filed; and (d) scheduling a Hearing to consider final approval of the Settlement and entry of the orders required by Paragraph 9 of this Agreement. With respect to the content and plan for publication and dissemination of Notice, Plaintiffs will propose that Notice in substantially the form attached hereto as Exhibit E, be sent via electronic mail, first class mail or international delivery service to all Interested Parties; sent via electronic service to all counsel of record for any Person who has been or is, at the time of Notice, a party in any case included in MDL No. 2099, In re: Stanford Entities Securities Litigation (N.D. Tex.) (the “MDL”), the SEC Action, the Investor Litigation, or the Committee Litigation who are deemed to have consented to electronic service through the Court’s CM/ECF System under Local Rule CV-5.1(d); sent via facsimile transmission and/or first class mail to any other counsel of record for any other Person who has been or is, at the time of service, a party in any case included in the MDL, the SEC Action, the Investor Litigation, or the Committee Litigation; and posted on the websites of the Receiver and the Examiner along with complete copies of this Agreement and all filings with the Court relating to the Settlement, this Agreement, and approval of the Settlement. Plaintiffs will further propose that Notice in substantially the form attached hereto as Exhibit H be published once in the national edition of The Wall Street Journal and once in the international edition of The New York Times. In advance of filing the motion papers to accomplish the foregoing, Plaintiffs shall provide the BDO Entities with a reasonable opportunity to review and comment on such motion papers.
Labour Management Committee (a) Where the parties mutually agree that there are matters of mutual concern and interest that would be beneficial if discussed at a Labour Management Committee Meeting during the term of this Agreement, the following shall apply. (b) An equal number of representatives of each party as mutually agreed shall meet at a time and place mutually satisfactory. A request for a meeting hereunder will be made in writing prior to the date proposed and accompanied by an agenda of matters proposed to be discussed, which shall not include matters that are properly the subject of grievance or negotiations for the amendment or renewal of this agreement. Any representative(s) attending such meetings during their regularly scheduled hours of work shall not lose regular earnings as a result of such attendance. (c) It is agreed that the topic of a rehabilitation program for drug and alcohol abuse is an appropriate topic for the Labour-Management Committee. It is also agreed that the topic of the utilization of full-time and part-time staff is an appropriate topic for the Labour-Management Committee. The committee shall have access to work schedules and job postings upon request. (d) It is understood that joint meetings with other Labour-Management Committees in the Hospital may be scheduled concerning issues of mutual interest if satisfactory to all concerned. (e) Where two or more agreements exist between a Hospital and CUPE the Committee may be a joint one representing employees under both agreements, unless otherwise agreed.