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

Join multiple knowledgegraphs #48

Open
joergfunger opened this issue Sep 1, 2022 · 2 comments
Open

Join multiple knowledgegraphs #48

joergfunger opened this issue Sep 1, 2022 · 2 comments
Assignees

Comments

@joergfunger
Copy link
Member

In the minimum working example, we generate a separate KG for each test. This mimics the situation of another test being performed which is supposed to be added to the large (single) KG. Before adding, a shacl validation is performed. Currently, this building of a joint knowledge graph is not done. Apart from building this global KG, the querries should also be reformulated (because they do not work for multiple data sets) and require e.g. to get the diameter, length, .. of a specimen for all tensile tests performed.

@PoNeYvIf
Copy link
Collaborator

PoNeYvIf commented Sep 5, 2022

I will start working on that this week. However I was wondering what a shacl validation is performed. Is there a tool that I can use for that? Is there a documentation about this tool? Also before merging all the KGs together I think that it would be great to find a nomenclature about the classes that will represent our specimens. For instance the entity that is linked to our diameter is automatically name informationbearingentity1 by owlready2. The naming can be different but I don't know what we should choose. I could imagine that something like specimenNameDiameter would be better. Is there a preferred way to name those?

@joergfunger
Copy link
Member Author

The shacl valdidation is already implemented by @horstf and there is a merge request #18 . So in theory that is just a prcoedure to validate the single dataset before joining, though if it passes the test (and only in that case it should be added to the graph) there is no change in the ttl of the single test. That said, in a first step you don't have to worry about the shacl validation, that could be added afterwards and maybe even @horstf could help doing that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants