Areas of Work Going Forward
- API's, Policy Languages and Development of Code
- Finalize components, flows and API's
- Develop working code
- stand-alone consent as a service
- embedded in coupled to a Shib IdP
- controlling an integrated set of token issuing protocols
- Establishing a draft attribute release preference record
- Liaison with other protocols and flows that need consent; circulate architecture and protocols
- Develop the consent event record and notification services
- Develop architectures and interactions with OIDC and OAuthCurrent technical drafts and documents Current technical drafts and documents
- Informed Consent Support
- Identify the major information needs for the UI, including graphics, information dialogues, histories, minimal and required attributes, etc
- Identify sources for information feeds, including metadata, well-known URI and software statements,
- Deciding content/complexity relative to Refeds discussions, etc.
- fields, graphics
- Friendly name/value translation
- Adapting PrivacyLens to the new internals
- Replumbing PrivacyLens to the new internals
- Adding UI components to reflect new internal capabilities, such as off-line consent, limited delegation,
- Refining UI in response to feedback and new research
...