• Assignments

Final Report Organization

This page conveys the administrative details of the work on the Draft Final Report.

Planning and Deadlines

Assignments

Below are two tables conveying the tasks for the URW3 Final Report and their respective assigned group members. The columns in the table indicate sections (S1 - S7). Section 5 is represented by the use case subsection numbers (501 - 516).

The rationale behind the initial assignment was to aggregate the authors as much as possible, while still providing a reasonable balance or work to be done and a feasible framework for realizing the planning above within its tight timetable. Although we'd encourage people to accept their respective assignments, URW3 members are free to change them until Jan 25.

OBS:

 A -> Author
 C -> Contributor
 E -> Coordinator

Editing Team

• Paulo Costa
• Mitch Kokar
• Trevor Martin
• Thomas Lukasiewicz

Summary of the Tasks

Sections

People assigned to sections (tasks marked as Sx in the URW3 Final Report Assignment Table) are supposed to coordinate among themselves for the writing and revision of their respectively assigned sections. Generally, each section has at least two people plus a member of the editing team assigned to it, so one can review the writings of the other. Each subgroup is expected to present a summary of their work during the upcoming URW3 Telecons.

Use Cases and Respective Appendices

People assigned to the use cases (tasks marked as 5xx in the URW3 Final Report Assignment Table) are supposed to coordinate among themselves for the writing and revision of their respectively assigned use cases. More specifically, they are required to write and review:

• 1) One or two paragraphs with a small description of the use case in section 5 (subsection 5xx); and

• 2) The completion of the use case detailed description in Appendix A (section Axx).

In some cases, there is a clearly assigned use case author and a reasonably well defined scenario (e.g. the 5.1 Discovery use case), so the workload would be mostly restricted to brief discussions, and some writing and editing. There are also cases without a clear author but with a reasonably well defined use case scenario (e.g. the 5.2 wine sweetness use case), which would probably demand a greater deal of coordination and discussions in order to realize the writing and reviewing within the timeframe. Finally, there are cases in which we do not have a clear author or scenario (e.g. 5.3 "other use case scenarios from the URW3"), which will demand a greater deal of coordination but would also allow for more flexibility from the subgroup on what should really be included (or not) in the final report. Each subgroup is expected to present a summary of their work during the upcoming URW3 Telecons.

Addendum: Timeline for the last two weeks

In the a few hours we are supposed to freeze the final report wiki and start working on the Final Report's HTML version. Given the proximity of the XG deadline and the need to move forward with our conclusions and recommendations, we in the editing team have discussed the options and would like to propose the following timetable for us to discuss in this upcoming telecon:

2/20 telecon:

• All must read the report before the telecon (we assume most of you already did it, this is just an administrative reminder).
• We are supposed to wrap up the Use Cases, so we might want to give it a one-by-one status report and then decide which ones to keep and what should be included as a minimum configuration for every UC. One important thing to remind is that UCs, although important, are there just to support our conclusions and recommendations, so it it time to move forward on this.
• Still regarding the UCs, we'd like to suggest that we discuss on what should be in the appendix. Maybe we should just leave one or a couple of UCs in there as a reference for future work and leave all UCs that have a minimum set of information restricted to section 5.
• Regarding the other sections, all of us are supposed to go through it and critique/suggest/collaborate. The EDT suggests that we define a deadline for doing that no later than Feb 24. After this deadline, we would assume everyone is happy with the current status and will be willing to approve it in the final report approval meeting (Mar 5 Telecon).

2/24 (Sunday):

• For practical purposes and with the deadline in mind, the EDT proposes that the Wiki becomes uneditable, so we can focus on the HTML version of the report and start to defining the report's definitive configuration
• It is important to remind that everyone in the group will still have a week for collaborating, but that must be done via the EDT so to avoid versioning nightmares.

3/02 (the other Sunday):

• We should be basically done by then, so no more changes will be made to the Final Report that will be discussed on the final telecon.
• This is the limit for us in the editing team to post a final version of the HTML Report (so everyone will have a reasonable time for reading it before the telecon).

3/05 (last telecon)

• All are expected to read the HTML report before the telecon (again, adm stuff).
• Unless a better format is proposed, we plan to go over the report section by section and approve it.

Once again, this is our suggestion for making sure we as a group could translate all of our 1-year discussions into paper within the upcoming two weeks. We would like to reinforce the general idea of wrapping up the UCs and other sections so to focus on the most important part of the report, which are the conclusions and recommendations.

• Thank you all for your invaluable support.