Dataservice binding #527
Merged
Dataservice binding #527
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IoT Agent was so far operating independent of datamodel. This had seveal disadvantages: - No detection of mismatch between namespaces - No systematic normalization/contextualization of input data with respect to data model - No trust building/plausiblity checks of incoming data - No use of knowledge graphs to pre-process data at gateway This PR provides a first draft of the future Dataservice which uses the ontology not only for data modelling but also to determine contextualization of incoming data. It only contains a test binding which is creating random data to demonstrate the concept. In future it will contain modules to retrieve data from other protocols, mainly proxied by MQTT and REST. As first step the JSON-LD "@context" is becoming a central structure. Every ontology must contain a context which determines the prefixes and namespace binding. For instance, it is assumed that every ontology must contain a "base:" prefix for the namespace which contains all the base terms of the used ontology (such as Binding and Connector classes) An example ontology is provided here: https://industryfusion.github.io/contexts/staging/example/v0.1 including context: https://industryfusion.github.io/contexts/staging/example/v0.1/context.jsonld Related Epic: IndustryFusion#514 Related User Story: IndustryFusion#515 Signed-off-by: marcel <wagmarcel@web.de>
wagmarcel
force-pushed
the
dataservice-binding
branch
from
89da15f
to
c3c7d40
Compare
abhijith-hr
approved these changes
Apr 3, 2024
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.