Skip to content

Wallet Conformance Criteria content correction re: ATP-Equivalent and DSCSA Authority credentials. #93

Description

@rceleste125

Steering: Proposal Summary

Used to propose a change or addition to Steering.
This is for the Steering work START approval step. Discuss the proposed work or change.

Section 5. Integration with VRS Providers, 1st paragraph has a statement about DSCSA Authority and ATP Equivalent credentials being discussed. Now that we have specified them, this needs to be corrected.

Steering: Publication Summary

Used to present completed work to Steering for approval to publish.
Discuss the work that was completed in reference to the above proposal. Include any differences from the proposal and why.
use [GitHub Preview](https://htmlpreview.github.io/) to show final state of documents along with pull requests (if needed).


Detailed Description:

Current text: "At time of publication, the use of Authority and ATP Equivalent credentials within the VRS is being discussed among relevant stakeholder groups."

As we have created the specs for these credential types, we need to adjust this text.

Triage:

  • Is Issue appropriate for OCI Architecture
  • Assign Size
  • Assign Priority
  • Assign Label (include Type of change and Steering "Review" or "FYI")
  • 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

Needs Steering Consensus

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

- Steering/Industry Notification

Does not need Steering Consensus (Steering may require a Consensus decision or futher clarification prior to issue being resolved by P&A

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

Communication

  • Website
  • Newsletter
  • email
  • None
  • Other:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Steering - FYITechnical or internal change. Not necessary for Steering to review.documentationImprovements or additions to documentation

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions