Nexus Requirements definition

Nexus Requirements means those requirements set forth at xxx.xxxxx.xx.
Sample 1Sample 2
Nexus Requirements means that You are (a) a natural person (i) who is a citizen of the United States of America, (ii) who is a permanent resident of the United States of America or its possessions or territories, or (iii) whose primary place of domicile is in the United States of America; (b) an entity or organization that is (i) incorporated in one of the fifty (50) States of the United States of America, the District of Columbia, or the possessions or territories of the United States of America, (ii) organized or otherwise constituted under the laws of one of the fifty (50) States of the United States of America, the District of Columbia, or the possessions or territories of the United States of America (including a federal, state, or local government of the United States of America or a political subdivision thereof, and non-commercial organizations based in the United States); or (c) a foreign entity or organization that has a Bona Fide Presence in the United States of America or its possessions or territories. A “Bona Fide Presence” shall mean the existence of real and substantial lawful connections with, or lawful activities in, the United States of America or its possessions or territories as certified by evidence acceptable to Registrar.
Sample 1Sample 2
Nexus Requirements means conditions of approval and CEQA mitigation measures addressing impacts resulting from the Project.
Sample 1

Examples of Nexus Requirements in a sentence

  • The Dispute Policy will provide interested parties with an opportunity to challenge a registration not complying with the Nexus Requirements.

  • The challenger must submit a written statement to the usTLD Administrator via first class mail alleging in specificity evidence to support its allegation that the registrant fails to meet any of the Nexus Requirements set forth above.

  • If, within the thirty (30) days, the registrant submits evidence establishing any of the Nexus Requirements, the registrant shall be permitted to keep the domain name.

  • If the registrant either (i) does not respond within the thirty (30) days, or (ii) is unable to proffer evidence demonstrating compliance with the Nexus Requirements, the domain name registration shall be deleted from the registry database and the domain name will be placed into the list of available domain names.

  • If, however, the registrant either (i) does not respond within the thirty days, or (ii) is unable to demonstrate through documentary evidence that it met any of the Nexus Requirements prior to the date the NDP was invoked, the usTLD Administrator shall issue a finding that the registrant has failed to meet the Nexus Requirements.

  • In the event that the usTLD Administrator finds that the challenger has established a prima facie case that the registrant has not met any of the Nexus Requirements, the usTLD Administrator shall issue a letter to the registrant to submit evidence of compliance with the Nexus Requirements ("Letter").

  • Impact Fee Nexus Requirements (AB 1600) Assembly Bill (AB) 1600, which was enacted by the State of California in 1987, created Mitigation Fee Act - Section 66000 et seq.

  • You are required to submit to a mandatory administrative proceeding in the event that a third party (a “Complainant”) asserts to the dispute provider (“Provider”), in compliance with the Rules, that your domain name has been registered or is being used in violation of the Nexus Requirements.

  • In the event that the Provider finds that the Complainant has not established a prima facie case that Registrant has not met any of the Nexus Requirements, the Provider shall issue a letter to the Complainant denying its challenge.

  • If, within the Response Period, Registrant submits evidence establishing any of the Nexus Requirements, the Panelist shall issue, within fourteen (14) business days from the end of the Response Period, a written finding directing that Registrant be permitted to keep the domain name.

