by Jürgen Neumann at Raum Schiff Erde 2011.
The Open Hardware and Design Alliance (OHANDA) is an approach to label Open Source Hardware to make it visible as a commons shared resource. The proposed solution with OHANDA is a label in the sense of a trademark. The label will allow the developer to connect a copyleft license with any kind of physical device through OHANDA. Ready to register?
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
OHANDA @RSE11
1. Why OSH
=> without knowing the bricks ...
... we can not play with them!
• open documentation and open design are key to open source
• OSH is a common approach to unleash innovation and creativity
• OSH needs lincenses for clear rules of cooperation and copying
3. OHANDA (Open Hardware and Design Alliance) is an initiative to foster
sustainable sharing of open hardware and design. It was started at the
GOSH!-Grounding Open Source Hardware summit at the Banff Centre in July
2009 and one of the first goals of the project is to build a service for open
hardware design which includes a certification model and a registration.
Ohanda is in process, the process is open.
4. Adaptation of freedoms from Free Software Definitions:
Freedom 0.
The freedom to use the device for any purpose
(The freedom to run the program for any purpose)
Freedom 1.
The freedom to study how the device works and change it to make it to
do what you wish. Access to the complete design is precondition to this.
(The freedom to study how the program works, and change it to make it to do what you wish.
Access to the source code is precondition to this)
Freedom 2.
Redistribute the device and/or design (remanufacture)
(The freedom to redistribute copies to help your neighbourgs)
Freedom 3.
The freedom to improve the device and/or design, and release your
improvements (and modified versions in general) to the public, so that
the whole community benefits. Access to the complete design is
precondition to this.
(The freedom to improve the program and, and release your improvements (and modified
versions in general) to the public, so that the whole community benefits. Access to the source
code is a precondition to this.
5. Why can't we just use any copyleft license? In short: copyleft is legally based on copyright, which can not be used in
the physical world. The equivalent would be patents, but patenting hardware to make it open is too time consuming,
complicated and expensive.
6. The solution is a trademark. The trademark will allow the designer to connect a copyleft license with any kind of
physical device through Ohanda.
8. designer device / prototype
individual / group
design artifacts (files)
copyleft license
1. The designer applies the copyleft license to the product designs and documentation.
9. designer
individual / group device / prototype
design artifacts (files)
copyleft license
ID: FFFF ohanda.org
OK
2. The designer registers in (as a person or as an organisation) and gets an unique developer ID. By registering at
Ohanda, the designer accepts the terms and conditions to use the trademark by granting the 4 freedoms to the user
and publishing the work under a copyleft license.
10. designer
ID: FFFF device / prototype
OKEY: FFFF-0001 ohanda.org
3. The designer will then register the product and receive a unique product ID. After doing so, the designer may
apply the trademark to the product.
11. designer product description user
individual / group consumer
ohanda.org
OKEY: FFFF-0001
design artifacts (files)
copyleft license
4. With the unique Ohanda key on the product the user will be linked back to the designer, the product description,
design artifacts and the copyleft license through the web based service offered by Ohanda.
12. designer product description user
individual / group consumer & producer
ohanda.org
5. Empowered by the freedoms, user may develop the product further, register in as producer, share his/her design
artifacts applied with copyleft license and be connected to the derivatives of the product.
13. The service could be based on existing webservices like DNS in order to keep the system light and distributed.
14. The trademark and registration key is printed / engraved on each copy of the device so the link to the documentation
and to the contributors travels with the physical device itself.
15. Who will own the trademark?
• existing, trusted & organisation like CC / FSF
• new organisation to be founded
• “share” / registrant = distributing ownership gradually
16. Next steps: Setting up a legal not-for profit entity for Ohanda and raising funds for registering the trademark.
17. RAVI GISLE SUSAN JON CHRIS BENGT TUOMO JÜRGEN DANIEL JESSICA BRIAN ALEX
19. To: ohanda <ohanda@piksel.no> REGISTRATION
(1) I hereby accept the terms and conditions for applying the OHANDA label to
all hardware/devices I will register with the OHANDA by granting the 4 Freedoms
(http://www.ohanda.org/index.php/4_Freedoms) to the user and I appreciate all efforts
to make my registered hardware become completely held in commons.
(2) I will publish the complete designs and documentation publicly on the Internet under a license that
complies with the Open Knowledge Definition (http://www.opendefinition.org/okd/) or the Open Source
Hardware Definition (http://freedomdefined.org/OSHW) or put them in the public domain
(http://en.wikipedia.org/wiki/Public_domain).
(3) I will publish any software that is required for using my hardware publicly on the Internet under a
license that complies with the Open Source Definition (http://opensource.org/docs/osd) or put it in the
public domain (http://en.wikipedia.org/wiki/Public_domain).
(4) I will provide the first product I will register with OHANDA registration service within a period of
1 month starting from today. This will include the weblink to the complete designs and documentation.
(5) I will print/engrave the OHANDA label and the OHANDA Registration Key (OKEY) on every physical
copy of my design starting latest 3 month after the confirmation of this registration.
place, date
Full Name
Organisation
Full Address
ZIP City Country
24. OPEN SOURCE HARDWARE AND DESIGN ALLIANCE
WIKI | MAILINGLIST | ACCOUNT | LOG OUT
ABOUT PRODUCTS BLOG CREDITS
4x
in brief | freedoms | category | category
USE, MAKE, LEARN, SELL, CHANGE, COPY,
MANUFACTURE, MASS-PRODUCE, IMPROVE,
DOWNGRADE, UPGRADE, REDISTRIBUTE,
DO ABSOLUTELY WHAT EVER YOU WANT.
FREEDOMS
= UNLIMITED & UNCONDITIONAL
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean pharetra rutrum augue vitae gravida. In hac habitasse platea dictumst.
Sed risus odio, tincidunt id tristique id, dapibus a lacus. Sed nisi mauris, fringilla ut viverra vel, tincidunt sit amet nisi. Vestibulum iaculis
nulla vitae ante cursus quis commodo purus sagittis. Praesent dignissim vehicula ipsum, quis consectetur nisi posuere vitae. Donec
molestie est dictum erat faucibus ac rutrum mauris vestibulum. Vestibulum lorem nulla, varius nec mollis at, condimentum vel neque.
Etiam vitae elementum quam. Nullam eu risus mi. Mauris non vehicula dui. Praesent venenatis odio non tellus feugiat mattis id sit amet
25. OPEN SOURCE HARDWARE AND DESIGN ALLIANCE
WIKI | MAILINGLIST | ACCOUNT | LOG OUT
ABOUT PRODUCTS BLOG CREDITS
| product | producer | organisation | OKEY | registration date | status
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress
MiniSix microcontroller Adam Whiton MIT Media Lab 0001-0001 2010-11-18 in progress