You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
importantWP1.3Iterative, community-getriebene Ontologiemodellierung und ValidierungWP1.4Ontologie-basierte Repräsentation von experimentellen und Simulationsdaten
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.
The text was updated successfully, but these errors were encountered:
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).
importantWP1.3Iterative, community-getriebene Ontologiemodellierung und ValidierungWP1.4Ontologie-basierte Repräsentation von experimentellen und Simulationsdaten
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.
The text was updated successfully, but these errors were encountered: