Notary Seal - Revision history

Tom: /* References */

2025-08-14T19:58:16Z

‎References

Tom: /* Preconditions */

2025-03-07T19:44:43Z

‎Preconditions

Tom: /* Unsuccessful Outcome */

2022-11-29T15:48:40Z

‎Unsuccessful Outcome

Tom: /* Preconditions */

2022-11-29T15:47:49Z

‎Preconditions

Tom: /* Actors */

2022-11-29T15:46:57Z

‎Actors

Tom: /* Context */

2022-11-29T15:45:44Z

‎Context

Tom: /* Actors */

2022-11-14T20:56:56Z

‎Actors

Tom: /* Contents of a digital notary seal */

2022-11-14T20:52:43Z

‎Contents of a digital notary seal

Tom: /* Contents of a digital notary seal */

2022-11-14T20:51:32Z

‎Contents of a digital notary seal

Tom: /* Taxonomy */

2022-11-14T20:50:31Z

‎Taxonomy

@@ Line 72: / Line 72: @@
 # Is a picture required for holder matching to the web site access points.
 # Is fraud one of the threats to be addressed within the scope of the recommendation?
 ==References==

@@ Line 36: / Line 36: @@
 * Note that the exact method used for access can be radios or visual displays. This use case will describe the use of visual display of a QR code for convenience only. Any presentation media that meets the same ease of access would be acceptable. The QR code has the advantage that it can be presented on a smartphone or printed on a sheet of paper for those without smartphones.
 * The person, at home, wishes to acquire an access token with a [[Notary Seal]] that will allow them, when and where presented, access to a desired resource.
-* While access to alcoholic beverages could talk place at several access points, for the purposes of this use case, it is assumed that every person with access to the private locations where alcohol is available will be verified to be 21 so that a single access point get access to both the physical location, as well as the alcoholic beverages, in a manner similar to the "No person under 21 permitted beyond this point" rule.
+* While access to alcoholic beverages could talk place at several access points, for the purposes of this use case, it is assumed that every person with access to the private locations where alcohol is available will be verified to be 21 so that a single access point get access to both the [[Physical Location]], as well as the alcoholic beverages, in a manner similar to the "No person under 21 permitted beyond this point" rule.
 * A holder at a venue can wander around during the transaction (either physically or virtually) with access points with many criteria so it will not be possible to determine in advance which access points a user might visit during the transaction. The approach taken here is to list all of the user claims that MIGHT BE required on the access token.
 ===Trigger===

@@ Line 53: / Line 53: @@
 ==Unsuccessful Outcome==
-# Validity of the access token is tested by the patron before travel to the park. This is a better outcome that getting to the park and then being denied access, so it should be considered a partial success.
+# Verification of the access token is tested by the patron before travel to the park. This is a better outcome that getting to the park and then being denied access, so it should be considered a partial success.
 #Failure to access at the entrance portal. The reason should be clear as a ticket counter available to get adjustments as required.
 #The Notary may need to be part of the process of getting a document this they are able to apply the [[Notary Seal].

@@ Line 30: / Line 30: @@
 ==Preconditions==
-* A state with strict rules about:
+* A state with strict rules about (for example):
 # Minors access to alcoholic beverages. The only officially recognized digital proof of age is the state-issued driver's license or eID.
 # Additional criteria like accreditation or health status for access to a venue or to take some action.

@@ Line 12: / Line 12: @@
 # Holder seeking access to one (or more) game.
 # Notary is used here to mean a notary public or other individual authorized to perform a notarial act as may be required for the acceptance of a digital document.
-# Validation web site that can analyze a person's access token remotely to let them know what access would be granted if used as specified by the relying party.
+# Verification web site that can analyze a person's access token remotely to let them know what access would be granted if used as specified by the relying party.
 # Relying Party intake routine will need a collection of credentials and attributes that taken together give the required level of assurance to complete the transaction.
 * Note that the validation and relying party may, or may not, be the same [[Entity]].

@@ Line 14: / Line 14: @@
 # Validation web site that can analyze a person's access token remotely to let them know what access would be granted if used as specified by the relying party.
 # Relying Party intake routine will need a collection of credentials and attributes that taken together give the required level of assurance to complete the transaction.
-Note that the validation and relying party may, or may not, be the same [[Entity]].
+* Note that the validation and relying party may, or may not, be the same [[Entity]].
 ===Taxonomy===
 * Notary Seal = a verifiable digital indictor that a nortorial act has successful been preformed.
 ===Contents of a digital notary seal===
 # hash of doc notarized

@@ Line 22: / Line 22: @@
 # category of notary in this instance
 # date and place notarized
-# id of notary + things like dates and authority
+# id of notary + things like dates and authority (this might be a credential all on its own)
 ==Preconditions==