Limited Agreement to Disclose Sample Clauses

Limited Agreement to Disclose. In the event that the Member has actual knowledge that the Member would be unwilling to provide other Members with a license to a work-in-progress of any Working Group, such Member agrees to promptly provide written notification to the Secretariat and appropriate Work Group chairperson of such Member’s intent not to license. Nothing in this Section is intended to create a duty for a Member to conduct a search of its patent portfolio.
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
Limited Agreement to Disclose. When Member Participates in a Workgroup, Member shall make reasonable efforts to disclose to the Workgroup the existence of copyrights, or patents or patent applications that may contain Necessary Claims, or any other intellectual property rights infringed by draft or final Works developed or considered by that Workgroup as soon as possible after discovering that such Works may infringe such copyrights, read on Necessary Claims, or infringe any other intellectual property rights. This obligation is limited to copyrights, Necessary Claims and other intellectual property rights that are personally known as such to the individuals acting on behalf of Member with respect to its Participation in that Workgroup. For patents and published applications, the disclosure shall identify the patent or application in question as well as the claims of such patent or application that may be Necessary Claims. For unpublished applications, the disclosure need not identify the claims that may be Necessary Claims, but shall identify with particularity the portions of any draft or final Work that might read on the claims. Notwithstanding the foregoing, in no event is Member obligated to conduct a search of its patents or pending applications.
Sample 1Sample 2
Limited Agreement to Disclose. Individual Members should declare at the earliest opportunity, any of their patents which they know to include Essential Claims, or potentially Essential Claims. In the event that Member has actual knowledge that the Member or its organization would be unwilling to provide a FRAND license to any such Essential Claims (or a royalty-free patent license with respect to OIX Deliverables produced by those Working Groups for which the OIX Board has imposed a RF Licensing Requirement) to any party that implements an OIX Deliverable (including those in draft or “work-in-progress” form) of any OIX Working Group, Member will promptly provide written notification to the Secretariat and appropriate Work Group chairperson of Member’s intent not to license. The Secretariat will maintain a list of all such declarations and the Working Group to which they relate. Nothing in this Section is intended to create a duty for Member to conduct a search of Member’s organization’s patent portfolio.
Sample 1
Limited Agreement to Disclose. When Member Participates in a Workgroup, Member shall make reasonable efforts to disclose to the Workgroup the existence of patents or patent applications that may contain Necessary Claims infringed by Specifications, Draft Specifications or Compliance Test Suites developed or considered by that Workgroup as soon as possible after discovering that they may contain Necessary Claims. This obligation is limited to Necessary Claims that are personally known as such to the individuals acting on behalf of Member with respect to its Participation in that Workgroup. For patents and published applications, the disclosure shall identify the patent or application in question as well as the claims of such patent or application that may be Necessary Claims. For unpublished applications, the disclosure need not identify the claims that may be Necessary Claims, but shall identify with particularity the portions of any Draft Specification or Specification and that might read on the claims. In no event is Member obligated to conduct a search of its patents or pending applications.
Sample 1

Related to Limited Agreement to Disclose

  • Right to Disclose With respect to any information, knowledge, or data disclosed to the Contractor by the Subcontractor, the Subcontractor warrants that the Subcontractor has full and unrestricted right to disclose the same without incurring legal liability to others, and that the Contractor shall have the full and unrestricted rights to use and publish the same as it may see fit. Any restrictions on Contractor’s use of information, knowledge, or data disclosed by Subcontractor must be made known to Contractor.

  • DUTY TO DISCLOSE If circumstances change or additional information is obtained regarding any of the representations and warranties made by the Applicant in the Application or this Agreement, or any other disclosure requirements, subsequent to the date of this Agreement, the Applicant’s duty to disclose continues throughout the term of this Agreement.

  • Nondisclosure of Private Proprietary or Confidential Information 13.1.1 If this Agreement requires City to disclose "Private Information" to Contractor within the meaning of San Francisco Administrative Code Chapter 12M, Contractor and subcontractor shall use such information only in accordance with the restrictions stated in Chapter 12M and in this Agreement and only as necessary in performing the Services. Contractor is subject to the enforcement and penalty provisions in Chapter 12M.

  • Compelled Disclosure of Confidential Information Notwithstanding anything in the foregoing to the contrary, the Receiving Party may disclose Confidential Information pursuant to any governmental, judicial, or administrative order, subpoena, discovery request, regulatory request or similar method, provided that the Receiving Party promptly notifies, to the extent practicable, the Disclosing Party in writing of such demand for disclosure so that the Disclosing Party, at its sole expense, may seek to make such disclosure subject to a protective order or other appropriate remedy to preserve the confidentiality of the Confidential Information; provided in the case of a broad regulatory request with respect to the Receiving Party’s business (not targeted at Disclosing Party), the Receiving Party may promptly comply with such request provided the Receiving Party give (if permitted by such regulator) the Disclosing Party prompt notice of such disclosure. The Receiving Party agrees that it shall not oppose and shall cooperate with efforts by, to the extent practicable, the Disclosing Party with respect to any such request for a protective order or other relief. Notwithstanding the foregoing, if the Disclosing Party is unable to obtain or does not seek a protective order and the Receiving Party is legally requested or required to disclose such Confidential Information, disclosure of such Confidential Information may be made without liability.

  • Incorporation of Schedules and Exhibits The schedules, attachments and exhibits referenced in and attached to this Agreement shall be deemed an integral part hereof to the same extent as if written in whole herein. In the event that any inconsistency or conflict exists between the provisions of this Agreement and any schedules, attachments or exhibits attached hereto, the provisions of this Agreement shall supersede the provisions of any such schedules, attachments or exhibits.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • Data Disclosure Under Minnesota Statute § 270C.65, Subdivision 3 and other applicable law, the Contractor consents to disclosure of its social security number, federal employer tax identification number, and/or Minnesota tax identification number, already provided to the State, to federal and state agencies and state personnel involved in the payment of state obligations. These identification numbers may be used in the enforcement of federal and state laws which could result in action requiring the Contractor to file state tax returns, pay delinquent state tax liabilities, if any, or pay other state liabilities.

  • Not to disclose PIN You must not disclose the PIN and must take all care to prevent the PIN from being disclosed to any other person.

  • No Disclosure Provider acknowledges and agrees that it shall not make any re-disclosure of any Student Data or any portion thereof, including without limitation, user content or other non-public information and/or personally identifiable information contained in the Student Data other than as directed or permitted by the LEA or this DPA. This prohibition against disclosure shall not apply to aggregate summaries of De-Identified information, Student Data disclosed pursuant to a lawfully issued subpoena or other legal process, or to subprocessors performing services on behalf of the Provider pursuant to this DPA. Provider will not Sell Student Data to any third party.

  • Return of material containing or pertaining to the Confidential Information 7.1 The Disclosing Party may, at any time, and in its sole discretion request the Receiving Party to return any material and/or data in whatever form containing, pertaining to or relating to Confidential Information disclosed pursuant to the terms of this Agreement and may, in addition request the Receiving Party to furnish a written statement to the effect that, upon such return, the Receiving Party has not retained in its possession, or under its control, either directly or indirectly, any such material and/or data.

Time is Money Join Law Insider Premium to draft better contracts faster.