Registration for an Industry Specification Group meeting (TWP 1 Sample Clauses

Registration for an Industry Specification Group meeting (TWP 1. 5.4) Every Attendee shall register on arrival at each meeting. Each Attendee who represents an ISG member or ISG Participant organization shall declare the precise name of that organization. An Attendee may only represent one ISG member or one ISG Participant.
AutoNDA by SimpleDocs
Registration for an Industry Specification Group meeting (TWP 1. 5.4) Every Attendee shall register prior to the meeting using the Meetings Application on the ETSI Portal or on arrival at the meeting. Where registration is made on arrival at the meeting each Attendee representing an ISG CCM Member or ISG CCM Participant shall declare the precise name of that ISG CCM Member or ISG CCM Participant. An Attendee may only represent one ISG CCM Member or one ISG CCM Participant.
Registration for an Industry Specification Group meeting (TWP 1. 5.4) Every attendee shall register prior to the meeting using the Meetings Application on the ETSI Portal or on arrival at the meeting. Where registration is made on arrival at the meeting each Attendee representing an ISG NGP Member or ISG NGP Participant shall declare the precise name of that ISG NGP Member or ISG NGP Participant. An Attendee may only represent one ISG NGP Member or one ISG NGP Participant.
Registration for an Industry Specification Group meeting (TWP 1. 5.4) Every attendee shall register prior to the meeting using the Meetings Application on the ETSI Portal or on arrival at the meeting. Where registration is made on arrival at the meeting each Attendee representing an ISG MBC Member or ISG MBC Participant shall declare the precise name of that ISG MBC Member or ISG MBC Participant. An Attendee may only represent one ISG MBC Member or one ISG MBC Participant.

Related to Registration for an Industry Specification Group meeting (TWP 1

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Indemnification for Marketing Materials In addition to the foregoing indemnification, the Fund and the Investment Adviser also, jointly and severally, agree to indemnify and hold harmless each Underwriter, affiliates, directors, officers, employees and agents of each Underwriter, and each person, if any, who controls any Underwriter within the meaning of Section 15 of the 1933 Act or Section 20 of the 1934 Act, against any and all loss, liability, claim, damage and expense described in the indemnity contained in Section 6(a), as limited by the proviso set forth therein, with respect to any sales material.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Registration Compliance; No Stop Order No order suspending the effectiveness of the Registration Statement shall be in effect, and no proceeding for such purpose or pursuant to Section 8A under the Securities Act shall be pending before or threatened by the Commission; the Prospectus and each Issuer Free Writing Prospectus shall have been timely filed with the Commission under the Securities Act (in the case of an Issuer Free Writing Prospectus, to the extent required by Rule 433 under the Securities Act) and in accordance with Section 4(a) hereof; and all requests by the Commission for additional information shall have been complied with to the reasonable satisfaction of the Representatives.

  • Commercialization Plan On a Product by Product basis, not later than sixty (60) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory, the MSC shall prepare and approve a rolling multiyear (not less than three (3) years) plan for Commercializing such Product in the Copromotion Territory (the "Copromotion Territory Commercialization Plan"), which plan includes a comprehensive market development, marketing, sales, supply and distribution strategy for such Product in the Copromotion Territory. The Copromotion Territory Commercialization Plan shall be updated by the MSC at least once each calendar year such that it addresses no less than the three (3) upcoming years. Not later than thirty (30) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory and thereafter on or before September 30 of each calendar year, the MSC shall prepare an annual commercialization plan and budget (the "Annual Commercialization Plan and Budget"), which plan is based on the then current Copromotion Territory Commercialization Plan and includes a comprehensive market development, marketing, sales, supply and distribution strategy, including an overall budget for anticipated marketing, promotion and sales efforts in the upcoming calendar year (the first such Annual Development Plan and Budget shall cover the remainder of the calendar year in which such Product is anticipated to be approved plus the first full calendar year thereafter). The Annual Commercialization Plan and Budget will specify which Target Markets and distribution channels each Party shall devote its respective Promotion efforts towards, the personnel and other resources to be devoted by each Party to such efforts, the number and positioning of Details to be performed by each Party, as well as market and sales forecasts and related operating expenses, for the Product in each country of the Copromotion Territory, and budgets for projected Pre-Marketing Expenses, Sales and Marketing Expenses and Post-Approval Research and Regulatory Expenses. In preparing and updating the Copromotion Territory Commercialization Plan and each Annual Commercialization Plan and Budget, the MSC will take into consideration factors such as market conditions, regulatory issues and competition.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Form B - Contractor’s Annual Employment Report Throughout the term of the Contract by May 15th of each year the Contractor agrees to report the following information to the State Agency awarding the Contract, or if the Contractor has provided Contract Employees pursuant to an OGS centralized Contract, such report must be made to the State Agency purchasing from such Contract. For each covered consultant Contract in effect at any time between the preceding April 1st through March 31st fiscal year or for the period of time such Contract was in effect during such prior State fiscal year Contractor reports the:

Time is Money Join Law Insider Premium to draft better contracts faster.