From rinehuls@access.digex.net Mon Aug 11 22:49:21 1997 Received: from access1.digex.net (qlrhmEbBUV1EY@access1.digex.net [205.197.245.192]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id WAA16536 for ; Mon, 11 Aug 1997 22:49:16 +0200 Received: from localhost (rinehuls@localhost) by access1.digex.net (8.8.4/8.8.4) with SMTP id QAA22919 for ; Mon, 11 Aug 1997 16:49:08 -0400 (EDT) Date: Mon, 11 Aug 1997 16:49:08 -0400 (EDT) From: "william c. rinehuls" To: sc22docs@dkuug.dk Subject: SC22 N2551 - Draft SC22 Business Plan - PLENARY ACTION ITEM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE ____________ beginning of title page _____________________________ ISO/IEC JTC 1/SC22 Programming languages, their environments and system software interfaces Secretariat: U.S.A. (ANSI) ISO/IEC JTC 1/SC22 N2551 August 1997 TITLE: Draft JTC 1/SC22 Business Plan SOURCE: Secretariat, ISO/IEC JTC 1/SC22 WORK ITEM: N/A STATUS: Please note that this Business Plan will be considered under Agenda Item 11.7 at the AUgust 1997 SC22 Plenary. CROSS REFERENCE: N/A DOCUMENT TYPE: Draft Business Plan ACTION: To SC22 Member Bodies for review. Address reply to: ISO/IEC JTC 1/SC22 Secretariat William C. Rinehuls 8457 Rushing Creek Court Springfield, VA 22153 USA Tel: +1 (703) 912-9680 Fax: +1 (703) 912-2973 email: rinehuls@access.digex. net ___________________ end of title page; beginning of draft plan _________ TO: SC22 SUBJECT: Business Plan for JTC 1/SC22 Following is my draft of an SC22 Business Plan for discussion at next week's plenary under agenda item 11.7. I have left in brackets the explanations of each item in the plan, but will delete them in the final copy. Note that I have no text for the last item; I would like help from the plenary to determine priorities. Robert H. Follett Chairman, JTC 1/SC22 ******************** Draft Business Plan Follows ******************** [Note: All items in brackets should be deleted before submission.]=20 =20 BUSINESS PLAN FOR JTC 1/SC22, Programming Languages, their Environments, an= d System=20 Software Interfaces =20 [Note: Currently missing reports from WG3 and WG4]=20 PERIOD COVERED: December 1996 - September 1997=20 =20 =20 SUBMITTED BY: Robert H. Follett, Chairman =20 =20 1. MANAGEMENT SUMMARY:=20 =20 =20 1.1 JTC 1/SC22 STATEMENT OF SCOPE: Standardization of programming languages, their environments and systems software interfaces such as:=20 *=09specification techniques; and * common facilities and interfaces. Excluded: specialized languages or environments assigned to the program of work of another Subcommittee or Technical Committee 1.2 PROJECT REPORT=20 SC22 has at total of 53 assigned projects which, after subdivisions, result in 94 identifiable items of work (projects and subprojects). Of these, 53 are currently active in development and 41 are published standards, technical reports and amendments that are in maintenance mode.= =20 None are planned for withdrawal at this time.=20 The SC22 Secretariat's report contains a complete listing of these projects and related target dates.=20 1.3 COOPERATION AND COMPETITION [Included here an analysis of the key players in the area pertaining to JTC 1 or its SC, in order to highlight any possibility for cooperation with other JTC 1 SC=92s, ISO TC=92s or Industry Consortia/Fora. Also indic= ate agreed division of work or opportunities for projects of a complimentary nature. Identification of standards initiatives or de-facto standards shall be made that may be in direct competition with some of the projects.] Ada (WG9): There are two major professional societies in this area: the Special Interest Group on Ada (SIG) of the Association for Computing Machinery and Ada-Europe. The semi-annual meetings of WG9 are scheduled to coincide with the major conferences organized by these two groups. Informal but close cooperation with SIGAda is maintained by the convener. The UK Head of Delegation to WG9 is also an officer of Ada-Europe.=20 There is one major vendor consortium, the Ada Resource Association (ARA).= =20 Formal liaison with ARA is maintained. WG9 is looking for opportunities to transpose de facto standards from the ARA. The United States Department of Defense (DOD), Ada Joint Program Office (AJPO) has a continuing interest in the Ada language. Liaison is assured because AJPO funds the convener to serve in his position. In addition, liaison and/or consultation are applied as appropriate with WG4 (Cobol), WG11 (Language-Independent Standards), WG14 (C Language), WG15 (POSIX), WG16 (LISP), WG21 (C++), SC21/WG3 (IRDS), the SC22 Java Study Group, and the IEEE Computer Society Software Engineering Standards Committee.=20 C (WG14): Where appropriate, WG14 has established active liaisons with other SC22 working groups.=20 C++ (WG21): =20 WG 21 has liaisons with other SC22 working groups on C, POSIX and Internationalization. With regard to the latter, it is using the WG20 guidelines on extended characters. It also takes account of the recommendations from WG11 on cross-language standards.=20 Fortran (WG5): WG5 cooperates closely with the ANSI NCITS/J3 Fortran Technical Committee, to whom it has delegated the technical development of Fortran 2000 as well as the maintenance of Fortran 95 (IS 1539-1:1997). There is also close contact with the industry-driven High Performance Fortran Consortium, with many members of the HPF Consortium also being members of J3 and/or WG5. Many of those responsible for the development of commercial Fortran compilers are members of J3 and/or WG5. Other important liaisons are those with IFIP WG2.5 (Numerical Software) and ISO/IEC JTC1/SC22/WG20 (Internationalization).=20 Internationalization (WG20): =20 WG20 works closely with CEN/TC304 which is developing an ordering standard for European languages and also developed ENV 12005 which is similar to CD 14652 on cultural conventions, but is limited to European conventions.=20 Language Independent Projects (WG11): The WG11 documents are mainly produced to be used by other programming language committees. Therefore, WG11 maintains liaisons with many of the SC22 WGs.=20 Lisp (WG16): The WG16 activities that produced ISLISP were done by collaborative work of six regularly participating P-member nations; France (Convenor), United States (Project Editor), Canada, Germany, Japan, and United Kingdom. These nations had close collaboration with their local Lisp communities; for example, EuLisp community in European nations, X3J13 in United States, and IPSJ-SIGSYM community in Japan. The ISLISP design reflected the experiences of COMMON LISP, EULISP, LE LISP, and SCHEME, and took into account common practices in the Lisp community. ISLISP is a small Lisp, but it is designed with extensibility in mind, trying also to keep compatibility with existing Lisp dialects. ISO/IEC ISLISP, ANSI COMMON LISP and ANSI/IEEE SCHEME are co-existing and complementary in the Lisp community, since they have their own distinctive features in languages, systems, and applications.=20 Modula-2 (WG13): WG13 cooperates with as many compiler writers as possible, and contacts with industry work quite well. Where appropriate, WG13 has established contact with other SC22 working groups. PCTE (WG22): The most active liaisons maintained by WG22 have been with ECMA/TC33, where most WG22 members are also ECMA/TC33 members, and with ISO/IEC SC7/WG11. In the latter case, the WG22 liaison in SC7/WG11 is the project editor of the subproject dealing with the definition of rules to derive PCTE Schema Definition Sets from the standard models adopted by WG11 (basically CDIF models).=20 POSIX (WG15): WG15's work is done with close cooperation of The Open Group (TOG, aka X/Open), Usenix, Europen, and other UNIX organizations. The bulk of development for work brought into WG15 has been done in cooperation with IEEE's Portable Applications Standards Committee. TOG is a category "C" liaison, and authorized to submit PAS specifications in areas relevant to WG15's work. While most "UNIX" type systems conform to the specifications from WG15 (POSIX), there is significant competition from de-facto standards, typically "Windows 95" and "NT".=20 Prolog (WG17): WG17 cooperates with the whole Prolog community. Where appropriate, WG17 has established contact with other SC22 working groups. VDM-SL (WG19): The VDM group involves collaborative work of six participating P-members:= =20 UK, Denmark, Holland, France, Japan and the USA. The VDM-SL standardization work was also supported by the EU by various grants.=20 Z Notation (WG19): The work of the Z group involves the participation of members from the UK, USA, Australia, Japan, Germany, France, Italy, Brazil, Canada, and Ireland. Members are drawn from industry, government, and universities.=20 The Z standardization work has been assisted by grants from industrial and government agencies in the USA and Europe.=20 2.0 PERIOD REVIEW=20 =20 [This is the report from the chair of JTC 1 and or one of it=92s SC=92s highlighting project progress, special considerations and or needs which were or were not met. This is where generic or specific comment from the chair is to be made highlighting special items requiring visibility and action. The review shall focus on the following elements: ] =20 2.1 MARKET REQUIREMENTS, =20 [Identification of key market trends, needs (anticipatory standards or = =20 voids) and determining factors for JTC1=92s success in this area. ] SC22 standards are produced in response to market requirements covering extensive and diverse areas of the marketplace. While press attention is primarily devoted to newer language and interface areas, it is important not to overlook the importance of older technologies where there is significant user investment. Adding current technological capabilities to older programming languages can provide important economic benefits to current users. Some specifics on market requirements in particular SC22 areas follow.=20 Ada: =20 The most fundamental change in the market has been action by the US Department of Defense (DOD) to drop its "mandate" of Ada in all military systems. The choice of language to be used will now be made by each individual development program. Certain segments of the DOD remain committed to favoring Ada, notably the real-time, embedded systems community. DOD has committed to increase funding to support the activities of the Ada Joint Program Office.=20 C:=20 The revision to ISO/IEC 9899 is in response to user community pressure and to implementers concerns to keep current with today's programming trends and market. The working group believes that evolution of Object Oriented programming, numerical extensions that were proposed by the US committee, internationalization, advancements in character set standardization, cross-language standards and cross-language bindings all need to be considered in the revised standard. Most of these issues where not considered during the technical discussions for the current ISO C Standard. C++:=20 More than one million people are estimated to be programming in C++.=20 This marketplace is very eager for the C++ international standard to be completed. Fortran:=20 Fortran is still the language of choice for the majority of scientific and technological programming. There are now signs of growing use of Fortran 90, and the recent introduction of two commercial subsets designed for educational use is generating increased interest in Fortran from the higher education sector. This growth in interest means that it is important that the development of the language can react quickly to market requirements, while still ensuring that the safeguards of full international review are maintained. (See Strategies below.)=20 One perceived market requirement is for a form of conditional compilation to simplify the transfer of programs between many platforms. This is being processed as an additional Part of the Fortran Standard, as it is not currently intended that it should be a requirement for all Standard-conforming compilers. It is expected that the draft CD will be submitted for its first approval ballot later this year. WG5 has developed a database of requirements for future versions of Fortran during the last five years since the publication of Fortran 90, and this formed the basis of a year-long analysis of the features which should be added to the base language in the next revision, informally known as Fortran 2000.=20 Internationalization:=20 With the proliferation of PCs and the emergence of the world wide web, internationalization has become a very important factor in the creation of programs and thus in programming languages. Language Independent Projects:=20 The market requirement for these standards is more indirect than explicit. Several ISO/IEC standards make reference to these documents and they are useful in promoting commonality and interoperability among these standards. LISP:=20 The working group has investigated several areas, e.g., modules, internationalization, graphics, and binding facilities, and has taken into consideration several contributions from member bodies. None had sufficient maturity for inclusion into the ISLISP standard published this year. Some of them, in particular a C language binding, should be included in a subsequent revision.=20 Modula-2:=20 Strong market demands from the Modula-2 community have resulted in the development of additional parts to the base standard. There was popular demand for Object Oriented Extensions and we anticipate that the current development of Part 3 will lead to a uniform way of handling these extensions in available compilers. There was popular demand mainly from academia for Generics which was met with Part 2. Finally, the requirement for interfacing to libraries in the C language is being handled by the development of a Type 3 Technical Report. PCTE:=20 The PCTE market is a subset of the Repository market. Today, PCTE addresses well the problem of providing a standard framework upon which complete repository products can be built. Like in many other domains of the software industry, the approval of a standard at the ISO level is not sufficient to make it universally adopted. A major condition for its acceptance in the industry is the wide availability of implementations compliant with this standard. Today this criteria is only partly met;=20 there are available implementations but they have not yet managed to be the leading technology on this market. In fact, there is still no leading technology as large software vendors seem to still believe in proprietary solutions in this domain and compete against each other without adhering to standards. =20 The repository market is relatively small. There is the same ratio between the market of databases in general and the market of repositories,as between the market of end user applications and the market of software development tools. The relatively small size of this market makes the adoption of PCTE technology grow slowly. Nevertheless, despite this aspect, the need for repositories is now fully recognised and most software development organisations are now convinced that they need a repository. PCTE based repository products are currently used at more than 100 different sites in Europe, America and Asia (principally Japan).= =20 POSIX:=20 Conformance to POSIX standards is taken for granted by a wide variety of private and public sector users for "UNIX" systems procurement. All major implementations of "UNIX" claim conformance to the POSIX standards.=20 Prolog:=20 The only market requirement beyond the base standard identified by the Prolog user community is the definition of a module facility. This is being developed as Part 2 of the standard.=20 VDM-SL:=20 The increase in the need for safety-critical systems will imply increased interest in formal languages. Regarding VDM-SL in particular, requirements have been identified for some sort of modularization and for addition of an object oriented structure to the language. In the latter area, a European group is working in this area and incorporation of this work may expedite the production of Part 2 of the standard. Z Notation:=20 The increasing interest in safety-critical systems and in secure systems suggests a continuing interest in the use of Z notation. Industrial users of the Z notation continue to exert pressure for a standard and are contributing participants to the development work.=20 2.2 ACHIEVEMENTS,=20 [ Highlight accomplishments reference work program, target dates, =20 corrective action and special circumstances. . ] =20 * Ada: DIS ballots completed on two additional Ada packages;=20 * C: CD Registration of the revision to IS 9899 on C;=20 * C++: Completion of the Final CD 14882 ballot on C++.=20 * Fortran: The latest revision of the Fortran standard has been approved and is being published; * Internationalization: TR 11017 on the Framework for Internationalization has been forwarded for publication; * Internationalization: The first CD 14651 on International String Ordering has been completed; * Internationalization: Concurrent Registration and CD 14652 ballot circulated for Specification of Cultural Conventions;=20 * Internationalization: Completion of DTR 10176 ballot adding internationalization issues to the TR on Guidlines for the Preparation of Programming Language Standards.=20 * LISP: Publication of IS 13816 on ISLISP;=20 * Modula-2: Parts 2 and 3 of the Modula-2 standard, IS 10514, progressed to the DIS stage;=20 * PCTE: Amendments for object-oriented extensions and fine grain objects for all three parts of IS 13719 on PCTE have been forwarded for publication;=20 * POSIX: Registration of amendments to POSIX Part 1, IS 9945-1, for realtime extensions;=20 * POSIX: DIS 15068-2 on POSIX Software Administration approved;=20 * POSIX: Final CD ballot circulated for revision of IS 13210 on Requirements and Guidelines for Test Methods Specifications and Test Method Implementations for Measuring Conformance to POSIX Standards; * Prolog: CD Ballot completed on Part 2 of IS 13211 on Prolog;=20 2.3 RESOURCES =20 [ Status of resource availability/commitment and the impact on projects, = =20 completion dates and priorities for the new work period. ] =20 It is increasingly difficult for standards participants to obtain the necessary funding for standards development activities. Nonetheless, all currently active SC22 projects continue to have sufficient support.=20 =20 =20 3.0 FOCUS NEXT WORK PERIOD =20 [An identification of the direction and focus for the new work period =20 leading up to the next plenary session. This section shall include =20 information on following elements. ] 3.1 DELIVERABLES:=20 [This shall indicate specific deliverables expected in the work period on a project level. Note that this work period will be from September 1997 through May 1998 since the next JTC1 plenary is the first week in June 1998. ] =20 * Ada: Final approval of DIS 13813 and DIS 13814 on Ada packages;=20 * C: Circulation of a CD ballot on the revision to IS 9899 on C;=20 * C++: Circulation of FDIS 14882 on C++.=20 * Fortran: Completion of work on the Fortran Type 2 Technical Reports;= =20 * Fortran: Final CD ballot on Fortran Part 2, Varying length character strings;=20 * Internationalization: Circulation of Final CD 14651 ballot on International String Ordering;=20 * Internationalization: Registration and completion of first CD 14652 ballot on Specification of Cultural Conventions;=20 * Internationalization: TR 10176 ballot on a revision to Guidlines for the Preparation of Programming Language Standards, adding internationalization issues to the TR;=20 * Language Independent: Progression of Part 2 of IS 10967 on Language Independent Arithmetic: Elementary Numerical Functions to the DIS level;=20 * Language Independent: Circulation of a PDTR ballot on Guidelines for Language Independent Service Specifications;=20 * Modula-2: Approval and publication of Part 2 and Part 3 of IS 10967 on Modula-2;=20 * PCTE: Completion of work on all four parts of IS 13719 on PCTE, including production of a new edition incorporating all amendments and corrections;=20 * POSIX: Completion of PDAM ballot on amendments to POSIX Part 1, IS 9945-1, for extensions to the base and for realtime extensions;=20 * POSIX: Circulation of DAM ballot on amendment to POSIX Part 1, IS 9945-1, for Protocol Independent Interfaces;=20 * POSIX: Completion of PDAM ballot on additional utilities for IS 9945-2, Shell and Utillities for POSIX;=20 * POSIX: Circulation of DIS ballot on Part 3 to IS 15068, POSIX System Administration: User & Group Account Management;=20 * POSIX: Circulation of FCD ballot on Part 4 to IS 15068 POSIX System Administration: Printing Interfaces;=20 * POSIX: Circulation of FDIS ballot for revision of IS 13210 on Requirements and Guidelines for Test Methods Specifications and Test Method Implementations for Measuring Conformance to POSIX Standards;=20 * POSIX: Circulation of PDAM 1 to IS 14515-1 on Realtime Extensions to the POSIX System Interface Test Methods;=20 * POSIX: Circulation of PDISP ballot on POSIX Supercomputing Applications Environment Profile;=20 * POSIX: Circulation of PDISP ballot on POSIX Real Time Application Support Profile;=20 * Prolog: Circulation of Final CD Ballot on Part 2 of IS 13211 on Prolog;=20 * Z Notation: Circulation of a CD 13568 ballot on Z Notation;=20 =09 3.2 STRATEGIES:=20 [A statement or statements related to strategic approaches required to =20 accomplish goals and objectives. ] =20 An important SC22 strategy is to use a variety of development methods in order to produce timely standards and make the most efficient use of standards development resources. SC22 has used the following methods:=20 =09a) Assignment of development responsibility to a National Body with a strong development committee, with a requirement for appropriate synchronization of the international and national comment processes so that all comments are appropriately considered in the production of the standard;=20 =09b) Joint or co-located meetings of SC22 WGs with NB or liaison organization development committees working in the same area, to produce standards with identical text;=20 =09c) Invitation to NB or liaison organizations to fast-track documents in the area of SC22 responsibility;=20 =09d) Development within traditional working groups.=20 The SC22 Working Group on Fortran is implementing a strategy allowing it to react effectively to new requirements without causing unacceptable delay to the processing of the main Standard. Certain high priority new features which were too late to be included in the last revision are being processed as Type 2 Technical Reports, with a guarantee that the feature will be incorporated unaltered in the next revision of the base Standard unless experience in implementation or use shows that a modification is necessary. The intent of this procedure is to encourage implementors to add these features to their compilers without waiting for the next revision of the main language Standard. Two such TRs are about to be submitted for their final DTR approval ballots, while a third is currently in the process of being balloted for PDTR approval.=20 3.2.1 RISKS =20 [ A definition of potential risk(s) involved with the strategy and the= =20 impact to the project or JTC 1. Risk(s) shall be defined for each =20 strategy to be employed/included. ] =20 The risks associated with all the above methods are:=20 =09a) Continuing commitment of participants and their sponsors throughout the development process, especially in a time of organizational downsizing;=20 =09b) Continuing commitment of sufficient National Bodies where the development work is done within WGs. This risk is significantly reduced when development is done outside a WG;=20 =09c) Dependence on other organizations for technical expertise, development work, and project editing when development is done outside a WG;=20 =09d) Obtaining consensus when conflicting implementations have been produced prior to the development of the standard.=20 3.2.2 OPPORTUNITIES=20 [ An explanation of the related opportunity(s) afforded by the strateg= y =20 and or envisioned due to trends and market developments. ] =20 Extensive use of electronic distribution techniques provides an opportunity to speed up the development process and reduce the requirement for as many meetings that add considerable expense to standards development participation.=20 =20 3.3 WORK PROGRAM PRIORITIES =20 [Based on the scope, market needs, strategies, resource availability and = =20 status of existing projects, provide an overview of the work program =20 priorities in capsule form. This should be as generic as possible with =20 rationale provided to support the determination by the group involved. ] =20 ??? ******************** End of Draft Business Plan ******************** __________________________ end of SC22 N2551 _____________________