Startup Legal and IP

© 2014, iText Group NV, iText Software Corp., iText Software BVBA© 2014, iText Group NV, iText Software Corp., iText Software BVBA
Startup Legal and IP
Founder Institute, January 5, 2015

Intellectual Property
Copyright versus Copyleft
Reviewing the IP of your product

© 2014, iText Group NV, iText Software Corp., iText Software BVBA
Copyright versus Copyleft
Copyright law allows an author to prohibit
others from reproducing, adapting, or
distributing copies of the author's work.
Copyleft gives every person who receives a
copy of a work permission to reproduce, adapt
or distribute the work as long as any resulting
copies or adaptations are also bound by the
same copyleft licensing scheme.
Founder Institute: Startup Legal and IP3
©
©

Friends, foes, and food
A permissive license makes most people see you as lunch,
A proprietary license makes most people see you as an enemy,
A copyleft license makes most people your ally.
Quote: http://zguide.zeromq.org/page:all#header-136

What is distribution?
Suppose that iText was an engine and the application using iText was a car or a bus:
License: MPL / LGPL GPL AGPL
Car distribution
(e.g. OEM)
Commercial use? OK for gratis commercial use Commercial license needed Commercial license needed
Bus service
(e.g. SaaS)
Commercial use? OK for gratis commercial use OK for gratis commercial use Commercial license needed
Free/Proprietary Before iText 5:
Improvements engine: LGPL
Car or bus: can be proprietary
Car: must be GPL
Bus: can be proprietary
Since iText 5:
Car or bus: must be AGPL
Or: buy commercial license

The iText case
Consent of owners is needed to change license
Who wrote iText?
Started by one person in 1998
Another developer joined in 2000
From then on organic growth of the product: different contributors
iText is MPL/LGPL, but
Who is the owner of the code?
Who owns the intellectual property of the code?

The situation before 2006
White zone
Gray zone
Black zone

The White Zone
White zone
Gray zone
Black zone

The White Zone
You have written the code yourself, but
What about your employer? Does your employer own (part of) the code?
Do you have a formal agreement with your employer with respect to
F/OSS?
Where did you get your inspiration? IBM developers are forbidden to look
at any code that is not formally approved by IBM’s legal team. Good
practice or burden?

Employees and IP

The Gray Zone
White zone
Gray zone
Black zone

The Gray Zone
The code was contributed, but
did the contributor agree with the license?
did the contributor’s employer agree?
where did the contributor get his inspiration?
The code is taken from another project, but
are the licenses compatible?
do you respect the other project’s license?
where did the other project get its code from?

The Gray Zone
Contributor License Agreements
The Apache Foundation demands contributors and their employers to
sign a CLA
SUN used to demand contributors to sign an SCA from the moment
contributions contained more than 20 lines of code
Check License Compatibility
Keep a detailed inventory of all F/OSS projects (subset / derivative work)

License compatibility
Your product: MPL
GPL
Your product: MPL
ASL

The Black Zone
White zone
Gray zone
Black zone

The Black Zone
Unfortunately, it may happen that you weren’t
allowed to use some specific code that is now part
of your project.
Possible solutions:
 Either you ask (and get!) permission, or
 You rewrite the code, or
 You remove the code.

Who owns iText?
First PDF library written in 1998
Completely refactored in 2000
Many people contributed, and IANAL

IP Project
July 2006: Eclipse Simultaneous Release
“Callisto”; tested and approved by IBM
Eclipse/BIRT (Actuate) is part of this release
Project led by Actuate
iText is used in Eclipse/BIRT
License MPL/LGPL: not acceptable for IBM
Research agreement between Actuate and Ghent University
with as deliverable: IP Review

Turning Gray and Black into White
White zone
Gray zone
Black zone

The process
Source code was vetted by lawyers
Source code was screened using software
Weekly reports listing potential issues

Example 1: Quick&Dirty XML parser
State machine to parse XML quickly
Source code taken from/inspired by:
http://www.javaworld.com/javaworld/javatips/jw-javatip128.html
Read the fine-print!
All contents of JavaWorld, including text, programs, applets, source code,
and images are copyrighted and owned by IDG or the copyright holder
specified, all rights reserved. No material may be reproduced
electronically or in print without written permission.

JavaWorld article + Fine-print

Solution
Write JavaWorld and author, get permission!
There were many other places where license
information was incomplete or missing.
It must become your second nature to ask
for permission and to document! document!
document!

Example 2: RC4 encryption algorithm
Names and variables referring to RC4
RC4 was initially a trade secret, but in September 1994 a description of it
was anonymously posted to the Cypherpunks mailing list.
It was soon posted on the sci.crypt newsgroup, and from there to many
sites on the Internet. Because the algorithm is known, it is no longer a
trade secret.
The name "RC4" is trademarked, however. The current status seems to be
that "unofficial" implementations are legal, but cannot use the RC4 name.

Solution
RC4 is often referred to as "ARCFOUR" or
"ARC4" (meaning Alleged RC4, because RSA
has never officially released the algorithm), to
avoid possible trademark problems.
Change all class and variable names:
 Don’t use: RC4_ENCRYPTION
 Use: ARCFOUR_ENCRYPTION

Example 3: Class IntHashtable
Code take from ACME.com:
// This is 90% based on JavaSoft's java.util.Hashtable.
// Visit the ACME Labs Java page for up-to-date versions
// of this and other fine Java utilities:
// http://www.acme.com/java/
JavaSoft is a name used by Sun in the past in their Java activities.
ACME indicates use of the class java.util.Hashtable which is subject to unfriendly
Sun license
It is unlikely that this code is available under a license that permits this use.
Without information indicating that Sun approved of this usage the class should
not be used.

Solution
Use the same class released by Apache under the ASL in
Apache-Commons instead of the ACME class.

IP Review: result
iText shipped with “Europa” simultaneous release
No more doubts about ownership iText
Transfer of IP to first iText company

Today: disciplined IP “book keeping”

Trademarks
Register your brand name
Register your logo

Unregistered vs Registered Trademark
You don’t need to register your trademark if you want to add
™ to your brand name.
Your brand name needs to be registered with the USPTO
before you can add ®
Registration isn’t always easy:
 “I TEXT” is descriptive: “I send an SMS”
 USPTO and BBIE could be convinced that iText was sufficiently distinctive
 OHIM didn’t agree (IMO, they were too lazy to read our arguments)
You can register your logo as a Trademark

Registered Trademark

Scam Alert!

Patents
Why companies use patents
To patent or not to patent?

Why write a patent?
To prevent others to copy your invention
To trade: “You can use mine if I can use yours”
To enforce a standard
To create value for your company

Use patent to enforce standards
http://partners.adobe.com/
public/developer/support/
topic_legal_notices.html
Most important words:
“compliant with the Specification”
ISO

Open Source versus patents
Open source is a means to prevent others to patent
You can not patent source code
You can patent software mechanisms

Questions?

Startup Legal and IP

More Related Content

Similar to Startup Legal and IP

More from Bruno Lowagie

Recently uploaded

Startup Legal and IP