Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

6.1 Documentation - IQ and comms with customer #55

Closed
8 of 31 tasks
bluesteens opened this issue May 25, 2023 · 0 comments · Fixed by #82
Closed
8 of 31 tasks

6.1 Documentation - IQ and comms with customer #55

bluesteens opened this issue May 25, 2023 · 0 comments · Fixed by #82
Assignees
Labels
documentation Improvements or additions to documentation Steering - Review Proposal and Completed work must be reviewed by Steering.

Comments

@bluesteens
Copy link
Member

bluesteens commented May 25, 2023

for Steering

Section 6.1 requires the wallet provider to create and share installation qualification documentation (IQ) during user onboarding. Whether IQ is needed depends on the wallet set-up. When and how to communicate with their prospects/customers is a provider decision. OCI can, at most, make recommendations.

Note for Steering Review:
Section 6.1 Documentation is a RECOMMENDATION that contains SHALLS. Changing SHALLs to SHOULDs to align with the RECOMMENDATION nature of 6.1.


suggestion

I'd reword the section as follows:

It is RECOMMENDED that the Digital Wallet provider offers the following documentation to support any validation process:

  • Functional documentation
  • End User documentation

The Digital Wallet provider SHOULD establish a process to create installation qualification documentation (IQ) if needed. Digital Wallet providers SHOULD provide any applicable IQ documentation to trading partners or other integrating solution providers. IQ should instruct about how the Digital Wallet components are installed and integrated correctly. This includes documentation of the software deployment process, installed system components, and host environments.


Triage:

  • Is Issue appropriate for OCI Architecture
  • Assign Size
  • Assign Priority
  • Assign Label (if needed)
  • OCI affected Artifacts Identified
  • Assign Triage - Artifact Version Target (v x.x.x Milestone)
  • Assign Triage - Interop Profile Version Target (v x.x.x Milestone)
  • Create sub-project (if needed)
  • Affected Parties (help determine Sunrise/Sunset):

Trading Partners

  • Issuers
  • Wallet Solutions
  • PI Verification Solutions

Affected OCI Artifact

  • Schema Document
  • Identity Schema
  • ATP Schema
  • Issuer Conformance Criteria
  • Wallet Conformance Criteria
  • VRS Solution Conformance Criteria
  • Wallet API Specification
  • Governance Document
  • Conformance Program
  • OCI Website
  • Internal Process

Change Category (Guides Steering Review)

Steering/Industry Review

  • Business-Level (May affect business operations)
  • OCI Governance, Policy or website feature

Steering/Industry Notification

  • Technical-Level (Does not affect business operations)
  • OCI Internal Process or Infrastructure

Communication

  • Website
  • Newsletter
  • email
  • Other
@bluesteens bluesteens added the documentation Improvements or additions to documentation label May 25, 2023
@rceleste125 rceleste125 added the Steering - Review Proposal and Completed work must be reviewed by Steering. label Jul 17, 2023
@bluesteens bluesteens linked a pull request Aug 16, 2023 that will close this issue
@bluesteens bluesteens self-assigned this Aug 16, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
documentation Improvements or additions to documentation Steering - Review Proposal and Completed work must be reviewed by Steering.
Projects
Status: Done - Published
Development

Successfully merging a pull request may close this issue.

2 participants