Application of the Native Title Act Sample Clauses

Application of the Native Title Act. The parties agree that: (a) the grant of the Licence and the Lease are future acts as defined in the Native Title Act; (b) the Lease and Licence and any works carried out pursuant to these: (i) are validated under the Settlement ILUA or alternatively under section 24JA of the Native Title Act; and (ii) do not extinguish native title.
AutoNDA by SimpleDocs

Related to Application of the Native Title Act

  • Limitation on Out-of-State Litigation - Texas Business and Commerce Code § 272 This is a requirement of the TIPS Contract and is non-negotiable. Texas Business and Commerce Code § 272 prohibits a construction contract, or an agreement collateral to or affecting the construction contract, from containing a provision making the contract or agreement, or any conflict arising under the contract or agreement, subject to another state’s law, litigation in the courts of another state, or arbitration in another state. If included in Texas construction contracts, such provisions are voidable by a party obligated by the contract or agreement to perform the work. By submission of this proposal, Vendor acknowledges this law and if Vendor enters into a construction contract with a Texas TIPS Member under this procurement, Vendor certifies compliance.

  • Non-Contravention of Existing Instruments; No Further Authorizations or Approvals Required Neither the Company nor any of its subsidiaries is (i) in violation of its charter, bylaws or other constitutive document or (ii) in default (or, with the giving of notice or lapse of time, would be in default) (“Default”) under any indenture, mortgage, loan or credit agreement, note, contract, franchise, lease or other instrument to which the Company or any of its subsidiaries is a party or by which it or any of them may be bound, or to which any of the property or assets of the Company or any of its subsidiaries is subject (each, an “Existing Instrument”), except, in the case of clause (ii) above, for such Defaults as would not, individually or in the aggregate, result in a Material Adverse Change. The execution, delivery and performance of the Transaction Documents by the Company, and the issuance and delivery of the Securities, and consummation of the transactions contemplated hereby and thereby and by the Pricing Disclosure Package and the Prospectus (i) have been duly authorized by all necessary corporate action and will not result in any violation of the provisions of the charter, bylaws or other constitutive document of the Company or any subsidiary, (ii) will not conflict with or constitute a breach of, or Default or a Debt Repayment Triggering Event (as defined below) under, or result in the creation or imposition of any lien, charge or encumbrance upon any property or assets of the Company or any of its subsidiaries pursuant to, or require the consent of any other party to, any Existing Instrument, except for such conflicts, breaches, Defaults, liens, charges or encumbrances as would not, individually or in the aggregate, result in a Material Adverse Change or materially adversely affect the consummation by the Company of the transactions contemplated hereby, and (iii) will not result in any violation of any law, administrative regulation or administrative or court decree applicable to the Company or any subsidiary. On and as of the date hereof, no event has occurred or is continuing which constitutes, or with notice or lapse of time would constitute, an Event of Default (as defined in the Indenture). No consent, approval, authorization or other order of, or registration or filing with, any court or other governmental or regulatory authority or agency is required for the execution, delivery and performance of the Transaction Documents by the Company to the extent a party thereto, or the issuance and delivery of the Securities, or consummation of the transactions contemplated hereby and thereby and by the Pricing Disclosure Package and the Prospectus, except such as have been obtained or made by the Company and are in full force and effect under the Securities Act, applicable securities laws of the several states of the United States or provinces of Canada. As used herein, a “Debt Repayment Triggering Event” means any event or condition which gives, or with the giving of notice or lapse of time would give, the holder of any note, debenture or other evidence of indebtedness (or any person acting on such holder’s behalf) the right to require the repurchase, redemption or repayment of all or a portion of such indebtedness by the Company or any of its subsidiaries.

  • Waiver of Statutory Rights To the extent permitted by law, Mortgagor hereby agrees that it shall not and will not apply for or avail itself of any appraisement, valuation, stay, extension or exemption laws, or any so-called “Moratorium Laws,” now existing or hereafter enacted, in order to prevent or hinder the enforcement or foreclosure of this Mortgage, but hereby waives the benefit of such laws. Mortgagor for itself and all who may claim through or under it waives any and all right to have the property and estates comprising the Property marshalled upon any foreclosure of the lien hereof and agrees that any court having jurisdiction to foreclose such lien may order the Property sold as an entirety. Mortgagor hereby waives any and all rights of redemption from sale under any judgment of foreclosure of this Mortgage on behalf of Mortgagor and on behalf of each and every person acquiring any interest in or title to the Property of any nature whatsoever, subsequent to the date of this Mortgage. The foregoing waiver of right of redemption is made pursuant to the provisions of applicable law.

  • Regulatory Requirements and Governing Law 43 14.1 Regulatory Requirements. 43 14.2 Governing Law 44 ARTICLE 15. NOTICES 44 15.1 General. 44 15.2 Xxxxxxxx and Payments. 44 15.3 Alternative Forms of Notice 44 15.4 Operations and Maintenance Notice 44 ARTICLE 16. FORCE MAJEURE 45 16.1 Force Majeure 45 ARTICLE 17. DEFAULT 45 17.1 Default. 45 ARTICLE 18. INDEMNITY, CONSEQUENTIAL DAMAGES AND INSURANCE 46 18.1 Indemnity. 46 18.2 No Consequential Damages. 47 18.3 Insurance 47 ARTICLE 19. ASSIGNMENT 49 19.1 Assignment. 49 ARTICLE 20. SEVERABILITY 49 20.1 Severability. 49 ARTICLE 21. COMPARABILITY 50 21.1 Comparability. 50 ARTICLE 22. CONFIDENTIALITY 50 22.1 Confidentiality. 50 ARTICLE 23. ENVIRONMENTAL RELEASES 53 23.1 Developer and Connecting Transmission Owner Notice 53 ARTICLE 24. INFORMATION REQUIREMENT 53 24.1 Information Acquisition. 53 24.2 Information Submission by Connecting Transmission Owner 54 24.3 Updated Information Submission by Developer 54 24.4 Information Supplementation 54 ARTICLE 25. INFORMATION ACCESS AND AUDIT RIGHTS 55 25.1 Information Access. 55 25.2 Reporting of Non-Force Majeure Events. 55 25.3 Audit Rights. 56 25.4 Audit Rights Periods. 56 25.5 Audit Results. 56 ARTICLE 26. SUBCONTRACTORS 56 26.1 General. 56 26.2 Responsibility of Principal. 57 26.3 No Limitation by Insurance 57 ARTICLE 27. DISPUTES 57 27.1 Submission 57 27.2 External Arbitration Procedures. 57 27.3 Arbitration Decisions. 58 27.4 Costs. 58 27.5 Termination 58 ARTICLE 28. REPRESENTATIONS, WARRANTIES AND COVENANTS 58 28.1 General. 58 ARTICLE 29. MISCELLANEOUS 59 29.1 Binding Effect. 59 29.2 Conflicts. 59 29.3 Rules of Interpretation 59 29.4 Compliance 60 29.5 Joint and Several Obligations. 60 29.6 Entire Agreement. 60 29.7 No Third Party Beneficiaries. 60 29.8 Waiver 60 29.9 Headings. 61 29.10 Multiple Counterparts. 61 29.11 Amendment. 61 29.12 Modification by the Parties. 61 29.13 Reservation of Rights. 61 29.14 No Partnership 62 29.15 Other Transmission Rights. 62 Appendices STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT THIS STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT

  • OBLIGATIONS AND ACTIVITIES OF CONTRACTOR AS BUSINESS ASSOCIATE 1. CONTRACTOR agrees not to use or further disclose PHI COUNTY discloses to CONTRACTOR other than as permitted or required by this Business Associate Contract or as required by law. 2. XXXXXXXXXX agrees to use appropriate safeguards, as provided for in this Business Associate Contract and the Agreement, to prevent use or disclosure of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY other than as provided for by this Business Associate Contract. 3. XXXXXXXXXX agrees to comply with the HIPAA Security Rule at Subpart C of 45 CFR Part 164 with respect to electronic PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY. 4. CONTRACTOR agrees to mitigate, to the extent practicable, any harmful effect that is known to CONTRACTOR of a Use or Disclosure of PHI by CONTRACTOR in violation of the requirements of this Business Associate Contract. 5. XXXXXXXXXX agrees to report to COUNTY immediately any Use or Disclosure of PHI not provided for by this Business Associate Contract of which CONTRACTOR becomes aware. CONTRACTOR must report Breaches of Unsecured PHI in accordance with Paragraph E below and as required by 45 CFR § 164.410. 6. CONTRACTOR agrees to ensure that any Subcontractors that create, receive, maintain, or transmit PHI on behalf of CONTRACTOR agree to the same restrictions and conditions that apply through this Business Associate Contract to CONTRACTOR with respect to such information. 7. CONTRACTOR agrees to provide access, within fifteen (15) calendar days of receipt of a written request by COUNTY, to PHI in a Designated Record Set, to COUNTY or, as directed by COUNTY, to an Individual in order to meet the requirements under 45 CFR § 164.524. If CONTRACTOR maintains an Electronic Health Record with PHI, and an individual requests a copy of such information in an electronic format, CONTRACTOR shall provide such information in an electronic format. 8. CONTRACTOR agrees to make any amendment(s) to PHI in a Designated Record Set that COUNTY directs or agrees to pursuant to 45 CFR § 164.526 at the request of COUNTY or an Individual, within thirty (30) calendar days of receipt of said request by COUNTY. XXXXXXXXXX agrees to notify COUNTY in writing no later than ten (10) calendar days after said amendment is completed. 9. CONTRACTOR agrees to make internal practices, books, and records, including policies and procedures, relating to the use and disclosure of PHI received from, or created or received by CONTRACTOR on behalf of, COUNTY available to COUNTY and the Secretary in a time and manner as determined by COUNTY or as designated by the Secretary for purposes of the Secretary determining COUNTY’S compliance with the HIPAA Privacy Rule. 10. CONTRACTOR agrees to document any Disclosures of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, and to make information related to such Disclosures available as would be required for COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 11. CONTRACTOR agrees to provide COUNTY or an Individual, as directed by COUNTY, in a time and manner to be determined by COUNTY, that information collected in accordance with the Agreement, in order to permit COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 12. XXXXXXXXXX agrees that to the extent CONTRACTOR carries out COUNTY’s obligation under the HIPAA Privacy and/or Security rules CONTRACTOR will comply with the requirements of 45 CFR Part 164 that apply to COUNTY in the performance of such obligation. 13. If CONTRACTOR receives Social Security data from COUNTY provided to COUNTY by a state agency, upon request by COUNTY, CONTRACTOR shall provide COUNTY with a list of all employees, subcontractors and agents who have access to the Social Security data, including employees, agents, subcontractors and agents of its subcontractors. 14. CONTRACTOR will notify COUNTY if CONTRACTOR is named as a defendant in a criminal proceeding for a violation of HIPAA. COUNTY may terminate the Agreement, if CONTRACTOR is found guilty of a criminal violation in connection with HIPAA. COUNTY may terminate the Agreement, if a finding or stipulation that CONTRACTOR has violated any standard or requirement of the privacy or security provisions of HIPAA, or other security or privacy laws are made in any administrative or civil proceeding in which CONTRACTOR is a party or has been joined. COUNTY will consider the nature and seriousness of the violation in deciding whether or not to terminate the Agreement.

  • Waiver of Statutes Lessor and Lessee agree that the terms of this Lease shall govern the effect of any damage to or destruction of the Premises and the Building with respect to the termination of this Lease and hereby waive the provisions of any present or future statute to the extent it is inconsistent herewith.

  • Authorization of the Common Shares The Common Shares to be purchased by the Underwriters from the Company have been duly authorized for issuance and sale pursuant to this Agreement and, when issued and delivered by the Company pursuant to this Agreement, will be validly issued, fully paid and nonassessable.

  • No Physical Presence of Quorum and Participation by Audio or Video; Disaster Declaration The ability of the Board to meet in person with a quorum physically present at its meeting location may be affected by the Governor or the Director of the Ill. Dept. of Public Health issuing a disaster declaration related to a public health emergency. The Board President or, if the office is vacant or the President is absent or unable to perform the office’s duties, the Vice President determines that an in- person meeting or a meeting conducted under the Quorum and Participation by Audio or Video Means subhead above, is not practical or prudent because of the disaster declaration; if neither the President nor Vice President are present or able to perform this determination, the Superintendent shall serve as the duly authorized designee for purposes of making this determination. The individual who makes this determination for the Board shall put it in writing, include it on the Board’s published notice and agenda for the audio or video meeting and in the meeting minutes, and ensure that the Board meets every OMA requirement for the Board to meet by video or audio conference without the physical presence of a quorum.

  • 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”.

  • COMPLIANCE WITH NEW YORK STATE INFORMATION SECURITY BREACH AND NOTIFICATION ACT Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law Section 899-aa; State Technology Law Section 208).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!