WG16 Business Plan/Convener Report BUSINESS PLAN FOR JTC 1/SC22 WG16 PERIOD COVERED: July 2003 - July 2004 SUBMITTED BY: Taiichi Yuasa Convenor, ISO/IEC JTC1/SC22/WG16 Kyoto University, Kyoto 606-8501, Japan 1. MANAGEMENT SUMMARY 1.1 JTC 1/SC22 WG16 Statement of Scope Development and maintenance of ISO/IEC Standards related to Lisp. 1.2 Project Report 1.2.1 Completed Projects Preparation of a draft technical corrigendum and a draft corrected report. 1.2.2 Projects Underway We have just finished the above project. 1.2.3 Projects Withdrawn None over this period. 1.3 Cooperation and Competition No liaison with any JTC1 group. No competition with any JTC1 group. 2. PERIOD REVIEW 2.1 Market Requirements No market requirement change were noted over this period. 2.2 Achievements Finished work for producing a draft technical corrigendum and a draft corrected report. 2.3 Resources Resources to address defect reports are secured (FR and US, and GB and JP as backup). 3. FOCUS NEXT WORK PERIOD Register the draft technical corrigendum and the draft corrected report as official documents of ISO/IEC JTC1. 3.1 Deliverables The drafts can be downloaded from the following Web page. http://ryujin.kuis.kyoto-u.ac.jp/~yuasa/lispwg/ 3.2 Strategies Japanese WG on Lisp Standardization chaired by T. Yuasa has registered ISLISP as JIS standard (JIS X 3012:1998) translating the English standard (ISO/IEC 13816:1997). In this process they found several (minor) errors in the original documents, and also, they found several places that need further refinements. They collected corrections for the standard and produced the first draft technical corrigendum and the first draft corrected report. They finished refining these documents, sent to WG 16 members for their support to go forward to SC22 for approval. The drafts have recently been approved. The next step is to register these documents as official documents of ISO/IEC JTC1. 3.2.1 Risks None for the work planned over the next period. 3.2.2 Opportunities Discussion on the draft technical corrigendum and the draft corrected report have been done by WG 16 members via emails. 3.3 Work Program Priorities Submission of a technical corrigendum and a corrected report to SC 22 for approval. 4. ADMINISTRATIVE INFORMATION 4.1 WG## Liaisons 5. SC22 PLENARY ACTIONS RELATED TO WG16 None.