Commit 2da27995 authored by fmerg's avatar fmerg

Try relative urls

parent 9b3861e2
Pipeline #3213 passed with stages
in 1 minute and 8 seconds
......@@ -8,7 +8,7 @@ The eSSIF-Lab framework has an architecture which is further developed during th
This means that all eSSIF-Lab open calls are directly related to the eSSIF-Lab architecture, see Figure 1 below. This architecture will remain work in progress during the whole eSSIF-Lab project in 2020-2022.
![eSSIF-Lab Architecture](/images/eSSIF-Lab-Architecture.png)
![eSSIF-Lab Architecture](https://essif-lab.pages.grnet.gr/essif-lab/images/eSSIF-Lab-Architecture.png)
*Figure 1: eSSIF-Lab architecture*
......
......@@ -43,7 +43,7 @@ However, the participants of a business transaction are different parties, which
Every agent that communicates with another actor for the purpose of progressing a transaction, will need to be sufficiently sure (to the extent necessary for the value of the transaction) that the actor that it is communicating with, is in fact an agent of the peer party of its owner. We will use the term ‘**peer agent (of a specific agent, in the context of a single transaction)**’ to refer to an actor with which the specific agent has a communications session, and for which it has obtained sufficient assurance that it is an agent of the peer party of its owner. Note that establishing whether or not an actor is a peer agent does not necessarily require knowing who the peer party actually is.
![eSSIF-Lab Single Party Functional Architecture Overview](images/eSSIF-Lab-Architecture.png)
![eSSIF-Lab Single Party Functional Architecture Overview](https://essif-lab.pages.grnet.gr/essif-lab/images/eSSIF-Lab-Architecture.png)
*Figure 1. eSSIF-Lab Single Party Functional Architecture Overview.*
......@@ -115,7 +115,7 @@ The **SSI Tech APIs** interface layer is the union of the interfaces that the co
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:
![eSSIF-Lab functional components that are part of the eSSIF-Lab infrastructure](images/eSSIF-Lab-architecture-infra-components.png)
![eSSIF-Lab functional components that are part of the eSSIF-Lab infrastructure](https://essif-lab.pages.grnet.gr/essif-lab/images/eSSIF-Lab-architecture-infra-components.png)
*Figure 2: eSSIF-Lab infrastructural (functional) components.*
......@@ -382,7 +382,7 @@ It is a task of the TVE to orchestrate the inputs: different parts of the form m
Because of this orchestration, the interface to the verifier component can be quite simple; it is shown in the image below:
![Generic Verification with SSI service](images/Generic Verification with SSI service.png)
![Generic Verification with SSI service](https://essif-lab.pages.grnet.gr/essif-lab/images/Generic Verification with SSI service.png)
The request identifier is included in messages between the TVE and verifier so as to allow them to handle different transactions at the same time.
......@@ -392,4 +392,4 @@ We assume that the provider has specified the form and the associated validation
[text still needs to be written\]
![Generic Issuing with SSI service](images/Generic Issuing with SSI service.png)
![Generic Issuing with SSI service](https://essif-lab.pages.grnet.gr/essif-lab/images/Generic Issuing with SSI service.png)
......@@ -14,7 +14,7 @@ The eSSIF-Lab framework is an SSI-domain-specific [software framework](https://e
Figure 2 sketches relationships between the open calls.
![Relationship among eSSIF-Lab open calls](/images/Relationship-among-eSSIF-Lab-open-calls.png)
![Relationship among eSSIF-Lab open calls](https://essif-lab.pages.grnet.gr/essif-lab/images/Relationship-among-eSSIF-Lab-open-calls.png)
Figure 2: Relationships between the eSSIF-Lab open calls
......
......@@ -17,59 +17,6 @@ const features = [
</>
),
},
// {
// title: <>Use Git and Gitlab</>,
// imageUrl: 'img/undraw_Tree_swing.svg',
// description: (
// <>
// How we work with git and gitlab (basic workflow, MRs, pre-commit hooks
// etc.).
// </>
// ),
// },
// {
// title: <>Work as a Team</>,
// imageUrl: 'img/undraw_co-working.svg',
// description: (
// <>
// How we collaborate as a team (scrum, agile, retrospectives, weekly
// meetings etc). How we apply best practices to our daily life.
// </>
// ),
// },
// {
// title: <>Easy to Use</>,
// imageUrl: 'images/eSSIF-Lab icon.png',
// description: (
// <>
// Docusaurus was designed from the ground up to be easily installed and
// used to get your website up and running quickly.
// </>
// ),
// },
// {
// title: <>Horizon 2020</>,
// imageUrl: 'images/EU-flag.jpg',
// description: (
// <>
// Funded by the European Commission, as part of the Horizon 2020 Research
// and Innovation Programme.
// </>
// ),
// },
// ---------------------------------------------------------------------------
//
// {
// title: <>Powered by React</>,
// imageUrl: 'img/undraw_docusaurus_react.svg',
// description: (
// <>
// Extend or customize your website layout by reusing React. Docusaurus can
// be extended while reusing the same header and footer.
// </>
// ),
// },
];
function Feature({imageUrl, title, description}) {
......
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