Standardisation of Open Source Hardware
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Alternative Title |
| |
| Title of Series | ||
| Number of Parts | 254 | |
| Author | ||
| License | CC Attribution 4.0 International: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/52993 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
00:00
Computer hardwareOpen setGoodness of fitOpen sourceDescriptive statisticsComputer hardwareField (computer science)Standard deviationComputer animationLecture/Conference
00:26
Open sourceComputer hardwareMetadataVirtual machinePublic key certificateTerm (mathematics)Different (Kate Ryan album)Open sourceProgram slicingComputer hardwareAssociative propertyOpen setCalculationProcess (computing)Projective planeStandard deviationMechanism designPairwise comparisonBridging (networking)Point (geometry)Boiling pointCartesian coordinate systemState of matterCore dumpPeer-to-peerFrame problemSet (mathematics)Module (mathematics)Web 2.0Product (business)Goodness of fitNP-hardSign (mathematics)Forcing (mathematics)Field (computer science)QuicksortLie groupVideo gameCycle (graph theory)Shared memoryOffice suiteFreewareRepetitionBasis <Mathematik>Multiplication signComputer animation
05:25
SpeciesRepository (publishing)Computing platformSearch engine (computing)Google+Field (computer science)1 (number)Point (geometry)WikiYouTubePublic key certificateProcess (computing)Context awarenessAreaStandard deviationComputer hardwarePeer-to-peerRepository (publishing)Open setView (database)WebsiteStatisticsSpeech synthesisReal numberClosed setComputer animation
07:02
FeedbackComputer hardwareStandard deviationOpen sourceResultantReal numberComplex numberRevision controlLevel (video gaming)Public key certificateForestObservational studyAreaComputer animation
07:58
Open sourceLogical constantRepository (publishing)1 (number)MereologyData managementPhysical systemProduct (business)FamilyVideo gameComputer-assisted translationPublic key certificateCalculationCycle (graph theory)Standard deviationComputer animationLecture/Conference
09:10
Repository (publishing)Data managementComputer hardwareProjective planeStandard deviationOpen sourcePublic key certificateModule (mathematics)Arithmetic progressionProduct (business)Factory (trading post)MereologyModul <Datentyp>Computing platformProcess (computing)WikiNP-hardEndliche ModelltheorieArithmetic meanComputer animation
09:52
1 (number)Level (video gaming)Open sourceType theorySineComputer hardwareSoftwarePublic key certificateTerm (mathematics)Dean numberForm (programming)Procedural programmingLatent heatObservational studyDifferent (Kate Ryan album)State of matterField (computer science)Graphics tabletFreewareRepository (publishing)Slide ruleTap (transformer)Computer animation
12:19
Task (computing)ConcentricPublic key certificateSelf-organizationDifferent (Kate Ryan album)Process (computing)Procedural programmingPower (physics)Open sourceKey (cryptography)Exception handlingPeer-to-peerComputer animation
13:43
Product (business)File formatDirection (geometry)Latent heatPublic key certificateOpen sourceOpen setShared memoryComputer fileQuicksortLecture/Conference
14:42
Open setSolid geometryFile formatStandard deviationFreewareInformationComputer-assisted translationGeometryComputer programmingComputer fileEndliche ModelltheorieNetwork topologyForm (programming)Lecture/Conference
15:57
ResultantBuildingWeb pageDean numberStandard deviationWhiteboardPublic key certificateControl flowIntegrated development environmentOffice suiteHydraulic motorWritingVirtual machineRevision controlCartesian coordinate systemOpen setPrototypeGoodness of fitComputer hardwareProjective planeStreaming mediaSelf-organizationOpen sourceMereologySubsetDataflowMultiplication signCycle (graph theory)Software testingSoftware developerFeedbackCASE <Informatik>Process (computing)Shift operatorCore dumpStructural loadSoftwareField (computer science)AuthorizationSineProduct (business)FirmwareType theoryTerm (mathematics)Business modelEnterprise architectureOnline helpPasswordHypermediaQuicksortBus (computing)System callSocial classAdditionObservational studyFreewareWordArithmetic meanSound effectPlastikkarteReading (process)Computer animation
24:18
Beta functionFeedbackOpen setComputer hardwareNP-hardContent (media)Revision controlCurve fittingOpen sourceBeat (acoustics)DampingComputer fileMultiplication signVideoconferencingComputer animation
25:02
Computer animation
Transcript: English(auto-generated)
00:05
Okay, good afternoon everybody standardization of open source hardware As I described well as I wrote it in my description. I won't gonna I won't tell you about how Great open source hardware is but I'm because I assume you all know that
00:23
but for those new in the field Open source hardware is not about giving away machines for free, but it's about the question who owns technology and as Hardware or other technology is how we would use our daily production
00:42
goods or living goods and also the base of circular economy I assume that's a super important question at least for us, so we start with the term and The term has been defined by some guys in the US by the open source hardware Association
01:02
That came out with the definition that opens as hardware is hardware whose design is made publicly Available so that anyone can study Modify distribute make and sell the design or hardware based on that design. So basically you upload the design files
01:21
Blueprints and all these calculations and stuff like that and then anyone can build machines with that and yeah So this is followed by a lot of license terms So what oshba did is? Defining what open in open source hardware means while hardware is rather clear It remains open what the source actually is
01:43
So it is not enough to just share The quick sketch of your machine Nobody can work with that. So what should actually be shared at an open license? So others are enabled to modify Redistribute and whatever your hardware so it's also a question about the purpose of the source
02:03
What are people meant to do with it? And this purpose has been already defined by oshba open source initiative and they boil down to these Four core points so people should been able to study modify make and distribute the hardware
02:21
Well, we put that in an official standard Which is then the frame for the technical documentation of the hardware because that's what you share in the end That's also the first official standard for open source Anywhere, so and that's then that we also acknowledge that this technical documentation depends on the lifecycle
02:43
Phases that you are trying to cover so not only Introducing the hardware to the world but also to maintain and operate it and to recycle refurbish Whatever so you need more documentation and we also include The point that the technical documentation depends on the technology
03:04
embedded in The piece of hardware and also that is used to produce the piece of hardware You will need a different doctor technical documentation for a 3d printed cup of tea without the tea Or when you want to share a machine that produces cheese and slices and packages it
03:25
So yeah, that's all nice. But why do we actually need a standard for that? Can't people just produce and document open source hardware so First of all, the standard defines what you should share and apparently that's a huge issue
03:41
There's very few Projects out there which are very good documented at least for mechanical open-source hardware so you're also Despite from enabling people to make use of your invention you make technical documentation
04:00
compatible and comparable to each other so When we have two awesome machines documented well, and you can actually make use of both technical documentations You can combine both to better machine if you like and Second point you can actually find it. There's no use if you just publish a lot of
04:22
Open-source modules around the web if no one can actually find them then you need to really when we invent the real Every time again, so the standard defines a common set of metadata. So others can actually find your hardware and As it's an official standard We can put a trusty and community-based
04:42
Certificate on that and this is meant to build a bridge between community industry and research institutes as apparently industry and science needs paper and certificates and by that process It doesn't really matter who comes up with the invention first and who uses it in the end so all
05:05
can effectively work together The certification process has also been defined by the standard. Here's how it works. So you start with the documentation release Then you make an application and then people can peer review
05:22
your technical documentation just as in science and when the peer reviews state that this is complete and Readable for others in the field then you will have the certificate which may look like that and as the certificate is based on peer reviews, it's updatable and
05:41
Challengeable, so it's not a certificate just for your lifetime Whenever someone else comes up with a negative peer review and they exceed the positive ones then it aspires and This process is moderated by a certification body who can just be anyone who is capable to
06:02
Organize a repository which cape keeps all these documents open and transparent Yeah so That's how it works in practice or that's the context of the documents the technique documentation is in the middle both standards define
06:21
How it is made and how it is certified and there's a third document that I didn't mention yet There's a guideline that helps you to make this technical documentation in the end it also helps you in other points like legal issues around opens as hardware patent law issues and a lot of stuff like that and on the other side
06:42
Talking and technical documentation is uploaded somewhere. So people usually upload it on github thinking verse wiki fob, whatever they're Alone in the english-speaking area. We have over 80 different platforms and We Developed a search engine that quads
07:00
These platforms plus Google plus YouTube and then you can actually find what's out there And the aim is to make it filterable by the certificate So when you search something you can filter the results for what is actual real Open-source hardware and what is more DIY?
07:21
stuff The nice thing about this map It's all open source Even the standard which was a lot of lobby work, but you can yeah participate in the in the standard and give feedback and then doing pull requests and other stuff and then the National Standardization Institute in Germany needs to look at it and
07:46
Make you that and for for the next version of this tunnel Yeah That Was maybe a bit fast, but I wanted to keep it as as Rough as possible as it's a complex field and usually
08:03
It's it's better to have a larger Q&A part about that. Feel free to ask me any questions about that Yeah, especially the uncomfortable ones are like those Yeah, and then we can dig into the details My question is regarding the repository is it kind of a product lifecycle management system or is it like
08:45
basically good where you upload a bunch of like you have a folder and you upload your cat files your calculations everything or is it something where you can dynamically Like pull out the data and say like half an assembly I have a bunch of standard parts which coming from like a shared library and like you can all mix it up together
09:04
Um this repository This repository is not meant to store the actual technical documentation But just all the documents involved in the certification process how people organize the technical documentation if they refer to other standardized parts
09:23
is Yet their issue But as I say that would make a lot more sense if we keep this hardware modular So if there's a repository of standardized modules and people can look at it and then yeah So there's currently no platform that is capable of like
09:42
Resembling an open source product lifecycle management. I mean, well, there is one in progress Wiki factory is trying to do that But it's yet a research project so it's not yet usable. Okay. Thank you
10:02
Many things for a talk first of all, it's very interesting that you really got it That Dean makes something really open source even the specification. So Congrats for this especially the other question The other thing I would like to ask is in the open source software you have tons of different license types and
10:26
This is only one license type So for example in you have GPL or you have BSD or whatever you you think of in open source software What's the license type when you are talking about open source hardware here? So
10:42
For open source hardware, there's not so that are so many Licenses out there yet. There are three major ones which is Sam OHL the yeah most common one and the best Maintained the TAP our license and the solder pad and
11:01
They basically split up into with copy left mechanism or without and that's it yet So it's a free field but OSHRA is Pretty open to that so they only define the license terms anyone can come up with a new license according which is Conformative to that. Yeah
11:23
No, I have a question about the slide here the certification body who is this This can be anyone So it could be you if you're capable to hold such a repository. I
11:44
Mean, it's the standard defines How this certification body needs to be organized what he needs to do, but in the end Yeah, anyone can do that you just need a state when you give out the certificate who you are so who issued that certificate and then
12:03
Yeah, even people can trust you or not And there's also a specification for that Yeah, we have two documents here, so Yeah, I didn't mention that Particularly the standard splits up into the definition for the technical documentation and into the definition for the certification procedure
12:27
so Here it's described how this procedure works and the certification body has clear roles and tasks to ensure That is working but again
12:40
Any anyone can just declare he's working? in Yeah in compliance of that standard And That's actually how certification works in industry too. You can be an institute someone is reviewing you and say it's okay. You can compliant to that standard
13:00
The difference here is that we don't have a power concentration here. So whenever the certification body Becomes corrupt. So for example, my organization opens as a college Germany wants to found such a certification body Yet there's no money involved so it's unlikely that we have become corrupt in in some sense, but when money
13:24
becomes a thing There is a risk for that so but as all the documentation and the whole process is open people can just fork us so When they find out that we that we accept Peer reviews from your friends, for example that you call a few colleagues and then you say this is open source
13:45
and Yeah Whatever. So is that we have some some corruption happening there and then you can just Clone the whole thing Yeah, and open your own certification body
14:08
Yeah, hey, thanks for the talk. I was wondering about the specifications on how to share your product data your technical documentation so for example
14:22
How is one supposed to share 3d 3d data are there specific file formats or Yeah, so essentially I think that the open source world is pretty lacking in that regard for example And I wonder if there's some direction given there there is
14:44
Um Especially regarding see these files. We are not yet ready to only use free cat or open scat for example So these programs are not ready for industrial use So what we say in the standard is you need to share the original file format
15:00
But you also need to make the information available In a way that people can look into this information without any licenses So you have your CD file and maybe people can look not look into the CD file, but you should share a Drawing as a PDF or whatever. So then people can look into the
15:24
geometry and tolerances on the other so the actual information is publicly available, but the CD model May be only available if you have a soldier of whatever Solid works license or stuff like that. So we give recommendations
15:42
But we cannot enforce it yet because for most companies, that's just unrealistic Yeah, if there's no more questions yet. Yeah There's
16:09
Even though it is not applicable anymore because it's a challenge or something. Oh, that's a good question Yeah, I got this ask a lot. What's the actual use of the certificate so we can
16:22
Talk a lot about how well you build this can be for industry But there's no one applying that who is supplying that is science in science for research project, it's Probably that you will construct any kind of prototype to test something and as it's financed in advance
16:44
You you don't need a business model behind that you can just build your prototype, but it's usually not documented So it stays in the laboratory and nobody will ever know about that and plus people usually cannot reproduce your Test results or all the data that you
17:02
That you produce with this prototype or testing environment because nobody knew knows how how you build the machine but if there's a standard and if there's a certificate it's Clear what could be documented and could be part of your research project?
17:20
So people can put this into the application for research project. It becomes part of it they get money for the documentation and time for that and So we have all this high-tech research stuff openly documented and we also win a Revenue stream like money flow for this whole open source hardware field
17:45
That was the but that's the first application case. We are also working together with a bunch of media sized enterprises which are interested in that They're looking more for a label or something, but They can also apply for public money and whenever you apply for public money your results should be publicly available. So
18:08
Certificate again, it all works with paper And it's a huge Authority as it's been these three letters make a lot
18:21
Thanks for your presentation. I'm drew from one of the board members Yeah, I was told about you from the libre solar a few days ago over here Yes, and Matthias is also here. He's also one of the board members So I think this is really exciting what you're doing And I'd like to talk more about how I wasn't familiar with thin before this but there's other standards organizations like ANSI and ISO in
18:44
The US and I'm thinking maybe this would be applicable to those things as well potentially Have you looked at other countries how how this process could work there? Yes There haven't been so open yet for that the Austrian National Standardization Institute
19:02
Was kind of interested but they didn't support us so well and Dean has much more Authority in the international sector. So this Dean spec is directly transformable into international standard but it's under CC bias a so
19:21
Whoever wants to publish this standard could be ANSI could be whoever I saw sin They need to publish it on the CC base a Yeah so Something like ISO is similar to din then in terms of a standards body is on the ISO
19:41
Is that kind of similar to what din that din does or? yes, it's It's actually the same building. So Inside the Dean building you have yeah The first office is the national standardization and if you walk down the corridor, there's the international sector
20:01
So just pass on the paper Thank you Well what I could do meanwhile is showing you the open hardware observatory which I mentioned so Should I ask my question now or sure you can if not, I
20:24
Ask the question already in industry Documentation is quite a problem because people are generally too lazy to do it. Do you think that in? Open-source hardware will find acceptance in a lot of cases or depends what you want to do
20:40
In the hardware sector support is a huge problem. So in a few weeks ago, I read Who was that actually didn't see who was talking out here. Okay, because I want to look at you the few weeks ago, I read an article about them garden robot er, and that was a relatively small company that wanted to provide 10 years support for their products, but
21:05
coming out with a new Version of their product every year. So that becomes a huge cost for this company and they couldn't It could simply not provide such a load of work for the support
21:21
But what they did in the end was open sourcing the firmware and some parts of the design So the community can take care of that. So people have the effective Ability to to maintain their product and also to modify it and you ask for help
21:41
Without costing this anything the company So some are starting with that Another example is sort of motors. I don't know if you heard of them that they're Developing an electric car in yeah in Munich And they want this car to be fully maintainable by anyone. So they want also develop
22:04
Yeah an instruction how to maintain this car They could do them that themselves and invest a lot of money in the actual writing of the manual but they could also just Write the first part and let the rest for the community
22:20
So the people that repair the car write the manual themselves by that they get a unique Thing out there in the market. There's no car that you can maintain by yourself in all the details yeah, at least in the electric sector and They also get free feedback. So they see
22:41
See that piece that always breaks when I do this and that or it's hard to repair so all these Development cycles that cost a lot of money are free then you're outsourcing things So I assume that there will be free few companies that will open source just everything but a few parts of it, I guess yes and
23:05
five years ago that wasn't Some kind of impossible thing to pitch to two companies to open source your your development but right now, I don't know what changed but Everyone I'm talking to is like well, let's make a pilot about that. How can I collaborate with you?
23:24
So there is a mind shift and I didn't question that yet So deeply as I didn't want these people to change their mind same for Dean because what we're doing is undermining Dean's Business model their core business model and I don't know if all of them understood that
23:41
But well, they are super motivated in that There's a they're actually looking for an open source software project with a standardization of motivations That they could support So if there's any out there come to me and I can link you but I'm talking too much any any more questions
24:01
Well, if not We could Yeah, what's that I could show you all hold on That's this so That's a web page. We could just type in any kind of technology any password out there anything you want to do
24:25
like We Turbine and then Yeah Then it shows you what's out there Yeah, and then you click on it and then you come to the
24:42
To the actual design files. So there's no need to invent anything from scratch. There's For almost all technologies. There's always some dude out there who did it and Made at least a video about that Your this mid time up yet. Okay, so yeah, thanks for listening