<spandir="">The Semantic Interoperability Layer (SIL) is the main component of the InterConnect Interoperability Framework. It is implemented as a distributed middleware responsible for facilitating secure and trusted semantic and syntactic interoperability between digital systems.</span>
<spandir="">The Semantic Interoperability Layer (SIL) is the main component of the InterConnect Interoperability Framework. It is implemented as a distributed middleware responsible for facilitating secure and trusted semantic and syntactic interoperability between digital systems.</span>
<spandir="">Central to the design of the Knowledge Engine is the concept of a **Knowledge Base (KB)**. A KB is a logical unit where knowledge flows to and/or from. These KBs can be anything like apps, services or existing databases and their nature depends on the use case that is being implemented. Also, the size of a KB is flexible, it can represent a single device or a whole platform with multiple devices and services.</span>
...
...
@@ -94,7 +94,7 @@ _Levels of interoperability provided by the Interoperability Framework:_
***<span dir="">Graph pattern matcher</span>**<spandir=""> – this is approach where KIs will execute knowledge exchange only if the graph patterns completely match. This approach ensures high speed knowledge exchanges.</span>
***<span dir="">Semantic reasoner</span>**<spandir=""> – this approach will ensure knowledge exchange through KIs with graph patterns that do not necessarily match completely. Partial matching is enabled and with it, new knowledge inference is possible in a wide Knowledge Network. The semantic reasoner is slower than the matcher, but it provides more flexibility in defining graph patterns for KBs.</span>
<spandir="">The Knowledge Engine Runtime comprises a set of Smart Connectors and internal interfaces needed for facilitating KIs between KBs. This KE Runtime can be deployed on different system levels: on level of single service runtime, on a level of one digital platform, shared among multiple services and digital platforms (e.g. on a pilot level) and on a global/project level. This flexibility in deploying KE Runtime constitutes the distributed nature of the Interoperability Framework.</span>
<spandir="">The Knowledge Engine Runtime comprises a set of Smart Connectors and internal interfaces needed for facilitating KIs between KBs. This KE Runtime can be deployed on different system levels: on level of single service runtime, on a level of one digital platform, shared among multiple services and digital platforms (e.g. on a pilot level) and on a global/project level. This flexibility in deploying KE Runtime constitutes the distributed nature of the Interoperability Framework.</span>
_Knowledge Engine as a distributed knowledge network:_
<spandir="">The P2P marketplace can be an energy marketplace or a marketplace for data transactions required for the realization of the community-based use cases. In the scope of the Task 5.4 the following P2P marketplace configurations are implemented and made available for the pilots and 3<sup>rd</sup> party integrators:</span>
</div>*<spandir="">Generic P2P marketplace configuration that can be easily adapted to specific use cases in energy and IoT domains. This implementation also features a web application for demonstration purposes.</span>
*<spandir="">Specialized configurations based on participating pilots (each having specific set of requirements for integration of P2P marketplaces into instances of the Interoperability Framework):</span>
*<spandir="">Dutch pilot - IoT data exchange with loyalty tokens realized through P2P marketplace.</span>
*<spandir="">Portuguese pilot - flexibility and energy profile trading/aggregation in communities through P2P marketplace instance.</span>
*<spandir="">Belgium pilot from Think E! and VUB - P2P energy trading within and between energy communities through instantiated P2P marketplace.</span>
</div>\*<spandir="">Generic P2P marketplace configuration that can be easily adapted to specific use cases in energy and IoT domains. This implementation also features a web application for demonstration purposes.</span>\*<spandir="">Specialized configurations based on participating pilots (each having specific set of requirements for integration of P2P marketplaces into instances of the Interoperability Framework):</span>\*<spandir="">Dutch pilot - IoT data exchange with loyalty tokens realized through P2P marketplace.</span>\*<spandir="">Portuguese pilot - flexibility and energy profile trading/aggregation in communities through P2P marketplace instance.</span>\*<spandir="">Belgium pilot from Think E! and VUB - P2P energy trading within and between energy communities through instantiated P2P marketplace.</span>
[Portuguese pilot (flexibility and energy profile trading/aggregation in communities) configuration, code and documentation](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace/-/tree/p2p-flex-sharing)
[Belgian pilot (P2P energy trading within and between energy communities) configuration, code and documentation](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace/-/tree/p2p-energy-trading)
[Belgian pilot (P2P energy trading within and between energy communities) configuration, code and documentation](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace/-/tree/p2p-energy-trading)
## Service Specific Adapters
...
...
@@ -198,6 +194,9 @@ _Interoperability chain and message sequence chart between two interoperable ser
Methodology for building Service Specific Adapters (SSA) will be included here by 25th of February 2022.
## Cascade Funding Opportunities
Here you can find the latest information about the project funding opportunities for European SMEs and Startups: https://interconnect-opencalls.fundingbox.com/
## Examples and Tutorials
Examples and tutorials in preparation - to be provided by 28th of February 2022.