Discuss issued and presented forms of JPTs

draft-ietf-jose-json-proof-token.md

@@ -128,25 +128,30 @@ The following is an example JWP Protected Header that includes a `cid`:
 
 <{{./fixtures/template/jpt-issuer-protected-header-with-cid.json}}
 
-# Payloads
+# Presented Claims and Proofs
 
-> Editor's Note: This section is incomplete. Use it only as an indicator of the intended direction.
-
-Application resolves each claim as required when processing the JPT.  Resolution can result in one of three things:
-1. A disclosed JSON value
-2. A custom proof method
-3. A `null` value
+Each claim in the issued form of the JPT results in one of three things in the presented form of the JPT:
+1. A disclosed JSON value.
+1. An indicator that the value was not disclosed.
+1. An algorithm-specific proof method.
 
 ## Disclosed
 
-Always an octet string of valid JSON text.
+A disclosed payload is represented as a UTF-encoded octet string representing a valid JSON value.
+
+## Undisclosed
+
+The placeholder indicating that a payload was not disclosed is represented as
+described in Section 6 (Serializations) of [@!I-D.ietf-jose-json-web-proof].
 
 ## Proof Methods
 
-* proof methods can be returned instead of a disclosed payload
-* these are generated by the algorithm from information in the JWP's proof value
-* a proof method may be custom based on the capabilities of the algorithm
-* define common proof method types available?
+Proof methods can be returned instead of a disclosed payload.
+These are generated in an algorithm-specific manner from information in the JWP's proof value.
+
+A proof method may be custom based on the capabilities of the algorithm.
+
+* TBD: Describe common proof method types available?
   * range
   * membership
   * time
@@ -205,6 +210,7 @@ for his valuable contributions to this specification.
   [[ To be removed from the final specification ]]
 
   * Update reference to new repository home
+  * Fixed #99: Discussed issued and presented forms of JPTs.
 
  -05