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.
Sample 1Sample 2Sample 3
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.
Sample 1Sample 2
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.
Sample 1Sample 2
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.
Sample 1Sample 2

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

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

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

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

  • BUY AMERICA ACT (National School Lunch Program and Breakfast Program With respect to products purchased by Customers for use in the National School Lunch Program and/or National School Breakfast Program, Contractor shall comply with all federal procurement laws and regulations with respect to such programs, including the Buy American provisions set forth in 7 C.F.R. Part 210.21(d), to the extent applicable. Contractor agrees to provide all certifications required by Customer regarding such programs. In the event Contractor or Contractor’s supplier(s) are unable or unwilling to certify compliance with the Buy American Provision, or the applicability of an exception to the Buy American provision, H-GAC Customers may decide not to purchase from Contractor. Additionally, H-GAC Customers may require country of origin on all products and invoices submitted for payment by Contractor, and Contractor agrees to comply with any such requirement.

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

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

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

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

  • Reporting of Metered Data and Parameters 7.2.1 The grid connected Solar PV power plants will install necessary equipment for regular monitoring of solar irradiance (including GHI, DHI and solar radiation in the module plane), ambient air temperature, wind speed and other weather parameters and simultaneously for monitoring of the electric power (both DC and AC) generated from the Project.

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