Changes

Page history
Update home authored by Rafael Braga Costa's avatar Rafael Braga Costa
Hide whitespace changes
Inline Side-by-side
home.md
View page @ 2a579aeb
...@@ -45,6 +45,7 @@ Fig. 1- _Overview of InterConnect ontologies_ in relation to SAREF and other exi ...@@ -45,6 +45,7 @@ Fig. 1- _Overview of InterConnect ontologies_ in relation to SAREF and other exi
Reuse of existing models is one of the pillars of the semantic web and linked data modelling paradigm. In the subsequent table, we provide a visual overview of the other external ontologies and data models that we have reused, in addition to SAREF, as basis for the InterConnect ontologies. Reuse of existing models is one of the pillars of the semantic web and linked data modelling paradigm. In the subsequent table, we provide a visual overview of the other external ontologies and data models that we have reused, in addition to SAREF, as basis for the InterConnect ontologies.
Table 1 – _Prefixes and namespaces_ of the _external_ ontologies reused by InterConnect Table 1 – _Prefixes and namespaces_ of the _external_ ontologies reused by InterConnect
| Prefix | Namespace | Main concepts | | Prefix | Namespace | Main concepts |
|--------|-----------|---------------| |--------|-----------|---------------|
| foaf | <http://xmlns.com/foaf/0.1/> | Agent | | foaf | <http://xmlns.com/foaf/0.1/> | Agent |
...@@ -63,6 +64,7 @@ Table 1 – _Prefixes and namespaces_ of the _external_ ontologies reused by Int ...@@ -63,6 +64,7 @@ Table 1 – _Prefixes and namespaces_ of the _external_ ontologies reused by Int
Within the framework of InterConnect project, the following nine ontologies have been modeled. Their prefixes and namespaces are presented hereunder. Within the framework of InterConnect project, the following nine ontologies have been modeled. Their prefixes and namespaces are presented hereunder.
Table 2 – _Prefixes and namespaces_ of the InterConnect ontologies Table 2 – _Prefixes and namespaces_ of the InterConnect ontologies
| Prefix | Namespace | Main concepts | | Prefix | Namespace | Main concepts |
|--------|-----------|---------------| |--------|-----------|---------------|
| ic-data | <http://ontology.tno.nl/interconnect/datapoint#> | Datapoint, TimeSeries, Message, Utility Purpose | | ic-data | <http://ontology.tno.nl/interconnect/datapoint#> | Datapoint, TimeSeries, Message, Utility Purpose |
...@@ -198,10 +200,10 @@ _High level architecture of the Generic Adapter:_ ...@@ -198,10 +200,10 @@ _High level architecture of the Generic Adapter:_
* **<span dir="">Hyperledger Fabric blockchain configurations</span>**<span dir=""> for different types of P2P marketplaces (different hierarchies, consortium organizations, stakeholders, nodes and channels).</span> * **<span dir="">Hyperledger Fabric blockchain configurations</span>**<span dir=""> for different types of P2P marketplaces (different hierarchies, consortium organizations, stakeholders, nodes and channels).</span>
* **<span dir="">Smart contract templates</span>**<span dir=""> for different types of orders and transactions to be featured in the marketplace. Smart contracts will include APIs for end user GUIs (web application) and APIs for services for automated P2P trading.</span> * **<span dir="">Smart contract templates</span>**<span dir=""> for different types of orders and transactions to be featured in the marketplace. Smart contracts will include APIs for end user GUIs (web application) and APIs for services for automated P2P trading.</span>
* <span dir="">Smart contract templates for generating reports and audits about status of the marketplace and executed transactions - in line with regulatory and business requirements.</span> * <span dir="">Smart contract templates for generating reports and audits about status of the marketplace and executed transactions - in line with regulatory and business requirements.</span>
* <span dir="">Smart contract implemented as semantic interoperability adapter for interfacing with the wider InterConnect Interoperability Framework.</span> * <span dir="">Smart contract implemented as semantic interoperability adapter for interfacing with the wider InterConnect Interoperability Framework.</span>
* <span dir="">Smart contracts for registering and identifying key actors and resources constituting P2P marketplaces.</span> * <span dir="">Smart contracts for registering and identifying key actors and resources constituting P2P marketplaces.</span>
* <span dir="">Smart Contracts for integration of interoperable services which write data to or read data from the Hyperledger Fabric. This ensures that the P2P marketplaces are integrated with a wider instance of Interoperability Framework.</span> * <span dir="">Smart Contracts for integration of interoperable services which write data to or read data from the Hyperledger Fabric. This ensures that the P2P marketplaces are integrated with a wider instance of Interoperability Framework.</span>
* **<span dir="">Configurable order matching engine</span>**<span dir=""> for managing regulatory constraints, transaction priorities and conflict resolutions. The ordering engine also chains the smart contract calls performed by services participating in the P2P marketplace.</span> * **<span dir="">Configurable order matching engine</span>**<span dir=""> for managing regulatory constraints, transaction priorities and conflict resolutions. The ordering engine also chains the smart contract calls performed by services participating in the P2P marketplace.</span>
* **<span dir="">White-labelled web application</span>**<span dir=""> for providing interface through which end users place orders. The web application can be instantiated and adapted to specific needs of a community establishing the P2P marketplace.</span> * **<span dir="">White-labelled web application</span>**<span dir=""> for providing interface through which end users place orders. The web application can be instantiated and adapted to specific needs of a community establishing the P2P marketplace.</span>
...@@ -211,17 +213,17 @@ _InterConnect P2P marketplace enablers:_ ...@@ -211,17 +213,17 @@ _InterConnect P2P marketplace enablers:_
![image](uploads/44add4a2118f84fd561462d142c4df37/image.png) ![image](uploads/44add4a2118f84fd561462d142c4df37/image.png)
<div>
<span dir="">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> <span dir="">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>
* **<span dir="">Generic P2P marketplace configuration</span>**<span dir=""> 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> * **<span dir="">Generic P2P marketplace configuration</span>**<span dir=""> 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>
* **<span dir="">Specialized configurations</span>**<span dir=""> based on participating pilots (each having specific set of requirements for integration of P2P marketplaces into instances of the Interoperability Framework):</span> * **<span dir="">Specialized configurations</span>**<span dir=""> based on participating pilots (each having specific set of requirements for integration of P2P marketplaces into instances of the Interoperability Framework):</span>
* **<span dir="">Dutch pilot</span>**<span dir=""> - IoT data exchange with loyalty tokens realized through P2P marketplace.</span> * **<span dir="">Dutch pilot</span>**<span dir=""> - IoT data exchange with loyalty tokens realized through P2P marketplace.</span>
* **<span dir="">Portuguese pilot</span>**<span dir=""> - flexibility and energy profile trading/aggregation in communities through P2P marketplace instance.</span> * **<span dir="">Portuguese pilot</span>**<span dir=""> - flexibility and energy profile trading/aggregation in communities through P2P marketplace instance.</span>
* **<span dir="">Belgium pilot from Think E! and VUB</span>**<span dir=""> - P2P energy trading within and between energy communities through instantiated P2P marketplace.</span> * **<span dir="">Belgium pilot from Think E! and VUB</span>**<span dir=""> - P2P energy trading within and between energy communities through instantiated P2P marketplace.</span>
</div>[P2P marketplace enablers repository](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace) [P2P marketplace enablers repository](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace)
[Generic P2P marketplace configuration, code and documentation](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace/-/tree/p2p-sample-marketplace) [Generic P2P marketplace configuration, code and documentation](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace/-/tree/p2p-sample-marketplace)
...@@ -238,10 +240,10 @@ _InterConnect P2P marketplace enablers:_ ...@@ -238,10 +240,10 @@ _InterConnect P2P marketplace enablers:_
* <span dir="">SSA Service endpoint functionality – includes all necessary functionality to interact with the service via the offered (legacy) service API.</span> * <span dir="">SSA Service endpoint functionality – includes all necessary functionality to interact with the service via the offered (legacy) service API.</span>
* <span dir="">SSA mapping functionality – performs mapping of parameter bindings (semantic interface) to service API parameters and vice versa. Can be one-to-one mapping or more complex logic to combine for instance several API calls to complete one binding set.</span> * <span dir="">SSA mapping functionality – performs mapping of parameter bindings (semantic interface) to service API parameters and vice versa. Can be one-to-one mapping or more complex logic to combine for instance several API calls to complete one binding set.</span>
* <span dir="">SSA GA endpoint functionality:</span> * <span dir="">SSA GA endpoint functionality:</span>
* <span dir="">Register the Generic Adapter instance for this service.</span> * <span dir="">Register the Generic Adapter instance for this service.</span>
* <span dir="">Register the Knowledge Base - this creates a smart connector.</span> * <span dir="">Register the Knowledge Base - this creates a smart connector.</span>
* <span dir="">Register the Knowledge Interactions (Graph Patterns).</span> * <span dir="">Register the Knowledge Interactions (Graph Patterns).</span>
* <span dir="">Offer Knowledge Interaction execution.</span> * <span dir="">Offer Knowledge Interaction execution.</span>
_Knowledge Base with its SSA and GA:_ _Knowledge Base with its SSA and GA:_
...@@ -301,4 +303,4 @@ The Graph pattern visualiser tool is available here. It allows to create a graph ...@@ -301,4 +303,4 @@ The Graph pattern visualiser tool is available here. It allows to create a graph
# InterConnect Project Prototypes # InterConnect Project Prototypes
[InterConnect Prototypes](https://gitlab.inesctec.pt/groups/interconnect-public/-/wikis/Project-Prototypes) [InterConnect Prototypes](https://gitlab.inesctec.pt/groups/interconnect-public/-/wikis/Project-Prototypes)
\ No newline at end of file