DAPSI leftover work

[hoijui]

1. (1w) Align Crawler-output and ontology/specification

2. (1w) Make modularity concept coherent
   with the common understanding in the maker-scene;
   specifically the wording of things like Part and Module.
   We would document it well for humans (and technically),

   • in text,
   • ontology, and with
   • a diagram;

   also taking into account things that are not in OKH
   but live in the same ball-park
   (like BoM items that are neither a Module nor a Part
   -> they need a name, and need to appear in the docu).
   See Modularity issues #11.

3. (4w) Tackle as many of the open issues from
   https://github.com/OPEN-NEXT/OKH-LOSH/issues
   as possible.

   • TRL - Documentation and Definitions of Open Documentation Readiness Levels (ODRL) #9
   • TRL - replace development-stage by TLR #74
   • misc - Reporting #90
   • ontology - US or UK spelling in the standard? #15
   • ontology - RDF: A property can not be a sub*Class*of anything #36
   • ontology - Tighter definition for links, document references & some other things #40
   • ontology - Standard for the language field(s) #41
   • ontology - ontology feedback v1 #66
   • ontology - Redefine field: outer-dimensions #10
   • ontology - Parts should have a BoM as well #12
   • ontology - forkOf exists in RDF, but not in the markdown spec #27
   • ontology - okh:repo - Web-View or git (clone) URL? #94
   • images - Image description/alt-text for people who can not see #43
   • images - Image type/description/category #35
   • images - what's the main picture when there are multiple pictures? #103
   • administration - register ontology at PURL and the internet archive #67
   • ...

[hoijui]

The modularity concept coherence effort is a huge success. It is already going for a year (with some pauses). It is a combined effort between Lyn Foster from https://valueflo.ws and me, and it will lead to much more then just improved modularity vocabulary.