ISO/ IEC JTC1/SC22 N3307

From:ISO/IEC JTC 1/SC22
Programming languages, their environments and system software interfaces
Secretariat:  U.S.A.  (ANSI)
 
ISO/IEC JTC 1/SC22 N3307
 
TITLE:
JTC 1/SC 22/WG 16 Business Plan and Convenor's Report

DATE ASSIGNED:
2001-09-10
 
SOURCE:
SC 22/WG 16 Convenor (P. Parquier)

BACKWARD POINTER:
N/A
 
DOCUMENT TYPE:
Other document (Open)

PROJECT NUMBER:
N/A
 
STATUS:
This document will be reviewed at the upcoming SC 22 Plenary under Agenda
Item 8.9 pending the approval of its addition to the agenda.

ACTION IDENTIFIER:
FYI
 
DUE DATE:
  
DISTRIBUTION:
Text

CROSS REFERENCE:
 
DISTRIBUTION FORM:
Open
 
Address reply to:
ISO/IEC JTC 1/SC22 Secretariat
Matt Deane
ANSI
25 West 43rd Street
New York, NY  10036
Telephone:  (212) 642-4992
Fax:             (212) 840-2298
Email:  mdeane@ansi.org

_______end of cover page, beginning of report____________

BUSINESS PLAN AND CONVENER'S REPORT: ISO/IEC JTC1/SC22/WG16 (LISP)

PERIOD COVERED: 
September 2000 - August 2001

SUBMITTED BY: 
Convener, ISO/IEC JTC1/SC22/WG16
Pierre Parquier
ILOG
9 rue de Verdun
94253 Gentilly Cedex, France
Phone: +33 1 49 08 35 86
Fax: +33 1 49 08 35 10
Email: parquier@ilog.fr <mailto:parquier@ilog.fr>


1. MANAGEMENT SUMMARY

1.1 JTC1/SC22/WG16 STATEMENT OF SCOPE 

  Development and maintenance of ISO/IEC Standards related to Lisp.
  Its single project is 22.23 "programming language ISLISP", which
  produced ISO/IEC 13816:1997.

1.2 PROJECT REPORT 

1.2.1 COMPLETED PROJECTS 

  None over this period.

1.2.2 PROJECTS UNDERWAY 

  Project 22.23 produced ISO/IEC 13816:1997.  The project has not 
  yet discussed the five-year revision.  The project has started a list of 
  unofficial defect reports.  

  Here are a few notes on national activity related to project 22.23:
  
1) ISLISP in Japan

  Japanese WG on Lisp Standardization chaired by T. Yuasa
  registered ISLISP as JIS language translating the English
  standard (JIS X 3012:1998). 

  In this process they found several (minor) errors in the
  original documents, and also, they found several places
  that need further refinements.

2) Implementations

  OpenLisp interpreter and compiler by C. Jullien  
  (Eligis),

  TISL interpreter and compiler by N. Izumi and T. Ito
  (TISL: Tohoku university ISLISP system)

  A system developed by Oki Corp under supervision by T. Yuasa
  (Interpreter and compiler for a specific VM)

  TISL/P interpreter and compilier by N. Izumi and T. Ito
  (An extension of TISL to introduce a package system)

1.2.3 NEW PROJECTS 

  None over this period.

1.2.4 CANCELLED PROJECTS 

  None over this period.

1.3 COOPERATION AND COMPETITION 

  No liaison with any JTC1 group.  No competition with any JTC1 group.

  Related standards are ANSI COMMON LISP and IEEE SCHEME.  
  All are complementary in the Lisp community.

2.0 PERIOD REVIEW 

2.1 MARKET REQUIREMENTS 

  No market requirement change were noted over this period.

2.2 ACHIEVEMENTS 

  Informal investigation of the five-year revision content.
 
  Informal discussiion on infrastructure of WG work to produce the 5-year
revision.

2.3 RESOURCES 

  Resources to address defect reports are secured (FR and US, and GB
  and JP as backup).

  Project Editor: Kent M. Pitman (US)
  Associate Project Editors: Julian Padget (GB), Taiichi Yuasa (JP)

3.0 FOCUS NEXT WORK PERIOD 

  Produce a five-year revision.

3.1 DELIVERABLES 

  Perhaps sumbit the five-year revision (convener is not sure yet about the
timeframe required by JTC1 rules).

3.2 STRATEGIES 

  Promote distant collaborative work instead of calling face-to-face
meetings.

3.2.1 RISKS 

  None for the work planned over the next period.

3.2.2 OPPORTUNITIES 

  Address new market requirements for Lisp thanks to the 5-year revision.

3.3 WORK PROGRAM PRIORITIES 

  None for the work planned over the next period.

4. OTHER ITEMS 

4.1 POSSIBLE ACTION REQUEST AT FORTHCOMING PLENARY

  None.

4.2 RECENT MEETING

  15th meeting: 1996 November, Paris, France.
  14th meeting: 1996 March, Bath, United Kingdom.

4.3 FUTURE MEETINGS

  No meeting planned for the next period, if distant collaborative work goes
well.

5 DRAFT RESOLUTIONS FOR SC22

  None.