Update Wallet Metadata and EC#1092
Conversation
Removed mention of Semantic Versioning from the README.
specs: updated rp md choices href and version
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Giuseppe De Marco <demarcog83@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Giuseppe De Marco <demarcog83@gmail.com>
logging policy: added Authentic Sources
terms: better definition of LoA
Authentic Source Onboarding Review
📢 Documentation Preview 🔍This PR comes from a forked repository, so the documentation preview was not automatically generated.
|
|
It might be worth revisiting this part for the With the changes introduced in this PR, the |
There was a problem hiding this comment.
Pull request overview
This PR updates the Wallet Provider Entity Configuration (EC) metadata structure and related documentation to align with issues #1075 and #1076 by removing the wallet_metadata wrapper and trimming presentation-time wallet metadata parameters.
Changes:
- Updated the WP EC example to remove
wallet_metadataand move wallet metadata fields to thewallet_solutiontop level. - Updated wallet solution metadata docs (IT/EN) to document the metadata fields at the top level (no
wallet_metadatacontainer). - Updated remote-flow docs (IT/EN) examples/tables to remove presentation-time
wallet_metadatafields that are no longer required.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| examples/ec-wp.json | Moves wallet metadata fields out of wallet_metadata into the wallet_solution object. |
| docs/it/wallet-solution-metadata.rst | Updates IT documentation to reflect the new metadata structure and adds guidance about authorization endpoint links. |
| docs/it/remote-flow.rst | Updates IT remote-flow examples/tables to reflect reduced wallet_metadata during presentation. |
| docs/en/wallet-solution-metadata.rst | Updates EN documentation to reflect the new metadata structure and adds guidance about authorization endpoint links. |
| docs/en/remote-flow.rst | Updates EN remote-flow examples/tables to reflect reduced wallet_metadata during presentation. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Manuel Rafeli <manuel.rafeli@pagopa.it> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Giada Sciarretta <giada.sciarretta@gmail.com>
📢 Documentation Preview 🔍This PR comes from a forked repository, so the documentation preview was not automatically generated.
|
📢 Documentation Preview 🔍This PR comes from a forked repository, so the documentation preview was not automatically generated.
|
| "credentials": [ | ||
| { | ||
| "version": "1.0", | ||
| "version": "1", |
| 2. **Private Sector AS** (Flexible Integration): Private entities provide specialized data through custom arrangements: | ||
|
|
||
| - **Custom APIs**: ``"integration_method": "custom_api"`` for business-specific data access patterns. | ||
| - **Custom APIs**: ``"integration_method": "pdnd"`` for business-specific data access. |
|
|
||
| - **Custom APIs**: ``"integration_method": "custom_api"`` for business-specific data access patterns. | ||
| - **Custom APIs**: ``"integration_method": "pdnd"`` for business-specific data access. | ||
| - **Regulatory Compliance**: Full transparency requirements with public catalog publication. |
| 2. **FA del Settore Privato** (Integrazione Flessibile): Le entità private forniscono dati specializzati tramite accordi personalizzati: | ||
|
|
||
| - **API Personalizzate**: ``"integration_method": "custom_api"`` per pattern di accesso ai dati specifici del business. | ||
| - **API Personalizzate**: ``"integration_method": "pdnd"`` per l'accesso ai dati specifici del business. |
|
|
||
| - **API Personalizzate**: ``"integration_method": "custom_api"`` per pattern di accesso ai dati specifici del business. | ||
| - **API Personalizzate**: ``"integration_method": "pdnd"`` per l'accesso ai dati specifici del business. | ||
| - **Conformità Normativa**: Requisiti di piena trasparenza con pubblicazione pubblica nel catalogo. |
| Authentic Source entities MUST undergo registration procedures that validate their data authority, declare their available claims from the standardized Claims Registry, and establish technical integration mechanisms. Authentic Source entities specify intended use cases (formally ``purposes``) that determine catalog eligibility per Supervisory Body policies. | ||
|
|
||
| Public Authentic Sources MUST leverage PDND integration to provide government data through standardized national infrastructure. | ||
| Public and Private Authentic Sources MUST leverage PDND integration to provide government data through standardized national infrastructure. |
| Le Fonti Autentiche Private POSSONO stabilire interfacce di servizio personalizzate che soddisfano requisiti organizzativi o normativi specifici. | ||
|
|
||
| Entrambe i flussi DEVONO assicurare standard di qualità dei dati e stabilire tracce di audit per tutte le attività di fornitura dati. | ||
| Le Fonti Autentiche Pubbliche e Private DEVONO sfruttare l'integrazione PDND per fornire dati governativi attraverso l'infrastruttura nazionale standardizzata. |
| * - **organization_info.tos_uri** | ||
| - string | ||
| - REQUIRED only for Private AS. URL to terms of service document. | ||
| - OPTIONAL. URL to terms of service document. |
This PR resolves
wallet_metadataand moving the metadata parameters directly at an upper level.The files modified are 6:
the others result from the switch from
italia:versione-correntetoitalia:eudiw