trustoverip / tip0028-saturn-v

ToIP Interoperability Profile for the Saturn-V solution architecture.

ToIP TIP0028 Saturn-V

• Authors: Dan Gisolfi
• Status: PROPOSED
• Since: 2021-01-17
• Status Note: Draft (work-in-progress)
• Supersedes: TSWG Proposal
• Start Date: 2020-08-03
• Tags: #tswg, #recommendation

Summary

This is the first TIP proposal under the Trust over IP Technical Stack Working Group (TSWG) and it represents the next evolutionary step towards the moon shot known as decentralized identity. Building on the groundwork established in the Sovrin Community, this TIP seeks to integrate technology for three ToIP Layers to achieve a common goal -- help propel the adoption of digital credentials.

Purpose

This repo manages the development and maintenance of the subject ToIP deliverable. It contains the tools necessary to generate multiple renderings formats.

1. Interactive Online Website: GitHub Pages
2. Printable Documents
   • PDF Version
   • HTML Version
   • Standalone Markdown

Contributor's Guide

Project collaboration and coordination happens in the project wiki.

Documentation and Specification contributors should familiarize themselves with the Authoring Process.

Related Resources

1. ToIP Deliverables Portal - Status
2. ToIP Contributor's Workflow

tip0028-saturn-v's Issues

[SUGGETION] Move Saturn-V diagram to intro

https://trustoverip.github.io/TIP0028-saturn-v/
message is a little hidden with Saturn-V analogy, need a quick intro get people interested. close architecture page and add to Intro

[SUGGETION] Key motivations proposal

https://trustoverip.github.io/TIP0028-saturn-v/
suggestion list for Key Motivations

• interop is fundamental for success of SSI between vendors
• learn through interop if standard are understandable
• certify interoperability between vendors

Prime Repository

Establish a baseline TIP outline and example content for the Saturn-V Task Force to build upon.

[TIP] Establish baseline content outline

Problem/Concern

In order to organize our work and track process we need to come to agreement on a document outline.

Proposed Solution

The original baseline outline proposal was:

- 'Introduction': 'index.md'
- 'Use Cases': 'use_cases.md'
- 'Design Principles': 'design_principles.md'
- Features:
    - 'Feature 1': 'placeholder.md'
- Best Practices:
    - 'BP 1': 'placeholder.md'
- 'Solution Architecture': 'tech_stack.md'
- Stakeholders:
    - 'Evernym': './interop/evernym.md'
    - 'IBM': './interop/ibm.md'
    - 'iGrant.io': './interop/igrantio.md'
    - 'Lissi': './interop/lissi.md'
- Interoperability Testing:
    - 'Test Plans': 'test_plans.md'
    - 'Certifications': 'certifications.md'
- Marketplace Adoption:
    - 'Case studies':  'placeholder.md'
    - 'Metrics':  'placeholder.md'
- Help:
    - 'FAQ': 'faq.md'
    - 'Contact us': 'contact_us.md'

We will use this issue to come to consensus for the desired outline.

[SUGGETION] Remove vendor list in Intro

https://trustoverip.github.io/TIP0028-saturn-v/
Intro section vendor list is out of date

[SUGGETION] Intro explain other sections

https://trustoverip.github.io/TIP0028-saturn-v/
This may be optional but like to give very short explanation of other sections for quick reference in the intro.

[SUGGETION] Remove empty sections

https://trustoverip.github.io/TIP0028-saturn-v/
While sections are not populated hide them. Does not give good impression if have empty sections for visitors.

[SUGGETION] Add explanation to newcomers in wiki

Add to wiki.

If you are interested to participate these are the steps you be involved with.

1. Register participation
   Register as a stackholder, https://trustoverip.github.io/TIP0028-saturn-v/. Edit a company md file here.
   Explain Testing Preparation, https://github.com/trustoverip/TIP0028-saturn-v/wiki/Testing-Preparation
   Mobile / Issuer & support contact

2. Start interop test
   Attend weekly meeting and report progress and issues

3. Completion of testing
   If 2 companies achieved interoperability they make joint statement of successful mutual testing (peer certification)

[SUGGESTION] Tools and Best Practices

Based on the recent @JanLin presentation -- it would be helpful if we create a new wiki page for Tools and Best Practices.

This SHOULD include IndyScan and others.

[Interop] Clarification of ephemeral proofs test case

The test plans refers to a´n ephemeral proof (receiver only) but unclear what it rfc it is related. Appreciate some clarification which specification it refers to. It is not in the AIP 1.0 that I can tell. Below is the reference to the tests to be run.

https://trustoverip.github.io/TIP0028-saturn-v/test_plans/

[Interop] Automation of Mobile App Testing

We seek a solution for mobile app automation testing.

We will use this issue to noodle on a solution.

For starters here is a list of suggested open source tools to consider.