-
Notifications
You must be signed in to change notification settings - Fork 3
Agenda 20171019
ianbjacobs edited this page Oct 17, 2017
·
3 revisions
Agenda for 2017-10-19. See also Meeting logistics.
- Where should we start?
- Who wishes to contribute to writing up the use case documentation?
- Thursday, 9 November in the morning, as part of TPAC 2017
- The TPAC 2017 agenda will be built of use cases
- Our mission for the next few weeks is to write down use cases
- A week before the meeting, we prioritize them and establish how to review them at TPAC (e.g., survey of all, or deep dive on 1 or 2).
- After TPAC we refine further, socialize, and pursue gap analysis
- What devices must be accessible to Web app developers? Are new browser capabilities necessary to enable this?
- What is the user experience in the use case that would be expected in a browser?
- Why would a Web standard be useful? What is the interoperability benefit?
- Be explicit about pre-requisites for use cases. For example: "the user is not required to have an account with the vendor prior to the transaction".
- Describe the flow of information
See the explainer template.