PUBLICATION AND PUBLICITY The CONSULTANT agrees that it shall not for any reason whatsoever communicate to any third party in any manner whatsoever concerning any of its CONTRACT work product, its conduct under the CONTRACT, the results or data gathered or processed under this CONTRACT, which includes, but is not limited to, reports, computer information and access, drawings, studies, notes, maps and other data prepared by and for the CONSULTANT under the terms of this CONTRACT, without prior written approval from the COMMISSION, unless such release or disclosure is required by judicial proceeding. The CONSULTANT agrees that it shall immediately refer any third party who requests such information to the COMMISSION and shall also report to the COMMISSION any such third party inquiry. This Article shall not apply to information in whatever form that comes into the public domain, nor shall it restrict the CONSULTANT from giving notices required by law or complying with an order to provide information or data when such order is issued by a court, administrative agency or other authority with proper jurisdiction, or if it is reasonably necessary for the CONSULTANT to defend itself from any suit or claim. All approved releases of information, findings, and recommendations shall include a disclaimer provision and all published reports shall include that disclaimer on the cover and title page in the following form: The opinions, findings, and conclusions in this publication are those of the author(s) and not necessarily those of the Mississippi Department of Transportation, Mississippi Transportation Commission, the State of Mississippi or the Federal Highway Administration.
RESEARCH AND PUBLICATION 29 CONTRACTOR shall not utilize information and/or data received from COUNTY, or arising out 30 of, or developed, as a result of this Agreement for the purpose of personal or professional research, or 31 for publication. 32
Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.
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.
zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Introduction and Statement of Policy The National Institutes of Health (NIH) has established NIH-designated data repositories (e.g., database of Genotypes and Phenotypes (dbGaP), Sequence Read Archive (SRA), NIH Established Trusted Partnerships) for securely storing and sharing controlled-access human data submitted to NIH under the NIH Genomic Data Sharing (GDS)
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Use of Customer Statements The Contractor shall not use any statement attributable to the Customer or its employees for the Contractor’s promotions, press releases, publicity releases, marketing, corporate communications, or other similar communications, without first notifying the Customer’s Contract Manager and securing the Customer’s prior written consent.