Commit 2b5ac5f3 authored by Rieks Joosten's avatar Rieks Joosten

Link to SSI Component API Documentation in GRNET Gitlab.

parent c805be3a
Pipeline #12820 passed with stages
in 2 minutes and 14 seconds
......@@ -11,3 +11,5 @@ yarn-debug.log*
yarn-error.log*
start_server.bat
*.ffs_batch
*.lnk
......@@ -98,16 +98,12 @@ It is expected that there are already some interfaces out there that may turn ou
There are two interface layers in this architecture
The \`**ESSIF Glue**\` interface layer consists of a set of APIs between the TVE and TRD on the one hand, and the WHIV components on the other hand.<sup>[API.1]</sup> The purpose of these APIs is to make calling the WHIV functions as simple as possible, given the functions of the Transaction Result Dispatcher and Transaction (Validation) Engine. Ultimately, we would like to see these APIs standardized. Having such APIs allows different Parties to create their own version of the WHIV components, supporting the SSI technologies as they see fit, and shrinking or expanding functionalities as they feel appropriate. Parties can then select such WHIV components as they see fit.
The \`**ESSIF Glue**\` interface layer consists of a set of APIs between the TVE and TRD on the one hand, and the WHIV components on the other hand. The current version of its specifications can be found in the eSSIF-Lab [SSI Service repository](https://gitlab.grnet.gr/essif-lab/tno-ssi-service/developer-docs). The purpose of these APIs is to make calling the WHIV functions as simple as possible, given the functions of the Transaction Result Dispatcher and Transaction (Validation) Engine. Ultimately, we would like to see these APIs standardized. Having such APIs allows different Parties to create their own version of the WHIV components, supporting the SSI technologies as they see fit, and shrinking or expanding functionalities as they feel appropriate. Parties can then select such WHIV components as they see fit.
The **SSI Tech APIs** interface layer is the union of the interfaces of the components within it. Any standardization in there is outside the scope of eSSIF-Lab.
-------
[API.1] When the specification of these APIs becomes available, a link thereto will be made available her.
-------
## 3. eSSIF-Lab Infrastructure Functional Components
This section details the functional specifications of the components that are in scope of the eSSIF-Lab infrastructure, i.e. in the green (rounded) rectangle as shown in the figure below:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment