Jusletter IT

Fuzzy Know-how

  • Author: Daniel Ronzani
  • Category of articles: TechLawNews by Ronzani Schlauri Attorneys
  • Region: Switzerland
  • Field of law: IP-Law
  • DOI: 10.38023/ffa6e9f0-2c54-47ab-b636-e19f5723ebf7
  • Citation: Daniel Ronzani, Fuzzy Know-how, in: Jusletter IT 27 May 2021
[1]

Depending on which side of the negotiation table you’re sitting on, the definition of intellectual property (IP) can be most relevant for the outcome of IP ownership, IP licensing and IP liability. For instance, whereas a software developer might want to retain as much (newly created) IP as possible and limit her liability regarding 3rd infringement of the software, her customer will likely seek a broad IP license and IP indemnification if the software infringes 3rd party rights. Often, know-how is forgotten by the parties. Does IP include know-how?

[2]

Know-how can be defined as knowledge of the methods or techniques of doing something, especially something technical or practical1, and possibly smoothly and efficiently, also known as expertise2. Legally, know-how might be summarized as information relating to IP and its exploitation3. Art. 1(1)(i) of the European Technology Transfer Block Exemption Regulation (TTBER)4 defines know-how a package of practical information, resulting from experience and testing, which is (i) secret, (ii) substantial, and (iii) identified (i.e. allowing verification of the qualifiers secret (i) and substantiality (ii)).

[3]

Hence, a common definition of know-how does not seem to exist. But at least there seems to be common understanding that know-how and trade secrets5 are not identical terms6: whereas the legal term «know-how» seems to be a trade secret, a trade secret is not necessarily know-how.

[4]

Applying this legal understanding to the software development example, the owner and licensor might grant access to the software code, but not necessarily also to the underlying development know-how. As example, a way to prevent access to such trade secrets might be compiling the source code.

[5]

If know-how is knowledge, information and/or experience it is undoubtedly intellectual property. As noted above, legally it is also a trade secret. Given the diffuse and unclear scope of the term «know-how» and what the parties might assume it includes (or does not include), it is recommended to clarify its integration or exclusion in any contractual definition of IP. This might be achieved by either enumerating the types of IP in a conclusive list (e.g. «IP means patents, copyrights, trademarks»); or, if the list of the types of IP is deliberately not conclusive, by explicitly excluding know-how from such definition (e.g. «[…] but in any case excluding know-how»).

 

  1. 1 Collins Dictionary: Know-how; tinyurl.com/8rmy9zr2.
  2. 2 Merriam-Webster Dictionary: Know-how; tinyurl.com/tdt8b9hx.
  3. 3 Law Insider: Know-how; tinyurl.com/4thwzt2h.
  4. 4 Commission Regulation (EU) No 316/2014 of 21.3.2014 on the application of Article 101(3) of the Treaty on the Functioning of the European Union to categories of technology transfer agreements.
  5. 5 Art. 162 Swiss Criminal Code (SR 311.0); Art. 4(1)(c) and art. 6 Swiss Unfair Competition Act (SR 241).
  6. 6 Dirk Scherp, Davide Rauhe, Datenklau!? – Entwurf eines Gesetzes zum Schutz von Geschäftsgeheimnissen – Teil 1, CB 2019, S. 21; with reference to Köhler/Bornkamm/Feddersen/Köhler, UWG, 36. Aufl. 2018, § 17 Rn. 6; OLG Karlsruhe WRP 2016, 751, § 17 Rn. 4b.