Steering summary:
VRS can now submit Self-Attestations. The repo has been created. We suggest to add the link to the Conformance Prgrm.

---

• P&A to decide on storage location
• create repo
• inform Messaging Team
• add ref to Conformance Prgrm

See draft: https://docs.google.com/document/d/1o_kXMNw5DzO-NpawGbp8HgeFCei3BAtgnTuuqgMu33Q/edit

new version of Conformance Program = v1.1.1

the prgram has only placeholder text instead of hyperlink to the repos atm. since we now have those addresses, we should add them
https://open-credentialing-initiative.github.io/Conformance-Program/latest/index.html#trusted-service-provider-registries

suggest that

• we refer to wallet criteria for issuer reg
• link to https://github.com/Open-Credentialing-Initiative/marketplace/tree/main/proof for wallets? or create dedicated file that links to the proof folder?

Steering: Proposal Summary

This is for the Steering work START approval step. Discuss the proposed work or change.

The Confo Prgrm requires a signature for Self-Attestaions. This does not seem practical in all cases, especially for wallet NFR reporting. I suggest to re-scope the requirement.

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:
Signature requirement:

Such representations SHALL be signed by the Service Provider’s senior management and provided to the OCI Steering Committee for publication

NFR006 and NFR007 in the Wallet Criteria require wallets to self-report certain performance data. This does not necessarily require a document like a signed PDF because a public website-based status display constitutes a practical hands-off option. Such a website would not be signed

I suggest we specify which type of Self-Attestations require a signature, e.g. explicit assurances concerning OCI compliance but not operational reports that make no claim beyond the presented data.

---

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

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.

The Conformance Program requires wallets to submit Self-Attestations for NFR006 & 007. It does not specify when wallets should begin to self-report and at which cadence. P&A should define this.

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:

---

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