Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Statement: The Issuer must ensure the existence of functionality allowing selective data release.

Review Meeting(s): TBD

Status: DRAFT

Selective Data Release

Statement (Single phrase or sentence)

The Issuer must ensure the existence of functionality allowing selective data release.

Description

The Issuer must ensure that the mobile credential app allows the mobile credential holder to share mobile credential data elements selectively. For example, if a request is for data elements A, B, and C it must be possible for a mobile credential holder to release only elements A and B.

Scope (applies to)

  • Part A: Verifiers
  • Part B: Issuers
  • Part C: Providers

Select the Primary Consideration*

  • CC (Consent and Choice)
  • PL (Purpose legitimacy and specification)
  • CL (Collection limitation)
  • DM (Data minimization)
  • UR (Use, retention, and disclosure limitation)
  • AQ (Accuracy and quality)
  • OT (Openness, transparency, and access)
  • IA (Individual access & participation)
  • AC (Accountability)
  • IS (Information Security)
  • PS (Privacy compliance)

Reference

1_BC_CC

Select other relevant considerations

  • CC (Consent and Choice)
  • PL (Purpose legitimacy and specification)
  • CL (Collection limitation)
  • DM (Data minimization)
  • UR (Use, retention, and disclosure limitation)
  • AQ (Accuracy and quality)
  • OT (Openness, transparency, and access)
  • IA (Individual access & participation)
  • AC (Accountability)
  • IS (Information Security)
  • PS (Privacy compliance)

Select impacted Identifiers

  • Direct
  • Indirect
  • Unique

Related Requirements


Explanatory Notes (Text or Link)

Original author Loffie Jordaan (Unlicensed)

Archived version: Allow selective data release

Page Tasks:

  •  
  • No labels