Wallet Requests - Revision history

Tom: /* References */

2024-02-28T05:30:34Z

‎References

2024-02-27T15:22:51Z

‎Purpose Structure

2024-02-27T15:20:38Z

‎Purpose Structure

2024-02-27T15:19:13Z

‎Purpose Registries

2024-02-27T15:12:50Z

‎Solutions

2024-02-27T15:11:52Z

‎Solutions

2024-02-27T15:08:36Z

‎Full Title or Meme

2024-02-27T15:06:27Z

‎Purpose Structure

2024-02-27T15:04:51Z

‎Contents of Query

2024-02-27T14:58:41Z

‎Contents of Query

@@ Line 65: / Line 65: @@
 There are a large number of reasons why a Verifier might ask the user for verified claims of one sort or another. In some cases the purpose can easily determine the data field to supply. For example the requirement for a minimum age for COPPA is 13. In that case the purpose could be age over 12 which could be coded as "ao.12".
-The purpose will be coded as rurl?code. Where rurl is a URL in reversed order and code is any ASCII string the registry desires. The rurl "0?" means the purpose code table described below. The optional data element (claim) list would be a json string similar to that proposed in other standards organizations.  For example  {eu.purpose?code) could be a table created by the eu and put at the location HTTPS:purpose.eu.
+The purpose will be coded as rurl?code. Where rurl is a URL in reversed order and code is any ASCII string the registry desires. The rurl "0?" means the purpose code table described below. The optional data element (claim) list would be a json string similar to that proposed in other standards organizations.  For example  {eu.purpose?code) could be a table created by the eu and put at the location https://purpose.eu.
 ===Purpose Registries===

@@ Line 65: / Line 65: @@
 There are a large number of reasons why a Verifier might ask the user for verified claims of one sort or another. In some cases the purpose can easily determine the data field to supply. For example the requirement for a minimum age for COPPA is 13. In that case the purpose could be age over 12 which could be coded as "ao.12".
-The purpose will be coded as rurl?code. Where rurl is a URL in reversed order and code is any ASCII string the registry desires. The rurl 0? means the code described below. The optonal data element list would be a json string similar to that proposed in other standards organizations.  For example  {eu.purpose?code) could be a table created by the eu and put at the location HTTPS:purpose.eu.
+The purpose will be coded as rurl?code. Where rurl is a URL in reversed order and code is any ASCII string the registry desires. The rurl "0?" means the purpose code table described below. The optional data element (claim) list would be a json string similar to that proposed in other standards organizations.  For example  {eu.purpose?code) could be a table created by the eu and put at the location HTTPS:purpose.eu.
 ===Purpose Registries===

@@ Line 64: / Line 64: @@
 ===Purpose Structure===
 There are a large number of reasons why a Verifier might ask the user for verified claims of one sort or another. In some cases the purpose can easily determine the data field to supply. For example the requirement for a minimum age for COPPA is 13. In that case the purpose could be age over 12 which could be coded as "ao.12".
 ===Purpose Registries===

@@ Line 74: / Line 74: @@
 | ao.xx || age over || ao.12 || the minimum age to avoid regulation like COPPA rules
 |-
+|}
 ==References==

@@ Line 2: / Line 2: @@
 What should a request to the wallet look like to achieve the purpose of the [[Verifier]] and the privacy of the [[Subject]].
-Also known as a Generic Wallet Query Language this proposal has deliberately not been formatted in any existing group's format as it is not clear which standards group is best suited to address the issue.
+Also known as a Generic Wallet Query Language this proposal has deliberately been formatted as an explainer and not in any existing group's format as it is not clear which standards group is best suited to address the issue. The need for an explainer will exist even after a standard is created.
 The primary deliverable is a message that can be created by any verifier independent of media used to transmit the query to the user's device or the format of credentials in the user's possession. The primary objective is to provide the holder of the device with a single screen information display that can be acted on by the user without referencing any other source.

@@ Line 62: / Line 62: @@
 None of these ideas or names originated with the paper.  Some of the sources include:
 *[https://github.com/KantaraInitiative/WG-ANCR/blob/main/TPI/ANCR-TPI-Conformity%20Specification%20v0.9.pdf ANCR-TPI-Conformity Specification v0.9.pdf] Advanced Notice and Consent Receipt - Transparency Privacy Indicator dated 2023-07 (To see the whole doc you need to keep clicking on "show more data")
 ==References==

@@ Line 35: / Line 35: @@
 ===Contents of Query===
-These are proposed data for the query to the wallet.
+These are proposed data for the query from the Verifier to the wallet.
 The security for this message has yet to be formalized. It could be be the inclusion of federation Metadata or a cert from a trust registry or as part of a signing key.