oseg/osh-ont
oseg/osh-ont
6
3
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Activity Actions
Open Source Hardware Ontology - Defining a common vocabulary for the OSH community, both human- and machine-readable. - May we understand each other, automatically!
49 commits 1 branch 1 tag 565 KiB
Shell 100%
Find a file
Robin Vobruba 1d6f507888 tractor: Uses new w3id namespace
2024-07-12 15:42:13 +01:00
.reuse Switches to codeberg 2023-10-24 15:02:00 +02:00
LICENSES REUSE licensing info - partly generated with reuseify.sh 2023-10-18 14:11:03 +01:00
res/media/img Initial commit 2023-10-18 13:54:11 +01:00
run visualize: Splits output into build/ and public/ 2023-12-15 17:23:38 +01:00
src tractor: Uses new w3id namespace 2024-07-12 15:42:13 +01:00
.gitignore Git ignores /public/ 2023-12-15 17:21:35 +01:00
LICENSE.txt Adds "main" project license file 2023-10-18 14:12:52 +01:00
README.md Switches to codeberg 2023-10-24 15:02:00 +02:00

README.md

OSH Ontology

License: CC0-1.0 REUSE status

In cooperation with Open Source Ecology Germany In cooperation with ValueFlows

  • OSH: Open Source Hardware (Machines and other things that free the user of the domination and control by the producer)
  • Ontology: A way of showing the properties of a subject area and how they are related, by defining a set of terms and relational expressions that represent the entities in that subject area

Why

The idea is, to share a general linguistic (and therefore social/human) and machine-friendly structure, that allows humans, organizations, software and standards to speak common language in the field of OSH.

This hopefully leads to us communicating more precisely, with less misunderstanding. It may also lead to different software applications - independently developed from each other - in the field, to feel more similar to the user and developers, and potentially even for them to be technically compatible.

If standards and specifications in the field refer to this ontologies vocabulary, or even link to the RDF ontology, It will also make it easier for humans and software to understand them (correctly), and it might help in their credibility and adoption.

Scope

So far:

  • Designing & Documenting
  • Assembling
  • Using
  • Manufacturing (planned)

Hopefully in the future:

  • repairing
  • recycling

Technical details

The core of it all is our RDF ontology. Apart from that, we are focusing on manually crafted diagrams to explain the ontology to humans. For those, we also create some icons.

All of these can be found under the src/ directory, while the res/ directory contains 3rd-party sources, potentially modified a bit.

Who is doing this?

Starting in October 2023, it is:

We are looking for more contributors!