Open Licensing—Advanced Sharing - Open-Source Lab: How to Build Your Own Hardware and Reduce Research Costs - page 42

ware's source, the design from which it is made, is available in the preferred format for making
modiications to it. Ideally, open source hardware uses readily-available components and materi-
als, standard processes, open infrastructure, unrestricted content, and open-source design tools to
maximize the ability of individuals to make and use hardware. Open source hardware gives people
the freedom to control their technology while sharing knowledge and encouraging commerce
through the open exchange of designs [ 22 ] .
3.4.2 Open-source hardware definition 1.0
The OSHW definition 1.0 is based on the open-source definition for open-source software. That
definition was created by Bruce Perens and the Debian developers as the Debian Free Software
Guidelines.
Introduction
OSHW is a term for tangible artifacts—machines, devices, or other physical things—whose
design has been released to the public in such a way that anyone can make, modify, distribute,
and use those things. This definition is intended to help provide guidelines for the develop-
ment and evaluation of licenses for OSHW.
Hardware is diferent from software in that physical resources must always be commited
for the creation of physical goods. Accordingly, persons or companies producing items
(“products”) under an OSHW license have an obligation to make it clear that such products
are not manufactured, sold, warranted, or otherwise sanctioned by the original designer and
also not to make use of any trademarks owned by the original designer.
The distribution terms of OSHW must comply with the following criteria:
1. Documentation
The hardware must be released with documentation including design files, and must allow
modiication and distribution of the design files. Where documentation is not furnished with
the physical product, there must be a well-publicized means of obtaining this documenta-
tion for no more than a reasonable reproduction cost, preferably downloading via the Internet
without charge. The documentation must include design files in the preferred format for mak-
ing changes, for example, the native file format of a CAD program. Deliberately obfuscated
design files are not allowed. Intermediate forms analogous to compiled computer code—such
as printer-ready copper artwork from a CAD program—are not allowed as substitutes. The
license may require that the design files are provided in fully documented open format(s).
2. Scope
The documentation for the hardware must clearly specify what portion of the design, if not
all, is being released under the license.
3. Necessary software
If the licensed design requires software, embedded or otherwise, to operate properly and
fulfill its essential functions, then the license may require that one of the following conditions
are met: (1) The interfaces are sufficiently documented such that it could reasonably be con-
sidered straightforward to write open-source software that allows the device to operate prop-
erly and fulfill its essential functions. For example, this may include the use of detailed signal
timing diagrams or pseudocode to clearly illustrate the interface in operation. (2) The neces-
sary software is released under an OSI-approved open-source license.
4. Derived works