docs: updated requirements

Requirements.md

@@ -1,8 +1,5 @@
-
-
 # TODOs for end-to-end requirements:
 
-
 - [ ] Protocol message modelling
   - [ ] claim request messages
   - [ ] claim provision messages
@@ -12,16 +9,20 @@
   - [ ] Log Access Grants
   - [ ] Log Operations
 - [ ] Authorization system
-  - [ ] Include authorization endpoint operations
-  - [ ] Include log access operations (others are internal)
+  - [ ] include logging endpoint
+  - [ ] include authorization endpoint 
+  - [ ] include policy management endpoint
 - [ ] Mock Policy instantiation
   - [ ] Write out policy model that works for demo
   - [ ] Discover existing policies to instantly grant some access
   - [ ] Link generic - instantiated - grant - operation
 - [ ] Negotiation implementations
   - [ ] Return instantiated policy requirements from ticket resolving function to create a signed instantiated policy to return
 - [ ] Signatures
-  - [ ] Sign and return agreement (either separately or together with grant)
+  - [ ] Create a VC form an instantiated policy
+  - [ ] Create verification endpoint for issued VCs 
+- [ ] Government mockup
+   - [ ] Create verification endpoint for issued VCs (can be mocked)
 - [ ] Client
   - [ ] Make some mock-up of how storage could be handled in a way that allows for auditing
-  - [ ] Recurring requests make use of the same grant?
+  - [ ] Recurring requests make use of the same grant?

packages/uma/README.md

@@ -13,4 +13,7 @@ can be swapped in.
 
 ## Known limitations
 ### Unused parameters in token request
-For token requests with grant_type `urn:ietf:params:oauth:grant-type:uma-ticket`, the token endpoint will ignore paramters `pct` and `scope` defined as optional in section 3.3.1 of the specification.
+For token requests with grant_type `urn:ietf:params:oauth:grant-type:uma-ticket`, the token endpoint will ignore paramters `pct` and `scope` defined as optional in section 3.3.1 of the specification.
+
+
+