Verifiable Presentation - Revision history

Tom: /* Context */

2025-08-02T20:12:23Z

‎Context

2024-01-22T00:43:33Z

‎Components

2024-01-22T00:42:52Z

‎Components

2024-01-22T00:38:49Z

‎Context

2022-03-03T05:46:11Z

‎Hide information from VCs in VPs

2022-03-03T05:45:42Z

‎Hide information from VCs in VPs

2022-03-03T05:45:02Z

‎Hide information from VCs in VPs

2022-03-03T05:43:05Z

‎Hide information from VCs in VPs

2022-03-03T05:42:01Z

‎Hide information from VCs in VPs

2022-03-03T05:41:02Z

‎Context

@@ Line 3: / Line 3: @@
 ==Context==
 * [[Decentralized ID]] is a related effort of the
 * A [[Verifiable Presentation]] may also include a short lived liveness credential along with other credentials needed by the [[Relying Party]] under the assumption that the access to the VC is controlled by a phone with a lock screen.  It is also possible for the wallet to ask for a proof of presence at the time the VP is created, but that is less likely in practice.

@@ Line 35: / Line 35: @@
 ===Presentation Request===
-https://w3c-ccg.github.io/vp-request-spec/
+https://w3c-ccg.github.io/vp-request-spec/<blockquote>This specification describes a declarative JSON-based query language used by applications to perform requests from wallets and agents. The results of the requests are always wrapped in a Verifiable Presentation.</blockquote>
 ===Bindings to Users===
-Also called proof of presence.<blockquote>This specification describes a declarative JSON-based query language used by applications to perform requests from wallets and agents. The results of the requests are always wrapped in a Verifiable Presentation.</blockquote>
+Also called proof of presence.
 ====Use of External Sites====
 * [https://www.dhs.gov/publication/dhsallpia-089-dhs-international-biometric-interoperability-initiative-visa-waiver  DHS/ALL/PIA-089 DHS International Biometric Interoperability Initiative for the Visa Waiver Program]

@@ Line 33: / Line 33: @@
 ===Parts of [[Verifiable Credential]]s===
 * The user is asked to supply verifiable attributed from credentials that are on the user device or that can easily be acquired online.
 ===Bindings to Users===
-Also called proof of presence.
+Also called proof of presence.<blockquote>This specification describes a declarative JSON-based query language used by applications to perform requests from wallets and agents. The results of the requests are always wrapped in a Verifiable Presentation.</blockquote>
 ====Use of External Sites====
 * [https://www.dhs.gov/publication/dhsallpia-089-dhs-international-biometric-interoperability-initiative-visa-waiver  DHS/ALL/PIA-089 DHS International Biometric Interoperability Initiative for the Visa Waiver Program]

@@ Line 4: / Line 4: @@
 ==Context==
 * [[Decentralized ID]] is a related effort of the
-* A [[Verifiable Presentation]] is likely to includ a short lived liveness credential along with other credentials needed by the [[Relying Party]].
+* A [[Verifiable Presentation]] may also include a short lived liveness credential along with other credentials needed by the [[Relying Party]] under the assumption that the access to the VC is controlled by a phone with a lock screen.  It is also possible for the wallet to ask for a proof of presence at the time the VP is created, but that is less likely in practice.
 ==Hide information from VCs in VPs==

@@ Line 9: / Line 9: @@
 ==Hide information from VCs in VPs==
-Aplieox opened this issue 2022-03-01
+Aplieox opened this issue 2022-03-01 in DIF-ID slack
 Is there any way to hide informations from VCs in a VP? The Standard describes that such a privacy-enhancing feature should be implemented.

@@ Line 24: / Line 24: @@
 The recommended alternative is to use single purpose credentials, or credentials with few claims that can be disclosed together, as opposed to large credentials with multiple claims. This way, you are free to use any other cryptographic suite for both credentials and presentations.
- Aplieox
+Aplieox - Thanks for the quick answer. Single purpose Credentials or Credentials with minimal private data seem to be the easiest solution.
-bumblefudge commented 8 hours ago •
+bumblefudge commented
 @Aplieox , you might want to check out the JsonWebPresentation work item in the Applied Crypto WG at DIF-- it's a greenfield project to add a new form of token to the JSON family for just this purpose. I'm not sure how committed that WG is to backwards compatibility with presenting today's JWTs selectively (or if that's even mathematically possible!), but it's the best upgrade path I can imagine for today's JWT systems to upgrade to selective disclosure without having to scrap all the JW* token tooling!

@@ Line 9: / Line 9: @@
 ==Hide information from VCs in VPs==
-Aplieox opened this issue 20 hours ago · 3 comments
+Aplieox opened this issue 2022-03-01
 Is there any way to hide informations from VCs in a VP? The Standard describes that such a privacy-enhancing feature should be implemented.
 See here: https://www.w3.org/TR/vc-data-model/#presentations
 mirceanis commented
 Hiding information from VCs contained in a VP is only possible when using cryptographic systems that support this.
@@ Line 26: / Line 25: @@
   @Aplieox
-Author
 Aplieox commented 14 hours ago •
-edited
 Thanks for the quick answer. Single purpose Credentials or Credentials with minimal private data seem to be the easiest solution.