From zedwiki

DAY ONE, Tuesday April 15

This day is about creating a general overview of the requirements gathering, analyzing the data to see if we have critical mass to warrant a revision process. It is also about understanding how we will interact with NISO during the revision.

• 09:00-09:01 Scribe [George]
• 09:02-09:15 Administrative matters [George]
  • Karen Wetzel described her role at NISO as Standards Manager
  • Minutes will be taken by different committee members for the 6 half-days of the meeting
• 09:15-10:15 Requirements Gathering: General Review, Outcomes [Jennifer, Markus]
  • Minutes General Review
• 10:15-11:00 Requirements Analysis and Categorization - definition of problem areas [Markus]
• 11:00-11:15 Coffee Break
• 11:15-12:30 Requirements Analysis and Categorization pt II
  • Minutes Categorization
• 12:30-13:30 Lunch
• 13:30-14:00 Formal decision on revision process [George]
• 14:00-15:00 NISO revision process [Karen Wetzel]
• 15:00-16:30 Strawman process outline

DAY TWO, Wednesday April 16

This day is about building concensus on the nature of the revision; * what problems are we going to address in the new specification, and what will the actual effect be on users * how do we want to re-architecture the specification, and what will the effects be

• 09:00 - 09:01 Scribe [George]
• 09:00 - 12:30 Theme: Defining which issues to address
  • Minutes Quintessential Standard
• 12:30 - 13:30 Lunch
• 13:30 - 16:00 Theme: Overall Specification Design approach
  • Mod Squad report: DAISY Accessibility Framework
  • Following discussion on alternative approaches
  • Minutes Distribution and Authoring
• 16:00 - 16:30 Conclusion

DAY THREE, Thursday April 17

This day is about creating high level project plans, including both resources and timelines. There is also a slot for continued work on overarching architectural concerns.

• 09:00 - 09:01 Scribe [George]
• 09:00 - 12:30 Theme: High Level Project Plans [George, Markus]
  • Minutes Way Forward
• 12:30 - 13:30 Lunch
• 13:30 - 16:00 Theme: Overall Design approach: requirements
  • The aim here is to create a final list of requirements on what we expect as the outcome of the revision process. This is a "manifest" which lists the effects we want to achieve for end users, for vendors, and for ourselves as a maintenance agency. This listing will serve as a guideline for the coming work, and will enable us to measure rate of success at the end of the process.
• 16:00-16:30 Concluding remarks [George, Markus]