Related to Nexus Requirements

  • OHS Requirements means all Laws applicable to the Supply and related to occupational health or safety, and all of the City Policies that relate to occupational health or safety, and includes without limitation the WCA;

  • Services Requirements means the requirements of the Authority or any other Contracting Body (as appropriate) for the Services from time to time;

  • MREL Requirements means the laws, regulations, requirements, guidelines, rules, standards and policies relating to minimum requirements for own funds and eligible liabilities applicable to the Issuer and/or the Group, from time to time, (including any applicable transitional or grandfathering provisions), including, without limitation to the generality of the foregoing, any delegated or implementing acts (such as regulatory technical standards) adopted by the European Commission and any regulations, requirements, guidelines, rules, standards and policies relating to minimum requirements for own funds and eligible liabilities adopted by the Federal Republic of Germany or the Republic of Italy, a relevant resolution authority or the European Banking Authority from time to time (whether or not such requirements, guidelines or policies are applied generally or specifically to the Issuer and/or the Group), as any of the preceding laws, regulations, requirements, guidelines, rules, standards, policies or interpretations may be amended, supplemented, superseded or replaced from time to time.

  • Listings Requirements means the listings requirements of the JSE from time to time;

  • Privacy Requirements means all applicable Privacy Laws and all of the Company’s and the Company Subsidiaries’ policies, notices, and contractual obligations relating to the Processing of Personal Information.

  • Program Requirements means certain minimum program entry requirements as well as ongoing program requirements, to be fulfilled by Partner, some of which are general PartnerEdge requirements, some of which are specific for the “Sell Engagement” and some of which are specific for the different “Cloud” Product Families, including, without limitation payment of the Program Fee(s), meeting certain minimum annual revenue requirements, upholding a Sell Authorization for at least one “Cloud” Product Family and other requirements as set out in detail in the PartnerEdge Program Guide and the RSPI.

  • JSE Listings Requirements means the Listings Requirements of the JSE applicable from time to time;

  • Risk Retention Requirements means the credit risk retention requirements of Section 15G of the Exchange Act (15 U.S.C. §78o-11), as added by Section 941 of the Xxxx-Xxxxx Xxxx Street Reform and Consumer Protection Act.

  • Operational requirements means the need to ensure that the Agency is to be operated as effectively, efficiently and economically as possible.

  • Project Requirements means the statement included in the Request for Proposal detailing the technical and other requirements of Canada which are to be met by the successful Bidder, and which are to be addressed in the Bid;

  • Safety Requirements means Prudent Electrical Practices, CPUC General Order No. 167, Contractor Safety Program Requirements, and all applicable requirements of Law, PG&E, the Utility Distribution Company, the Transmission Provider, Governmental Approvals, the CAISO, CARB, NERC and WECC.

  • Design requirements means the written description of the infrastructure facility to be procured pursuant to this article, including:

  • Service Requirements means the specification that the Flexibility Services must be capable of meeting, as defined in Schedule 1;

  • Minimum Requirements means the minimum requirements for available commercial structures. The minimum requirements may be found at this link: https://portlandgeneral.com/energy- choices/renewable-power/green-future-impact The minimum requirements may be updated from time to time to reflect PGE’s criteria from its latest Commission accepted renewable request for proposals.

  • Technical Requirements means the Technical Requirements in Section VII of the tendering documents.

  • Relevant Requirements means all applicable Law relating to bribery, corruption and fraud, including the Bribery Act 2010 and any guidance issued by the Secretary of State for Justice pursuant to section 9 of the Bribery Act 2010;

  • End Client Requirements means the specific requirements of the End Client, as notified to the Supplier in writing;

  • Statutory Requirements means all approvals, consents, permits, or licences necessary for the purposes of the Project from the State, any government department, authority, instrumentality or local government authority, and includes, without limiting the generality of the foregoing, all approvals, consents, permits, and licences, for engineering drawings, construction plans, earthworks and structures necessary for the purposes of the Project;

  • Data Protection Requirements means all applicable (i) Data Protection Laws, (ii) Privacy Policies and (iii) those terms of any Contracts imposing obligations on the Company or its Subsidiaries with respect to the Company’s collection, use, storage, disclosure, or cross-border transfer of Personal Data.

  • Listing Requirements means the Main Market Listing Requirements of Bursa Securities.

  • Pretreatment requirements means any substantive or procedural requirement related to pretreatment, other than a pretreatment standard, imposed on an industrial user.

  • Applicable Technical Requirements and Standards means those certain technical requirements and standards applicable to interconnections of generation and/or transmission facilities with the facilities of an Interconnected Transmission Owner or, as the case may be and to the extent applicable, of an Electric Distributor, as published by Transmission Provider in a PJM Manual provided, however, that, with respect to any generation facilities with maximum generating capacity of 2 MW or less (synchronous) or 5 MW or less (inverter-based) for which the Interconnection Customer executes a Construction Service Agreement or Interconnection Service Agreement on or after March 19, 2005, “Applicable Technical Requirements and Standards” shall refer to the “PJM Small Generator Interconnection Applicable Technical Requirements and Standards.” All Applicable Technical Requirements and Standards shall be publicly available through postings on Transmission Provider’s internet website.

  • Storage Injection Requirements means all volumes required by the Seller for injection into underground storage, including cushion gas, and for liquification, including fuel used for injection and in liquification plants, or for such other storage projects that may be developed expressly for the protection of supply to high priority users.

  • MREL Requirement means the minimum requirement for own funds and eligible liabilities which is or, as the case may be, will be applicable to the Issuer;

  • Regulatory Requirements means all applicable federal and state statutes, regulations, regulatory guidance, judicial or administrative rulings, requirements of Governmental Contracts and standards and requirements of any accrediting or certifying organization, including, but not limited to, the requirements set forth in a Product Attachment.

  • Perfection Requirements means the making or procuring of filings, stampings, registrations, notarisations, endorsements, translations and/or notifications of any Finance Document (and/or any Security created under it) necessary for the validity, enforceability (as against the relevant Obligor or any relevant third party) and/or perfection of that Finance Document.