From jwagener@amoco.com Mon Jul 19 04:08:06 1993 Received: from interlock.amoco.com by dkuug.dk with SMTP id AA07520 (5.65c8/IDA-1.4.4j for ); Mon, 19 Jul 1993 16:07:40 +0200 Received: by interlock.amoco.com id AA10702 (InterLock SMTP Gateway 1.1 for SC22WG5@dkuug.dk); Mon, 19 Jul 1993 08:59:19 -0500 Received: by interlock.amoco.com (Internal Mail Agent-2); Mon, 19 Jul 1993 08:59:19 -0500 Received: by interlock.amoco.com (Internal Mail Agent-1); Mon, 19 Jul 1993 08:59:19 -0500 Date: Mon, 19 Jul 93 09:08:06 CDT Message-Id: <9307191408.AA29071@trc.amoco.com> From: Jerrold L. Wagener To: SC22WG5@dkuug.dk Subject: informal report on X3J3 meeting 126 X-Charset: ASCII X-Char-Esc: 29 JLW informal report on the 1993 July 12-16 X3J3 meeting (#126) in Brussels, Belgium The objectives of this meeting were to (1) continue processing requests for interpretations, (2) respond to the WG5 Berchtesgaden resolutions, and (3) begin planning for implementation of the 1995 requirements. About two-thirds of the subgroup time was devoted to interpretation processing. Two interpretation subgroups, PROC and nonPROC, divided the backlog of 28 items, including five new items in the premeeting distribution and four more submitted at the meeting. Of these, 12 were approved for inclusion in the letter ballot to be issued next month. That leaves a backlog of 16 requests (7,49,70,88,91,121,136/137,138,139,141,143,145,146,147,148, 149), plus whatever is returned from the letter ballot and any new requests; these are assigned to a single subgroup responsible for all maintenance activities in the near future. The remaining subgroup time was devoted to organization of the technical work related to the Fortran 95 requirements (WG5 Berchtesgaden resolution B9, WG5- N930). The main result of this planning is X3J3/93-204r4, entitled RB9 Implementation PlanS, which is a chart containing 18 line items, one each for B9 resolution items A1-A5, B1-B3, C1-C7 and three for item B4. Identified for each 204r4 line item are: the responsible X3J3 subgroup, the principal X3J3 member contact, specific external contacts (if any), an external "subcontractor" (if one), and specific deliverables for X3J3 meetings 127, 128, and 129. In a few cases the X3J3 member contact and appropriate external contacts have not yet been identified. Of the 18 line items, two were identified at this meeting for subcontracting - B4.2 (additional obsolescent features, subcontractor BSI) and C2 (derived-type parameters, subcontractor L. Schonfelder); in all likelihood, at the next meeting other items will be identified for subcontracting. In most cases the meeting 127 deliverable is a tutorial on that topic, possibly accompanied by a preliminary proposal. X3J3 has so far recommended that one topic (C7, derived-type I/O) not be included in F95 - the rationale for this recommendation is contained in paper X3J3/93- 231, which will be communicated to WG5. Some attention was given to the editorial process for producing the 1995 revision. (Only six X3J3 meetings remain, meetings 127-132, before the draft revised standard is scheduled for delivery to WG5.) Documents X3J3/93-229, 230 summarize the currently envisioned editorial process, which involves two "specification" standing documents maintained by the editorial committee. One of these, the 008, is for editorial specifications; the other, a new standing document (009), will be used for specifications pertaining to the B9 resolution items and any other primarily technical items. The formats of the 008 and 009 are expected to evolve (as did that of the 006) as experience indicates the most useful forms. Preliminary suggestions for 009 fields include "status", "functional specifications", "implementation considerations", "example applications", "detailed edits", and "history"; the detailed edits field would be optional and only the functional specifications would be subject to X3J3 approval of a 009 item. Meeting 128 and 129 deliverables in the B9 Implementation Plan (93-204) are largely "009 specifications". A small drafting committee (membership as yet undetermined) would have the responsibility of turning the F90 standard + 008 specifications + 009 specifications into the 007 draft revision. X3J3, of course, would have to approve the 007 before submittal to WG5 as the draft revised standard. Finally, some adjustments were made to the X3J3 requirements process, to bring the US process more in line with that used by other WG5 member bodies and WG5 resolution B7. In the light of the WG5 requirements action, a cursory pass through that part of the 004 not yet having received formal X3J3 action identified one new item (0020, user-defined elemental functions) with near- unanimous straw-vote support, and a couple of others with a majority in favor. Major objectives at the next X3J3 meeting are likely to be refining and finalizing the X3J3 requirements and editorial processes, as well as executing the B9 implementation plan and continuing to provide Fortran 90 maintenance. Jerry Wagener 1993 July 19