From jwagener@trc.amoco.com Tue Sep 15 23:55:23 1992 Received: from [137.66.12.254] by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8) id AA24824; Tue, 15 Sep 92 23:55:23 +0200 Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA15160; Tue, 15 Sep 92 16:55:23 -0500 Received: from [129.230.11.2] by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA07218; Tue, 15 Sep 92 16:55:21 -0500 Received: from trc.amoco.com (apctrc.trc.amoco.com) by netserv2 (4.1/SMI-4.0) id AA12426; Tue, 15 Sep 92 16:53:41 CDT Received: from crmac1 by trc.amoco.com (4.1/SMI-4.1) id AA12259; Tue, 15 Sep 92 16:53:37 CDT Date: Tue, 15 Sep 92 16:53:37 CDT Message-Id: <9209152153.AA12259@trc.amoco.com> From: Jerrold L. Wagener To: SC22WG5@dkuug.dk Subject: "I" project proposal for the 1995-96 revision X-Charset: ASCII X-Char-Esc: 29 To X3J3 and WG5 - Attached is the text of the project proposal (SD-3) for the 1995-96 revision, initially drafted at the Aug X3J3 meeting and following that meeting submitted to X3/SPARC for preliminary review; I expected that there would requests for changes, additional information, etc. SPARC met last week, and though I have not yet had an "official" report from the meeting, here is the gist of an unofficial report from a SPARC member that called me about something else. 1. There is no opposition to the proposal within SPARC, and it looks like it will receive early approval (if the problem in 2. is solved). As of now, there is no request for any changes to the proposal (though the resolution of item 2. might involve a name change). 2. SPARC is uncomfortable about the name of the language. The name of ISO/IEC 1539:1991 is "Fortran"; the name of ANSI X3.9-1978 is "Programming Language FORTRAN"; the name of ANSI X3.198-1992 is (will be) "Programming Language Fortran 90". The concern is that when this standard is completed the US will have two standards, one called "Fortran" and the other called "Programming Language FORTRAN". (I've already pointed out that the all-caps of FORTRAN 77 saves us, but I'm not sure if that has been taken seriously.) Everybody seems to think this is a somewhat silly problem, and that it won't be a stumbling block, but for now this is what the worry is. I'll keep you informed as to how this progresses, and of course would welcome any suggestions you might have regarding the name or any other aspect of the proposal. (The proposal text follows.) Jerry ------------------------------------------------------- RIS Project Proposal for Fortran 9x X3J3/92-188 1. Identification of Proposed Project Title: Fortran 9x Proposer: X3J3 Date Submitted: 31 August 1992 Project Type: I 2. Justification of Proposed Standard Needs Fortran 90 (ISO/IEC 1539:1991 and ANSI X3.198-1992) maintenance activities have produced a number of corrections, clarifications, and interpretations. Second, certain restrictions of Fortran 90 should be removed in order to better serve the Fortran user community. And third, there is pressing new functionality (possibly parallel processing, for example) for which Fortran users badly need standards. Therefore, ISO/IEC JTC1/SC22/WG5 has decided to produce a revision of ISO/IEC 1539:1991 in the 1995-96 time frame. Recommended Scope of Standard WG5 and X3J3 are in agreement that this revision should be done as an X3 RIS project, with the result replacing both ISO/IEC 1539:1991 and ANSI X3.198- 1992. Removing Fortran 90 defects and restrictions will have the highest priority. New functionality will be based on requirements identified in accordance with the WG5 strategic plan for Fortran standardization, WG5/SD-4 (attached), and is expected to be minimal for this revision. 1995 is the proposed target period for CD submittal. Existing Practice in Area of Proposed Standard Existing practices in this area comprise the use of ISO/IEC 1539:1991, ANSI X3.198-1992, ANSI X3.9-1978, and various auxiliary formal or defacto standards such as those of X3H5, POSIX, and HPFF. Expected Stability of Proposed Standard: expect replacement about the year 2000 3. Description of Proposed Project Type of Document: standard Definitions of Concepts and Special Terms: none Expected Relationships with Approved X3 Reference Models The proposed standard will conform to the Fortran Reference Model described in the X3/ SD-1B. It is not expected to conflict with any reference models. Recommended Program of Work The recommended program of work is for X3J3 to function as the primary development body as described in the attached WG5/SD-4; WG5 recommended that X3J3 be the primary development body in resolution V9 (Victoria, July, 1992). The schedule and scope of this revision are described in WG5/SD-4, as are the specific responsibilities of WG5 and the primary development body. Resources - Individuals and Organizations Competent in Subject Matter The resources of X3J3 and WG5 are available for this project. Approximately 30 individuals attend each X3J3 meeting and, with some overlap in membership, a similar number attend each WG5 meeting. This is expected to constitute adequate resources to produce the proposed revision. Recommended X3 Development Technical Committee: X3J3 Anticipated Frequency and Duration of Meetings It is anticipated that X3J3 will meet four times per year, five days per meeting, during the development of this revision, and WG5 will have at least one five-day meeting per year. Target Date for dpANS to X3 (Milestone 10) Milestone 10 is not applicable to an RIS project; 1995 is the target date for submittal as a CD. Estimated Useful Life of Standard: approximately five years 4. Implementation Impacts Impact on Existing User Practices and Investments The proposed revision will be substantially, if not completely, upwardly compatible with Fortran 90, thereby protecting current investments; therefore, the impact on users should be minimal. Impact on Supplier Products and Support Suppliers will welcome corrections and clarifications to the Fortran standard, and many will have already removed various Fortran 90 restrictions from their products. Since the amount of new functionality is expected to be small, impact on suppliers also should be minimal. Techniques and Costs for Compliance Verification As with previous versions of the Fortran standard, X3J3 will not verify or monitor compliance to this standard. Various other organizations provide such services. Legal Considerations: none known or expected 5. Closely Related Standards Activities Existing Standards: ISO/IEC 1539:1991 and ANSI X3.198-1992 X3 Standards Development Projects: X3H5 - Fortran 90 binding X3/SPARC Study Groups: none Other Related Domestic Standards Efforts: POSIX, HPFF ISO Standards Development Projects: 1539.1 - ISO Varying String Other Related International Standards Development Projects: none Recommendations for Coordinating Liaison: none Recommendations for Close Liaison: none