Skip to content

review & update version of 3rd party refs #63

Description

@bluesteens

Steering summary:
We reference 3rd party specs, e.g. from W3C, in our conformance documents and hyperlink to the latest version of these. However, we do not explicitly specify the 3rd part document version numbers. Thus, a change of the content shown on the hyperlinked 3rd party pages could result in inconsistencies and would suggest a change in our criteria, which is not intended. It is recommended to review those references and state the intended version numbers.


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:

Metadata

Metadata

Assignees

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