| Excerpt | ||
|---|---|---|
| ||
It may be easiest to edit the incomplete links in the template text below in "wiki markup" mode. |
...
This document is a product of the CISWG Work Group. It records the scenarios and use cases governing the development of XXX the Consent Receipt Schema (CRS) and guiding associated implementations and deployments.
...
- Pending: Initial status when first submitted
- Accepted: Needs to be accounted for in UMA Consent Receipt Schema V1 and/or its associated compliant implementations
- Deferred: Relevant to the problem space; may be considered in future versions
- Rejected: Out of scope
...
Specify the existing fields for a consent transaction receipt and list them as a basic template for consent receipts. (Note: This entails formally defined attributes, published and open for comment. )
Develop scenario covering the life cycle of a minimum viable consent receipt for building a demonstrator. This would involve
- Create a consent receipt generator, --> Common Terms, Legal.TXT
- Create a consent receipt button, --> Embed Code, publish legal.txt
- provision Provision a consent to a service user
- service Service user, uses the receipt to achieve the use case specified.
Intended Use
Use Case: Demonstrator (Pending)
Submitted by: Mark Lizar
So far this looks like --> Scenario 1
...