POSTING OF FIRM CAPACITY Sample Clauses

POSTING OF FIRM CAPACITY. (1) Natural posts on the Informational Postings portion of its Interactive Website the firm capacity currently available on its system, as provided in Section 17.1(b)(1) of these General Terms and Conditions. Natural also posts consistent with the remainder of this Section 5.1(e), forward-haul firm transmission segment capacity and all Receipt Point, Delivery Point and storage firm capacity becoming available in the future (excluding firm capacity created by the construction of new facilities, including both expansions and extensions, until the initial allocation of such capacity has been made). Postings hereunder will be adjusted for capacity reserved under Section 5.1(c)(11) of these General Terms and Conditions. Natural is not obligated to post other types of firm capacity. The capacity which must be posted hereunder is Posted Capacity as referenced in Section 5.1(c)(1), except as provided in Section 5.1(e)(8).
AutoNDA by SimpleDocs

Related to POSTING OF FIRM CAPACITY

  • Service Registration Certain of our Services require you to register to use them. In such case, you agree that a l information you provide is truthful, current and complete. If there is any change to your registration information, you agree to provide us with updated information immediately. To the extent any of the Services are password protected, you agree to keep such password confidential and not to share it with any third party. You also agree that you wil not access any Services for which a password is required by using any third party’s password. If you discover any use of your password other than by you, you agree to immediately notify us. If you become aware of unauthorized account access, you similarly agree to immediately notify us. At the end of any use of a password protected Service, you agree to exit and logout out of your user session. Under no circumstances sha l we be responsible for any loss or damage that may result if you fail to comply with these requirements.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

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

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

  • Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.

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

  • Service Offerings Our Services vary and particular descriptions of such Services can be found at points where you access each respective Service. We genera ly provide the Services to you free of charge, unless otherwise noted at the time the Services are presented to you for acceptance and use. Use of our Services is subject to your agreement with this XXXX and your compliance with same. We make no representation or warranty with respect to the quality, accuracy and/or completeness of the Services. We may suspend, modify, terminate and/or alter the Services at any time and for any reason, in our sole discretion.

  • Resale of Services Except as expressly prohibited by law or regulation or as set forth in the Agreement, Customer may not resell, charge, transfer or otherwise dispose of Services (or any part thereof) to any third party.

  • Verification of the Registration of E - Bidders 6.1. Registration shall subject to verification and approval of the Auctioneer’s website and subject further to bank’s clearance of deposit payment. Please take note that approval from the Auctioneer’s administrator may take at least 1 working day and any improper, incomplete registration or late registration may be rejected at the sole discretion of the Auctioneer. Neither the Auctioneer nor its website nor its agents and/or representative bears any responsibility or assumes any liability in the event that the registration of a prospective E-Bidders is rejected and/or delayed for any reason whatsoever. In the event of the registration is rejected, the deposit paid (if cleared by the bank) shall be refunded to the same bank account from which the deposit transfer was made within three (3) working days.

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

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