Version 1.1 of the definition has been released. Please help updating it, contribute translations, and help us with the design of logos and buttons to identify free cultural works and licenses!
Editing Talk:OSHW
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 75: | Line 75: | ||
=== Design representation file formats === | === Design representation file formats === | ||
In the Open Manufacturing community, one of the ideas that has spawned is this concept of | In the Open Manufacturing community, one of the ideas that has spawned is this concept of focusing on STL/meshes/jpegs as kind of like "binary objects". Yes they are useful if you have the same machine that you compiled the object on, but they are not really design files in the sense that constructive solid geometry (CSG) or boundary representation (b-rep) CAD files are, like ISO 10303-21 (STEP) or IGES or the myriad of other formats. It's also interesting from a community education perspective, because a lot of people think that Google SKetchup is a CAD tool, and that Blender is a CAD tool (blendercad), when in reality the fundamental data representations are different. In my view, I would favor SVG or JPEG any day. I suspect that static image files are covered by Creative Commons licenses, and when we're talking about "modifications" to designs, that's like a diff applied to SVG or STEP. Right? Can we get a little more coherent in what we're talking about? :-) -- [http://heybryan.org/ Bryan] | ||
=== Human Readable vs Best Practices === | === Human Readable vs Best Practices === |