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.
Specific Preliminaries C1. Proprietary branded products The contractor shall take delivery of, handle, store, use, apply and/or fix all proprietary branded products in strict accordance with the manufacturer's instructions after consultation with the manufacturer's authorised representative. 95 F: ……….… V: ….……… T: ….……... Item C2. Trade Names, etc. All materials, fittings, finishings, etc., specified hereinafter under a trade name, catalogue number or reference, must be exactly as described. The Architect's approval in writing must be obtained for the use of any alternative to the specification before the submission of tenders otherwise the specified materials, fittings, finishings, etc., will be assumed to have been allowed for in the tender. The Contractor must take delivery of, handle, store, use, apply and/or fix all proprietary branded products in strict accordance with the manufacturer's instructions after consultation with the manufacturer's authorised representative. 96 F: ……….… V: ….……… T: ….……... Item C3. Contractors responsibility The Employer, the Principal Agent and the other professional consultants shall not be responsible for any act or omission on the part of the Contractor which may result in any patent or latent defects, in materials or workmanship, breach or neglect of any local regulations. The Contractor shall at all times be responsible for any such neglect, deviation or wrong act, whether the same is discovered before or after the final certificate, or any other Certificate, has been approved. 97 F: ……….… V: ….……… T: ….……... Item Carried to Collection R Section 1 Bill No. 1 Preliminaries C4. Overtime Should overtime be required to be worked for any reason whatsoever, the costs of such overtime are to be borne by the contractor unless the principal agent has specifically authorised in writing, prior to the execution thereof, that costs for such overtime are to be borne by the employer. 98 F: ……….… V: ….……… T: ….……... Item
Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.
CAFA Notice Pursuant to 28 U.S.C. § 1715, not later than ten (10) days after the Agreement is filed with the Court, the Settlement Administrator shall cause to be served upon the Attorneys General of each U.S. State in which Settlement Class members reside, the Attorney General of the United States, and other required government officials, notice of the proposed settlement as required by law, subject to Paragraph 5.1 below.
Signaling Parameters All SS7 signaling parameters will be provided in conjunction with traffic exchange trunk groups, where and as available. These parameters include Automatic Number Identification ("ANI"), Calling Party Number ("CPN"), Privacy Indicator, calling party category information, originating line information, charge number, etc. Also included are all parameters relating to network signaling information, such as Carrier Information Parameter ("CIP"), wherever such information is needed for call routing or billing. GTE will provide SS7 via GR-394-SS7 and/or GR-317-SS7 format(s).
Product Specific Terms these terms apply to specific Products referenced in this section.
Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.
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.
