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.
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.
Consent to Use of Data You grant NCR Voyix a perpetual, non-exclusive, irrevocable, sub-licensable, transferrable license to use the data transmitted through the Platform: (a) to provide the NCR Voyix Product and the Platform as well as related products, software, materials and services under this Agreement or another agreement between you and NCR Voyix; (b) for product and service enhancements, as well as research and development purposes; and (c) after it has been aggregated, for analytics, commercial and benchmarking purposes.
Abuse and Neglect of Children and Vulnerable Adults:
Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
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 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.
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.
Confidentiality; Use of Name Portfolio Manager and the Trust acknowledge and agree that during the term of this Agreement the parties may have access to certain information that is proprietary to the Trust or Portfolio Manager, respectively (or to their affiliates and/or service providers). The parties agree that their respective officers and employees shall treat all such proprietary information as confidential and will not use or disclose information contained in, or derived from such material for any purpose other than in connection with the carrying out of their responsibilities under this Agreement and the management of the Trust’s assets, provided, however, that this shall not apply in the case of: (i) information that is publicly available; and (ii) disclosures required by law or requested by any regulatory authority that may have jurisdiction over Portfolio Manager or the Trust, as the case may be, in which case such party shall request such confidential treatment of such information as may be reasonably available. In addition, each party shall use its reasonable efforts to ensure that its agents or affiliates who may gain access to such proprietary information shall be made aware of the proprietary nature and shall likewise treat such materials as confidential. It is acknowledged and agreed that the names “Xxxxxx Xxxxxxxxx,” “Xxxxxx Xxxxxxxxx Chief Investment Officers” (which is a registered trademark of Xxxxxx Xxxxxxxxx & Co., Inc. (“HCCI”)), “HC Capital” and derivatives of each, as well as any logo that is now or shall later become associated with either name (“Marks”) are valuable property of HCCI and that the use of the Marks, or any one of them, by the Trust or its agents is subject to the license granted to the Trust by HCCI. Portfolio Manager agrees that it will not use any Xxxx without the prior written consent of the Trust. Portfolio Manager consents to use of its name, performance data, biographical data and other pertinent data, and the Parametric Marks (as defined below), by the Trust for use in marketing and sales literature, provided that any such marketing and sales literature shall not be used by the Trust without the prior written consent of Portfolio Manager, which consent shall not be unreasonably withheld. The Trust shall have full responsibility for the compliance by any such marketing and sales literature with all applicable laws, rules, and regulations, and Portfolio Manager will have no responsibility or liability therefor. The provisions of this Section 8 shall survive termination of this Agreement. It is acknowledged and agreed that the names “Parametric Portfolio Associates” and “Parametric Xxxxxxx” and any portions or derivatives thereof, as well as any logo that is now or shall later become associated with such name (“Parametric Marks”), are valuable property of Portfolio Manager and that the use of the Parametric Marks by the Trust or its agents is permitted only so long as this Agreement is in place. The provisions of this Section 8 shall survive termination of this Agreement.
Use of FIIOC’s and FSC's Name The Trust shall not use the name of FIIOC and FSC in any Prospectus, sales literature or other material relating to the Trust or any Fund of the Trust in a manner not consented to by FIIOC and FSC prior to use; provided, however, that FIIOC and FSC shall approve all uses of its name which merely refer in accurate terms to its appointments, duties or fees hereunder or which are required by the Securities and Exchange Commission ("SEC" or “Commission”) or a state securities commission; and further, provided that in no event shall such approval be unreasonably withheld.
