Skip to content
GitLab

Self-Assessment of Open Source Hardware

  • Discussion
  • Documentation

Components used during the assessment can be standard components (e.g. with ISO standards), proprietary components (e.g. available as purchase) or Open Source Hardware.

Requirements of proprietary components PROPOSAL!

  • Dimensions of the components have to be given
  • The component is purchasable and offered for international shipping

Requirements of Open Source Hardware

There are two ways to qualify as Open Source Hardware according to DIN SPEC 3105.

1. Community based assessment PROPOSAL!

  • Project is assessed according to the process given in DIN SPEC 3105-2
  • A Community Assessment Body (CAB) confirms the confirmity according the the DIN SPEC 3105-1
  • If a complaint is reaching the CAB the confirmity has to be verified again and can be revoked

2. Self assessment PROPOSAL!

  • The author of the project officially declares the project as
  • This declaration has to be published at the project repository

Embedding Self-assessed Open Source Hardware

If self assessed Open Source Hardware (here: component) is embedded in an Open Source Hardware project that is undergoing assessment (here: main project), the self-assessment for the component can be trusted. However, if - again - a complaint is reaching the CAB that is responsible for the confirmity of the main project, the self-assessment for the component can be rejected and thus has to qualify either as proprietary component (e.g. by being purchasable) or be re-assessed as Open Source Hardware.

Edited by Nils Weiher