Commit 41ec29a7 authored by Rogier Morsink's avatar Rogier Morsink
Browse files

Update README.md

parent c37e798c
......@@ -17,10 +17,20 @@ Overall, mandates can be used for 2 different purposes:
- To authorize someone to have acess to data of someone else.
- To authorize someone to act on behalf of someone else.
The SSI Mandate Service is already used in different cases:
# Example solutions
The SSI Mandate Service is already used in two different cases. Both cases have a thoroughly elaborated problem. Both will be described here:
- Cross Border Delegation (Customs): Authorizing a company to do the customs administration on behalf of an importer from the Netherlands
- Construction site access (Heras Hekwerken): Authorizing a subcontractor or self-employed to have access to a construction site to be able to work for a main contractor.
## Construction site access
Heras Hekwerken is a well known company within the Netherlands, mainly because of the production of fences. But they are also one of the biggest suppliers of saftey and security solutions of construction sites. A major problem on construction sites is unauthorized or unqualified personnel present on such construction sites. Key cards are shared with coworkers or lent with malicious intentions. To face this problem, we've developed together with Heras this Mandate service.
The owner of the construction site will mandate the main contractor to take care of the complete authorization flow.
With this mandate the main contractor can provide subcontractors with several other mandates. One kind of mandate is just having access to the construction site. Another kind of mandate enables a subcontractor to provide other contractors or workers to gain access. Every provided mandate is related to the mandate which is used to provide this mandate. This results in a tree of mandates. There is no limit to the length of a branch within a tree.
Every mandate can be revoked. This immediately ends the validity of the mandate and all its child mandates.
# SSI Mandate project
The current SSI Mandate Service is described in the [functional specification](https://gitlab.grnet.gr/essif-lab/infrastructure_3/visma-connect/deliverables/-/blob/master/functional_specification.md). The specification describes the flow of defining, creating, accepting and proving a mandate. Next to that, the architecture of the SSI Mandate Service describes the components and the relation with the SSI Platform and the different users. The [interface specification](https://gitlab.grnet.gr/essif-lab/infrastructure_3/visma-connect/deliverables/-/blob/master/interface_specification.md) describes how you can use the Mandate Service using an API.
The backend application has been built with Hyperleder Indy and uses Trinsic as wallet provider. We want to make the application more interoperable, trustworthy and robust.
......
Supports Markdown
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