Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make a plan about combining all vocabularies from all partners into the MatVoc ontology #1

Open
TBoonX opened this issue Nov 2, 2020 · 2 comments
Labels
important WP1.3 Iterative, community-getriebene Ontologiemodellierung und Validierung​ WP1.4 Ontologie-basierte Repräsentation von experimentellen und Simulationsdaten
Milestone

Comments

@TBoonX
Copy link
Member

TBoonX commented Nov 2, 2020

Every partner is creating their own vocabularies which should be part of the MatVoc ontology. We need a process in which everything comes together and could be published and used at the end.

@TBoonX TBoonX added WP1.3 Iterative, community-getriebene Ontologiemodellierung und Validierung​ important labels Nov 2, 2020
@TBoonX TBoonX added the WP1.4 Ontologie-basierte Repräsentation von experimentellen und Simulationsdaten label Dec 4, 2020
@TBoonX
Copy link
Member Author

TBoonX commented Dec 8, 2020

My idea is the following:
Because each partner is developing their vocabularies on their own, we could create one folder per partner in the git repository. In there each partner works on their own files. Files which should be included into the ontology should be saved as n-triple files.
The CI will then concatenate theses files into one and save: the diff of the whole n-triple file(between old and new version) and the complete turtle file.
After this the CI runs our scripts and tools on the main turtle file. (RDFUnit, OOPS, Reasoner, ...)
With this we would have one turtle file which helps us using tools like VoCol, we would have with the diff the possibility to see what changed, we would have the possibility to use our CI and we would have more possibilities like detecting namespace duplication.

This would be the automatic part of the solution. The work on concepts/details of the ontology could only be happen together manually on VoCol (with the tools in there like WebVOWL).

@TBoonX TBoonX added this to the 2022.01.31 milestone Feb 9, 2021
@TBoonX
Copy link
Member Author

TBoonX commented Apr 26, 2022

Vacobularies created based on MatVoc should not be combined with MatVoc, instead a standalone CI, documentation and publication is needed.
The main plan could be found in https://docs.google.com/document/d/1cwoVhiDBEk3HedUKh5AHS6Hdh_a0h236DuD3P2Pwa9s/edit#
Differenciation is done with the path. E.g. MSLE under stream-ontology.com/MSLE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
important WP1.3 Iterative, community-getriebene Ontologiemodellierung und Validierung​ WP1.4 Ontologie-basierte Repräsentation von experimentellen und Simulationsdaten
Projects
None yet
Development

No branches or pull requests

1 participant