| Time | Item | Who | Notes |
|---|
| Next Steps | Former user (Deleted) | - will be an editor, with John,
- Will edit, draft and comment until we get a version 1
- Will present version 1 for Work Group Review and comment, everyone is welcome to comment on all drafts using the comment form at the bottom of the specification
- John, Mary, Mark, have
|
| Â | introduce spec | Â | - the spec is setup to make compliance very easy for organisations and to make it very easy to see if what the org self asserts is true.
- the spec development priorities are based on increasing and extending usability of compliance with core extensions, trusted services extensions, and different operational contexts of consent
- compliance requirements are operators
- Context of the compliance, e.g. location of consent, has its own operational requirements for compliance in different legislation. e.g. website based consent, mobile/app based consent.
|
| Â | Â | TBD | - adding additional jurisdictions
- rules for the compliance scale audit
- multiple jurisdictional use case
|
| Â | Call Quality was bad and lost connectivity | - | - |
| Â | Extensions To Add | Â | - keep a copy of all notice with receipt extension
|