Open hoijui opened 3 months ago
The following 4 topics we want to work in are from our NGI Search application. The sub-lists are potential software candidates. We will not be able to work on all of them:
ttl2pretty
- RDF/Turtleowl:Ontology
is present (NOE: or is there an other way? *.owl
is XML only))nt2pretty
- N-Triples is a very simple, text-based RDF serialization format that is efficient to parseowl2shacl
- SHACL can be used to validate RDF dataowl2jsonscm
- JSON-Schema can be used to validate JSON, YAML, TOML and similar formats, and to generate GUI forms to create and edit the data.owl2shacl
(yes, fits here too)owl2jsonscm
(yes, fits here too)owl2md
- Human-Readable only Markdown (can then be converted to HTML and PDF as well)Milestone | Date | Deliverable No. | Deliverable Name | Budget split |
---|---|---|---|---|
2 - Development of the MVP (TODO) | 2.1 | TODO | ||
2.2 | TODO | |||
2.3 | TODO | |||
End of March 2025 | Total: 75,000.00 | |||
3 - Completion of the Technology adoption Plan (TODO) | 3.1 | TODO | ||
3.2 | TODO | |||
3.3 | TODO | |||
End of June 2025 | Total: 45,000.00 |
NOTE: This is highly controversial and experimental, but practical to have in most scenarios where the ontology is mostly representing a kind of distributed DB Schema.
Still free - maybe some community testing and feedback?
Final milestones:
Development of the MVP and (if applicable) Business Plan
Due Date: End of March 2025
Responsible: Robin Vobruba (@hoijui)
Software that auto-checks these formats against best-practice. This should help mediate the huge issue of quality in the RDF world, by doing it automatically on each git commit to an ontology in CI.
Responsible: Robin Vobruba (@hoijui)
Maintains a LinkedData DB with meta-data about OSH projects hosted on different platforms, and will be hosted and maintained by OSEG.
Responsible: Robin Vobruba (@hoijui)
of the ones linked to in https://github.com/iop-alliance/OpenKnowHow/issues/146
7 OKH issues closed
Completion of the Technology Adoption Plan.
Date of Planned Delivery: End of June 2025
Responsible: Robin Vobruba (@hoijui)
A software that re-writes a turtle file to have minimal variance/diff between changes. This helps when different people work on the same RDF file in a repo, and/or different GUI tools are used to edit it, to not create a huge mess in the history.
Responsible: Timm Wille (@timmwille)
A web page backed by an OKH index server, that allows to easily search for OSH projects, and presents all meta-data in a palatable way. It also provides a good overview of the project ecosystem.
Responsible: Timm Wille (@timmwille)
Community targeted communication and efforts to scale the implementation and enable collaboration. Cross-Community posting and continuation strategy.
In July 2024, we applied for NGI Search funding. If we get accepted, this issue will serve as the organizing hub for the technical part of the proposal.
We selected these 19 initial issues as candidates to be solved within the funding period. We pledge to solve at least 7 of them.
Apart from these, which are all directly related to the standard, we will also work on related tooling:
owl2shacl
description
Converts an OWL ontology (e.g. the OKH standard specification) into SHACL, which can be used to check if hardware project data in the RDF format conforms to the standard, or to automatically generate web forms to enter and edit data in this format.[ ] develop current alpha to a first release; verified by producing meaningful results for these ontologies:
okh
okhmeta
vf
owllint
description
Checks an OWL ontology against best-practices, as defined partly by LOV in their documents: Ontology meta best practise & Ontology HTML version best practise & related paper. Or by us, in a document that will also be created.ttl2pretty
description
Pretty-prints RDF/Turtle files. This can be used both for the ontology as well as for the data. This is crucial for machine- and human optimized git diffs, to reduce merge conflicts, and for humans to find their way around faster within an RDF data file or ontology.owl2jsonscm
description
Converts an [OWL] ontology into [JSON-Schema], which can be used to check if hardware project data in TOML, JSON or YAML format conforms to the standard, or to automatically generate web forms to enter and edit data in this format.details
This will likely pose a big challenge, and might even prove to be overly complex to the ontology creator, to the point where it will be impractical. In that case, we would document our findings well, and close the case without further pursuing this. Consequently we would also have to re-consider the whole TOML & JSON & YAML secondary format idea.