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.
Delay of Registration; Furnishing Information (a) No Holder shall have any right to obtain or seek an injunction restraining or otherwise delaying any such registration as the result of any controversy that might arise with respect to the interpretation or implementation of this Section 2.
(b) It shall be a condition precedent to the obligations of the Company to take any action pursuant to Section 2.2, 2.3 or 2.4 that the selling Holders shall furnish to the Company such information regarding themselves, the Registrable Securities held by them and the intended method of disposition of such securities as shall be required to effect the registration of their Registrable Securities.
(c) The Company shall have no obligation with respect to any registration requested pursuant to Section 2.2 or Section 2.4 if the number of shares or the anticipated aggregate offering price of the Registrable Securities to be included in the registration does not equal or exceed the number of shares or the anticipated aggregate offering price required to originally trigger the Company’s obligation to initiate such registration as specified in Section 2.2 or Section 2.4, whichever is applicable.
Content and Services Neither Licensor nor the provider of the wireless network is the provider of any financial services available through or related to the Software, and neither Licensor nor the provider of the wireless network or any contractor of the provider of the financial services available through or related to the Software, is responsible for any of the materials, information, products or services made available to you via the Software.
Alternative Warning Xxxxxxx may, but is not required to, use the alternative short-form warning as set forth in this § 2.3(b) (“Alternative Warning”) as follows: WARNING: Cancer and Reproductive Harm - xxx.X00Xxxxxxxx.xx.xxx.
Application of other Rules and Special Commitments 1. Where a matter is governed simultaneously both by this Agreement and by another international agreement to which both Contracting Parties are parties, nothing in this Agreement shall prevent either Contracting Party or any of its investors who own investments in the territory of the other Contracting Party from taking advantage of whichever rules are more favourable to his case.
2. If the treatment to be accorded by one Contracting Party to investors of the other Contracting Party in accordance with its laws and regulations or other specific provisions of contracts is more favourable than that accorded by the Agreement, the more favourable shall be accorded.
Covenant to Provide Financial Information and Maintain Sufficient Capital The Administrator shall obtain and maintain the necessary capital to fulfill its obligations under this Agreement and shall remain solvent. The Administrator will report to the Issuer on a semi-annual basis its current and total assets, current and total liabilities, and total equity and the Company intends to include such amounts in its SEC reports.
Audit of Existing Content and Functionality By September 1, 2017, the Recipient will propose for OCR’s review and approval the identity and bona fides of an Auditor (corporation or individual) to audit all content and functionality on its website, including, but not limited to, the home page, all subordinate pages, and intranet pages and sites, to identify any online content or functionality that is inaccessible to persons with disabilities, including online content and functionality developed by, maintained by, or offered through a third party vendor or an open source. The Auditor will have sufficient knowledge and experience in website accessibility for people with disabilities to carry out all related tasks, including developing a Proposed Corrective Action Plan. The Audit will use the Benchmarks for Measuring Accessibility set out above, unless the Recipient receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the Recipient will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the Recipient, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.
AT WEBSITE XXX XXXXXXXXXXXXXXXX.XXX
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.
1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database.
1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value.
1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.
1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Deadlines for Providing Insurance Documents after Renewal or Upon Request As set forth herein, certain insurance documents must be provided to the OGS Procurement Services contact identified in the Contract Award Notice after renewal or upon request. This requirement means that the Contractor shall provide the applicable insurance document to OGS as soon as possible but in no event later than the following time periods:
