Data Publication Clause Samples

The Data Publication clause governs how data generated or used under an agreement may be shared or published. Typically, it outlines the conditions under which parties can disclose data to third parties, such as requiring prior consent, anonymization, or compliance with applicable laws and confidentiality obligations. This clause ensures that sensitive or proprietary information is protected while allowing for the controlled dissemination of data, thereby balancing the interests of transparency and confidentiality.
Data Publication. Licensor shall not publish nor otherwise publicly disclose any data or results regarding any Product without the prior written consent of Licensee; provided, however, that Licensor may publish the data and results that it generates solely through the exercise of their retained right. If Licensee wishes to publish peer reviewed manuscripts disclosing any non-public results of studies carried out under this Agreement, it shall provide Licensor with the opportunity to review and comment on any proposed publication which relates to the Product at least thirty (30) days prior to its intended submission for publication. Licensee shall: (i) consider in good faith any comments thereto provided by Licensor within such thirty (30) day period; and (ii) remove any Confidential Information of Licensor identified by Licensor as part of its review.
Data Publication. Eisai shall not publish nor otherwise publicly disclose any data or results regarding any Compound or Product without the prior written consent of Roivant, provided that with respect to the proposed eight articles on Exhibit D listed as in process but not yet published on or prior to the Effective Date, Roivant shall have the right to (a) review each not less than [***] prior to intended submission for publication, or if such date has passed as of the Effective Date, within [***] after the Effective Date, and (b) comment on each article prior to its submission. If Roivant wishes to publish peer reviewed manuscripts disclosing the results of studies carried out under this Agreement provided that such publication does not disclose any of Eisai’s Confidential Information, it shall provide Eisai with the opportunity to review and [***] = CERTAIN CONFIDENTIAL INFORMATION CONTAINED IN THIS DOCUMENT, MARKED BY BRACKETS, IS FILED WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO RULE 406 OF THE SECURITIES ACT OF 1933, AS AMENDED. EXECUTION VERSION Confidential comment on any proposed publication which relates to the Product at least [***] prior to its intended submission for publication. Roivant shall: (i) consider in good faith any comments thereto provided by Eisai within such [***] period; and (ii) remove any Confidential Information of Eisai identified by Eisai as part of its review.
Data Publication. ‌ For the purpose of the Core FB MC shall be – mutatis mutandis – governed by article 11.5 of the SDAC DAOA.‌ On the basis of Art. 11.5.1.ii) of the SDAC DAOA, the Parties agree that NEMOs are entitled individually to publish TSOs data, i.e. Cross-Zonal Capacities (and optional Allocation Constraints), for the Core FB MC purposes, on condition that these data have been previously validated by the respective TSOs. TSOs hereby award authorization to NEMOs to publish scheduled exchanges between bidding zones in line with the rules stipulated in Art. 11.3.3 SDAC DAOA, if ▇▇▇▇▇ decide to.
Data Publication. 11.5.1. Without prejudice to Article 11.4: i) The Parties are entitled individually to publish their own data linked to SDAC. ii) The publication of other data linked to SDAC shall be dealt with in either this Agreement, Local Arrangements, NEMO 11.5.2. Without prejudice to Article 11.3.3. and 11.5.1, each TSO agrees and undertakes, up to the receipt of the Global Final Confirmation sent by the NEMOs, that neither it, nor its officers, employees, agents delegates or subcontractors, will forward or publish any price information included in the Market Coupling Results or use such price information otherwise than for the purposes of validation of Scheduled Exchanges and/or Congestion Revenue calculations. In addition, in case of breach, the NEMOs or any individual NEMO is entitled to demand, with immediate effect, a change of the TSO’s data handling processes for the purpose of result validation in such a way that the data concerned is no longer at risk. The TSOs shall not unreasonably object to such demand.
Data Publication. A list of data items and their timing of publication is contained in the following Table 47. Procedures for the updating of Publications and the method of Publication are contained in Agreed Procedure 6 “Data Publication”.
Data Publication. The CITI‐SENSE SEDS Platform enables access to data stored in the SEDS Data Repository via open web services. These web services include a mix of comprehensive WFS and light‐weight RESTful services, which supports a variety of data encodings such as XML, GML, CSV and JSON. For creating and deploying the WFS web services the software product GO Publisher for Snowflake Software is used and for creating and deploying the REST services Mulesoft Anypoint has been used.
Data Publication. 5.1 At the end of one calendar year, the data manager creates a file containing all data for all species and gardens that have been submitted to the PhenObs database. This data set is uploaded to the iDiv data repository (▇▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇/) and remains restricted for two years but can be provided on request (see 6.1). After two years, the data becomes freely accessible. 5.2 All data remains property of the data owners (e.g. persons responsible for the monitoring in the respective gardens). All data owners are listed in the metadata of the dataset uploaded to the iDiv data repository.
Data Publication. 1. Without prejudice to Article 11.4: i) The Parties are entitled individually to publish their own data linked to SDAC. ii) The publication of other data linked to SDAC shall be dealt with in either this Agreement, Local Arrangements, NEMO Only Agreements or TSO Only Agreements (including service agreements as the case may be).