Single formality. This document is subject to a single formality.
Single formality Sample Clauses
Related to Single formality
Due Formation The Purchaser is duly formed, validly existing and in good standing in the jurisdiction of its organization. The Purchaser has all requisite power and authority to carry on its business as it is currently being conducted.
Corporate Formalities The Borrower will strictly observe limited liability company formalities in its dealings with the Servicer, the Parent, the Performance Guarantor, the Originators or any Affiliates thereof, and funds or other assets of the Borrower will not be commingled with those of the Servicer, the Parent, the Performance Guarantor, the Originators or any Affiliates thereof except as permitted by this Agreement in connection with servicing the Pool Receivables. The Borrower shall not maintain joint bank accounts or other depository accounts to which the Servicer, the Parent, the Performance Guarantor, the Originators or any Affiliate thereof (other than the Servicer solely in its capacity as such) has independent access. The Borrower is not named, and has not entered into any agreement to be named, directly or indirectly, as a direct or contingent beneficiary or loss payee on any insurance policy with respect to any loss relating to the property of the Servicer, the Parent, the Performance Guarantor, the Originators or any Subsidiaries or other Affiliates thereof. The Borrower will pay to the appropriate Affiliate the marginal increase or, in the absence of such increase, the market amount of its portion of the premium payable with respect to any insurance policy that covers the Borrower and such Affiliate.
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.
Validation To validate the notice requirements outlined in Section 5.3, the Assuming Institution shall provide the Receiver (i) an Affidavit of Publication to meet the publication requirements outlined in Section 5.3(a) and (ii) the Assuming Institution will prepare an Affidavit of Mailing in a form substantially similar to Exhibit 2.3B after mailing the seven (7) day Notice to Depositors as required under Section 5.3(b).
Formalities Parties to this Agreement
MAINTENANCE OF STANDARDS The Employer agrees, subject to the following provisions, that all conditions of employment in his/her individual operation relating to wages, hours of work, overtime differentials and general working conditions shall be maintained at not less than the highest standards in effect at the time of the signing of this Agreement, and the conditions of employment shall be improved whenever specific provisions for improvement are made elsewhere in this Agreement.
Hot Weather Guidelines For the purposes of site based discussions regarding the need to plan and perform work during expected periods of hot weather, the following issues shall be considered in conjunction with proper consideration of Occupational Health and Safety issues.
Scaling “Scaling,” as used herein, involves:
REQUIRED FOR PART 2 JOC - PRICING OF Regular Hours Coefficient What is your regular hours coefficient for the RS Means Price Book? (FAILURE TO RESPOND PROHIBITS PART 2 JOC EVALUATION)
Fabrication Making up data or results and recording or reporting them.
