search

iop-alliance / OpenKnowHow

A metadata specification to enable the collection of distributed, standardised metadata of open source hardware designs
GNU General Public License v3.0
1 stars 1 forks source link

Sub-parts from v1 can not be converted into valid parts of v1-LOSH #26

Open hoijui opened 2 years ago

hoijui commented 2 years ago

... because v1-LOSH currently requires either source or export for an OKH Part, both of which can not be derived from v1.

hoijui commented 2 years ago

I think, v1 does it better then LOSH. In v1, a sub-thing (named Part in LOSH) is actually modular. In LOSH not really, because the meta-data of the Part is within the parent.

Why did we do it like this, @moedn?

moedn commented 2 years ago

sorry, not quite sure what you mean

  1. source/export for modules are not mandatory; there are many scenarios in which such requirement shouldn't be enforced, e.g. when a manufacturing instruction would suffice
  2. sub-things can be integrated via URL; one could just reference these parts if (for whatever reason) they are developed in another repo
hoijui commented 1 year ago

  1. The MD documentation states, that 'source' is mandatory for a Part. The RDF docu does generally not specify what is mandatory, so we can not refer to it. The JSON Schema states, that either source or export need to be defined for a Part.

    You are saying, these are both wrong, and I should change them, @moedn?

moedn commented 1 year ago

hmmm ja, sorry for the inconsistency among the specs… that's something that was bugging me all along the open_next project; I never had the time to fix that

so, from a practical standpoint, it should be mandatory to have either a source or an export file available for a part. of course it's better to have the source/native file (or both!), but without any of these, it's technically a blocker for replication: a part that is needed, but cannot be bought and there's no information on how to build it