Description of Agreements Sample Clauses

Description of Agreements. The Company is not a party to or bound by any contract or other instrument of a character required to be described in the Registration Statement or the Prospectus or to be filed as an exhibit to the Registration Statement that is not described and filed as required.
AutoNDA by SimpleDocs
Description of Agreements. There is no franchise, lease, contract, agreement or document required by the Securities Act or by the Rules and Regulations to be described in the General Disclosure Package and in the Prospectus or a document incorporated by reference therein or to be filed as an exhibit to the Registration Statement or a document incorporated by reference therein which is not described or filed therein as required; and all descriptions of any such franchises, leases, contracts, agreements or documents contained in the Registration Statement or in a document incorporated by reference therein are accurate and complete descriptions of such documents in all material respects. Other than as described in the General Disclosure Package, no such franchise, lease, contract or agreement has been suspended or terminated for convenience or default by the Company or any of its subsidiaries or any of the other parties thereto, and neither the Company nor any of its subsidiaries has received notice nor does the Company have any other knowledge of any such pending or threatened suspension, termination or non-renewal, except for such pending or threatened suspensions, terminations or non-renewals that would not reasonably be expected to, singularly or in the aggregate, have a Material Adverse Effect
Description of Agreements. There is no franchise, lease, contract, agreement or document required by the Securities Act to be described in the Prospectus or a document incorporated by reference therein or to be filed as an exhibit to the Registration Statement or a document incorporated by reference therein which is not described or filed therein as required; and all descriptions of any such franchises, leases, contracts, agreements or documents contained in the Registration Statement or in a document incorporated by reference therein are accurate and complete descriptions of such documents in all material respects. Other than as described in the Prospectus, no such franchise, lease, contract or agreement has been suspended or terminated for convenience or default by the Company or any of its subsidiaries or any of the other parties thereto, and neither the Company nor any of its subsidiaries has received notice nor does the Company have any other knowledge of any such pending or threatened suspension, termination or non-renewal, except for such pending or threatened suspensions, terminations or non-renewals that would not reasonably be expected to, singularly or in the aggregate, cause a Material Adverse Change.
Description of Agreements. The class Agreement Description as the segment description of SLA tem- plates and SLA has its own structure, which differs from the SLA* model. In the A-SLO-A Format the segment descriptions contains exactly one element of the class Property with the segment entries. These en- tries use the class Entry, which has two attributes key and value. The attribute key contains the type of the following document in the attribute value. The type can be either a CoverageDescr, a AgrementDescr or a Disclaimer. The information itself is stored in the attribute value. Signatures in SLAs and SLA Templates. New at- tributes are in the class SLATemplate the segment ProviderSignature and in the class SLATemplate the segment customerSignature. These containe the sig- nature of the corresponding party, for signing a SLA online. If the SLA is accepted by the cus- tomer/provider, the signature will be added to the SLA (segment customerSig) and/or SLATemplate (segment providerSig). Interface Declaration. The interface declaration is part of the service description and is used to connect the interfaces of a service and the SLOs. Also this is needed for the reference of further documents. There are two ways to implement that useing the abstract class interface. First the class ResVersion is used to keep further external documentation in the segment endpoints. The class Endpoints contains the three attributes location, id and protocol, to describe how to access the document. The location represents the location of the file, for example an URL, the proto- col states the required protocol to access the file, for an URL this could be HTTP or HTTPS. The id con- tains an unique identifier for the document. The at- tribute refProvider describes, who deposit the docu- ment. Also the segment interface is represented by the class with the same name, which contains through the class ResourceType the type of the document. This is in uppercase the type of the document. For exam- ple for an PDF document the shortcut ’PDF’ is used. Second the class SpecVersion, that can be defined by Figure 4: Overview of Agreement Terms. WSDL (Web Service Description Language). This is also part of the XXX* interface specification.
Description of Agreements. The terms of the Notes, the Indenture, the ADSs and the share capital of the Issuer, including the Shares represented by the ADSs, conform and will conform in all material respects to the descriptions thereof contained in the Offering Document.
Description of Agreements. Each of the Transaction Documents conforms in all material respects to the description thereof contained in the Registration Statement, the General Disclosure Package and the Prospectus. The Reorganization Transactions conform in all material respects to the descriptions thereof contained in the Registration Statement, the General Disclosure Package and the Prospectus.
AutoNDA by SimpleDocs
Description of Agreements. This Agreement, each of the Trust Agreements and each of the Subadvisory Agreements complies in all material respects with all applicable provisions of the 1940 Act, the 1940 Act Rules and Regulations, the Advisers Act and the Advisers Act Rules and Regulations and, in the case of the MLIM International Subadvisory Agreement, the FSMA, the FSMA Regulations and the FSA Handbook. Each of the Successor Advisory Agreement and each of the Successor Subadvisory Agreements, when executed and delivered, will comply in all material respects with all applicable provisions of the 1940 Act, the 1940 Act Rules and Regulations, the Advisers Act and the Advisers Act Rules and Regulations and, in the case of the MLIM International Subadvisory Agreement, the FSMA, the FSMA Regulations and the FSA Handbook.
Description of Agreements. The Indenture, the Notes, the Guarantees, the Collateral and the Collateral Documents conform in all material respects to the descriptions thereof contained in the General Disclosure Package and the Final Offering Circular.
Description of Agreements. This Agreement and each of the Trust Agreements complies in all material respects with all applicable provisions of the 1940 Act, the 1940 Act Rules and Regulations, the Advisers Act and the Advisers Act Rules and Regulations.
Time is Money Join Law Insider Premium to draft better contracts faster.