Create and use a pattern language for parts

[hoijui]

This came up in the the Sensorica + OKH + ValueFlows hackathon today.

In order for us to (automatically) identify what kind of thing a Part/Module (in OKH terms) a thing is,
it could make sense to define a pattern-language (or ontology?),
which we could look for in file and directory names of a project.

The osh-tool could then look for these,
and give extra-points if such "tags"/patterns are used.

glocalvr: OSE US pattern language:
https://wiki.opensourceecology.org/wiki/Pattern_Language

Bob: ValueFlows started with a pattern that we talked about developing into a pattern language, but never did the whole language:
http://mikorizal.org/dependent_demand.pdf

kny5: We could use taxonomies from parametric design CAD tools*, like:
http://papers.cumincad.org/data/works/att/caadria2015_178.content.pdf
(and also extract them from CAD files?)

I know for Python there are bit walkers to get this info from proprietary binaries, we could process this files and get the metadata and store in a "modeling tags" file. idk.

• https://www.sciencedirect.com/science/article/abs/pii/S0010448505000412
• https://www.sciencedirect.com/science/article/abs/pii/S001044850400140X

* CAM == CAD tool limited to processes available in manufacturing

Note: This idea might overlap with TsDC. It defines what kind of hardware has to define what kind of meta-data, for example, a chair might have to define the maximum load it can bear, while a camera objective might need to define its focal length, but not vice-versa. TsDC is not yet well developed though. That might happen in 2023 (at least there are plans for that).

Decision- & Classification-Trees - Clearly Explained:
https://www.youtube.com/watch?v=_L39rN6gz7Y