Commit c7101b22 authored by Georgios D. Tsoukalas's avatar Georgios D. Tsoukalas

Editing enhancements.

parent ee4d5b6a
......@@ -8,7 +8,7 @@ Applicants are expected to be already active in the SSI field and to be familiar
Subgrantees are expected to work in an ecosystem with other subgrantees for the purpose of ensuring interoperability at the various levels (technology, processes, business/policy), scalability of solutions, and ensuring that solutions are fit-for-purpose (i.e. can actually be used in practice). This implies that subgrantees collaborate in the project to maintain a shared vision, functional architecture and specifications of functionalities, API’s, ways of working etc.
The eSSIF-Lab consortium has drafted
The eSSIF-Lab consortium has drafted:
- an initial [Vision and Purpose document](essif-lab-vision-and-purpose.md), which states at a high level what it is eSSIF-Lab aims to contribute in terms of impact that it wants to see realized.
- an initial [Functional Architecture document](essif-lab-functional-architecture.md), which identifies several functional components that sit on top of different kinds of SSI-technologies in order to realize the vision, purpose and impact.
......@@ -19,13 +19,13 @@ Applications for the “First Business-oriented Call” are expected to submit p
## eSSIF-Lab Framework
The eSSIF-Lab framework is an SSI-domain-specific [software framework](https://en.wikipedia.org/wiki/Software_framework) that is
The eSSIF-Lab framework is an SSI-domain-specific [software framework](https://en.wikipedia.org/wiki/Software_framework) that is:
- built upon the extensions provided through the infrastructure-oriented call
- dedicated to the development of generic services that use SSI in 1<sup>st</sup> business-oriented call
- dedicated to the development of SSI-based applications in 2<sup>nd</sup> business-oriented call
The eSSIF-Lab framework has an architecture which is further developed during the project. We expect the subgrantees to form a business ecosystem together under eSSIF-Lab coordination. The emphasis is on interoperability, i.e. development and implementation of standardized protocols, data models and API’s, including contributing to standardization and performing of interoperability tests.
The eSSIF-Lab framework has an architecture which will be further developed during the project. We expect subgrantees to form a business ecosystem among them under eSSIF-Lab coordination. The emphasis is on interoperability, i.e. development and implementation of standardized protocols, data models and API’s, including contributing to standardization and performing of interoperability tests.
This means that all eSSIF-Lab open calls are directly related to the [eSSIF-Lab functional architecture](essif-lab-functional-architecture.md), for which we have an initial version as a 'stick in the ground', and that we expect to be further developed and refined as subgrantees cooperate during the whole eSSIF-Lab project in 2020-2022.
......@@ -63,14 +63,14 @@ The following are examples of topics that would be suitable for a potential prop
The following are examples of potential proposals. Applicants should use these for inspiration, and not take them normatively. Useful ideas and concepts for SSI that are not listed here are also very welcome. In case of doubt, contact us at [info@essif-lab.eu](mailto:info@essif-lab.eu).
- **SSI wallet**. eSSIF-Lab needs multiple wallet codebases to validate interoperability and to integrate with. A wallet must provide safeguards against inadvertent adding, reading, modifying or deleting contents; be available when needed; and provide only access to applications that are allowed to. What codebase could you offer?
- **SSI wallet**. eSSIF-Lab needs multiple wallet codebases to validate interoperability and to integrate with. A wallet must provide safeguards against inadvertent adding, reading, modifying or deleting contents. It must be available when needed and provide access only to applications that have been given permission. What codebase could you offer?
- **SSI smartphone app**. eSSIF-Lab needs multiple SSI apps that act on behalf of its owner; and that provides a user interface to register with the app, to get (re)authenticated, to specify preferences, to work with a browser for obtaining credentials, issuing credentials, filling in forms and requesting credentials from web-servers (to reduce the risk of dealing with fraudulent servers/fishing sites), to manage credentials it has obtained or issued, and to check the logs. What codebase could you offer?
- **SSI browser add-on**. How could the SSI wallet/app functionality be made available as browser plug-in? What codebase could you offer?
- **Web server proxy**. eSSIF-Lab may need a web solution, where the wallet resides in the cloud. What provisions can be made to make such solutions sufficiently secure? What codebase could you offer?
- **SSI browser add-on**. How could the SSI wallet/app functionality be made available as a browser plug-in? What codebase could you offer?
- **Web server proxy**. eSSIF-Lab may need a web solution where the wallet resides in the cloud. What provisions can be made to make such solutions sufficiently secure? What codebase could you offer?
- **Credential-query solution**. How could a verifier agent semantically specify what combination of credentials it requires? What solution can you offer to further automate the credential query-response process at both the verifier and holder side?
- **Automated issuer referral**. How could an SSI application be automatically referred to appropriate issuers, when a requested credential happens to be missing in the wallet?
- **Revocation service**. Many credentials (e.g. driver’s license) need the possibility of revocation. While many solutions exist (e.g. revocation lists, online status protocols, accumulators), each has its merits and drawbacks that may make it unsuitable for certain issuers to use. For example, how could a verifier at some later time check the revocation status of a credential in absence of the holder, while respecting GDPR? What solutions do you envision?
- **Cryptographically enforceable issuer policies**. As stated by the Dutch ministry of internal affairs, a government should protect its citizens from data-guzzlers, e.g. foreign customs or tech giants that may coerce Dutch citizens to provide all credentials from their wallet. So, what solution can you envision that enables an issuer to cryptographically enforce a policy to prevent such abuse?
- **Automated issuer referral**. How could an SSI application be automatically referred to the appropriate issuers to obtain a credential that is missing from the wallet?
- **Revocation service**. Many credentials (e.g. driver’s license) need the possibility of revocation. While many solutions exist (e.g. revocation lists, online status protocols, accumulators), each has its merits and drawbacks that may make it unsuitable for certain issuers to use. For example, how could a verifier at some later time check the revocation status of a credential in absence of the holder while respecting GDPR? What solutions do you envision?
- **Cryptographically enforceable issuer policies**. A government should protect its citizens from data-guzzlers, e.g. foreign customs or tech giants that may coerce foreign citizens to provide all credentials from their wallet. So, what solution can you envision that enables an issuer to cryptographically enforce a policy to prevent such abuse?
- **Calamity override**. In case of a calamity, what solution could you offer to give a health worker emergency access to health-related credentials, while respecting the self-sovereignty of the patient?
---
\ No newline at end of file
---
This diff is collapsed.
......@@ -6,21 +6,21 @@ eSSIF-Lab is funded by the European Commission, as part of the Horizon 2020 Rese
<p align="center">Author: Rieks Joosten (TNO)</p>
It is the eSSIF-Lab vision that Self-sovereign Identity (SSI) will *empower European citizens (as well as other individuals, of course)* by providing new means to manage privacy, eliminating logins, and making electronic transactions much faster and much safer, both via the Internet and in real, physical life. SSI will *empower European organisations and governments* by providing new means to speed up, secure and automate transactions with citizens, customers, suppliers and partners, resulting in tens of billions of euros savings annually on administrative costs in Europe. SSI will be *a new business ecosystem paradigm* with thousands of new jobs, many new job categories and new business opportunities for existing and new European companies. And last but certainly not least, SSI fosters *inclusiveness* and supports organizations and citizens to exercise their rights and fulfil their duties under the GDPR.
The eSSIF-Lab vision is that Self-sovereign Identity (SSI) will *empower European and other citizens* by providing new means to manage privacy by eliminating logins and making electronic transactions fast and safe both in the Internet and in physical life. SSI will *empower European organisations and governments* by providing new means to speed up, secure and automate transactions with citizens, customers, suppliers and partners, resulting in tens of billions of euros savings annually on administrative costs in Europe. SSI will be *a new business ecosystem paradigm* with thousands of new jobs, many new job categories and new business opportunities for existing and new European companies. And last, but certainly not least, SSI fosters *inclusiveness* and supports organizations and citizens to exercise their rights and fulfil their duties under the GDPR.
The current situation is that (SSI) solutions that are being created and brought to the market, often have specific applications in mind for which they provide a solution (vertical ‘stovepipes’), many have some kind of centralized governance/control, others have privacy issues, and none that we know of are interoperable with other such solutions.
The current situation is that (SSI) solutions that are being created and brought to the market either target specific applications for which they provide a vertical solution (‘stovepipes’), many need some kind of centralized governance/control, others have privacy issues, and none that we know of are interoperable with other such solutions.
The situation we would like to see is one in which we have SSI-enabled, interoperable and scalable technologies, that form an infrastructure that every application in any vertical can use in a very easy manner, for the exchange of verified (personal and non-personal) data. In that situation people, businesses and governments think more about the information they need and/or provide as they conduct business transactions. They no longer need to be concerned about the SSI technologies that have empowered them to make this happen.
The situation we would like to see is of SSI-enabled, interoperable and scalable technologies that form an infrastructure that every application in any vertical can easily use for the exchange of verified personal and non-personal data. In that situation, people, businesses and governments think more about the information they need and/or provide as they conduct business transactions. They no longer need to be concerned about the SSI technologies that are needed to make this happen.
| The **purpose of the eSSIF-Lab** ... |
| ------------------------------------------------------------ |
| ... is to specify, develop and validate technological and non-technological means that support people, businesses and governments to think about, design and operate their (information) processes and (electronically) conduct business transactions with one another. |
| ... is to specify, develop and validate technological and non-technological means that support people, businesses and governments to think about, design and operate their information processes and electronically conduct business transactions with each another. |
The context of the eSSIF-Lab vision can be found in articles 8-10 of the [*European Convention on Human Rights (ECHR)*](https://www.echr.coe.int/Pages/home.aspx?p=basictexts/convention), that state the rights of individuals regarding their privacy, and their freedoms to collect, process, store, and express information in a self-sovereign fashion, i.e. in a way that they can decide for themselves. This is without prejudice to Member States’ laws that exist to protect their national security, public safety, the economic well-being of the country, health or morals or the rights and freedoms of others, or to prevent disorder or crime. The eSSIF-Lab vision extends these rights and freedoms - within the limits of the law - to public and private organizations. Thus, we say that individuals as well as public and private organizations (that we collectively refer to as ‘parties’) are self-sovereign<sup>[1]</sup>.
Within (the limitations of) these rights and freedoms, we seek to support (electronic) business transactions, i.e. the (electronic) exchange of goods, services, funds, or data between parties, which we call ‘participants’ to the transaction<sup>[2]</sup>.
In the context of these rights and freedoms, we seek to support electronic business transactions, i.e. the electronic exchange of goods, services, funds, or data between parties, which we call ‘participants’ to the transaction<sup>[2]</sup>.
An electronic business transaction is a business transaction that requires each participant to have (at least one) electronic agent, i.e. equipment (e.g. an app on a mobile phone, a webserver, a browser, …) that acts on behalf of its owner in the transaction.
An electronic business transaction is a business transaction that requires each participant to have (at least one) electronic agent, i.e. equipment (e.g. an app on a mobile phone, a web server, a browser, …) that acts on behalf of its owner in the transaction.
## High-Level Example of a Business Transaction
......
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