Create querying mixin

[Mec-iS]

Current behaviour

All the methods are stacked in the kglab module and it makes it difficult to handle.

New expected behaviour

Implement mixins for different functionalities in different modules:

• namespace management (ontology, controlled vocabularies)
• graph construction
• serialization
• SPARQL querying implemented by this PR
• SHACL validation
• inference based on OWL-RL, RDFS, SKOSby creating a mixin

@ceteri let me know if this is ok. The only problem I see is that the credits for writing the code are moved to the developer that created the mixin. So if you want to keep the credits to the developer that wrote the code in the first place he/she will have to create the mixins by himself. Let me know if this is a problem.

Change logs

• Add querying module that incapsulates querying for KnowledgeGraph
• Move querying out of KnowledgeGraph into QueryingMixin

[ceteri]

Awesome, thank you @Mec-iS!

Using mixin design pattern is a great fit for this refactoring of kglab, and alleviates some of the problems I'd encountered early (in the comment thread about instance members)

[tomaarsen]

Looks good! Well done.