From jwagener@trc.amoco.com Thu Aug 13 16:44:39 1992
Received: from noc.msc.edu by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA17078; Thu, 13 Aug 92 16:44:39 +0200
Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324))
	id AA12876; Thu, 13 Aug 92 09:44:41 -0500
Received: from [129.230.11.2] by uc.msc.edu (5.65/MSC/v3.0z(901212))
	id AA14727; Thu, 13 Aug 92 09:44:40 -0500
Received: from trc.amoco.com (apctrc.trc.amoco.com) by netserv2 (4.1/SMI-4.0)
	id AA19883; Thu, 13 Aug 92 09:44:30 CDT
Received: from crmac1 (crmac1.trc.amoco.com) by trc.amoco.com (4.1/SMI-4.1)
	id AA16694; Thu, 13 Aug 92 09:44:28 CDT
Date: Thu, 13 Aug 92 09:44:27 CDT
Message-Id: <9208131444.AA16694@trc.amoco.com>
From: Jerrold L. Wagener <jwagener@trc.amoco.com>
To: SC22WG5@dkuug.dk
Subject: informal report on the Seattle X3J3 meeting
X-Charset: ASCII
X-Char-Esc: 29

informal JLW report of the August 1992 X3J3 meeting in Seattle
--------------------------------------------------------------

The principle objectives of this meeting were to (1) process the outstanding 
issues associated with Fortran 90 maintenance, (2) respond to the POSIX 
request regarding the proposed Fortran 90 binding, and (3) respond to the WG5 
resolutions of the previous week.  Objectives (2) and (3) were achieved and 
good progress was made on objective (1).  In addition, the committee welcomed 
Ken Kennedy for a timely tutorial and discussion on the work and status of 
the High Performance Fortran Forum (HPFF).

At the beginning of the meeting there were 121 "unresolved issues" associated 
with the processing of corrections, clarifications, and interpretations to 
Fortran 90.  The vast majority of these were informal email questions or 
comments and did not represent new requests; 71 of these issues were resolved 
at the meeting.  Because of the high volume of such email traffic, the 
sentiment seemed to favor putting increased emphasis on asking the email 
authors to more clearly identify what they expect X3J3 to consider and less 
emphasis on X3J3 automatically considering every item in that traffic.  To 
this end the procedures outlined in document X3J3/92-027a will be revised and 
reissued.  The results of issue resolution at this meeting will be reflected 
in the Fortran 90 maintenance document, X3J3/S20, the update of which will be 
issued shortly.

The response to the IEEE POSIX request (X3J3/92-128,141a) confirmed X3J3 
support of the proposed Fortran binding and requested coordination between 
X3J3 and POSIX 1003.9 equivalent to that of "coordinating liaison" (ANSI 
jargon).  This is consistent with the response to the X3H5 binding proposal 
(X3J3/92-030,110) and with the policy recently adopted by WG5 regarding 
auxiliary standards (WG5/SD-4, X3J3/92-135, section 3.5 of the strategic 
plan).  Accordingly the response in /92-141a requests that the IEEE establish 
X3J3 as an official "coordination point" (IEEE jargon) for the proposed 
binding project.

Responses to WG5 resolutions V5, V6, V7, V8, V9, V11, V12, V13, and V14 were 
developed as document X3J3/S14.122 and passed by unanimous consent.  (X3J3 
response to the other 10 Victoria resolutions are either not needed or not 
appropriate.)  There were no X3J3 resolutions (in the sense of the /92-135 
provisions for R&R documents) at this meeting.  Maureen Hoffert, X3J3 vice 
chair, was appointed the X3J3 (primary devolpment body) representative on the 
WG5 management committee (V8).

The most significant, to X3, of the WG5 resolutions are V6 (adoption of the 
"Strategic Plan for Fortran Standardization"), V9 (identification of the 
primary development body for Fortran), and V13 (procedures for processing 
maintenance material for the international Fortran standard).  X3J3 concurs 
with all three of these resolutions.  Regarding V6, the strategic plan 
specifies that WG5 serve as a requirements body for the next revision and 
development of the revision, based on these requirements, is delegated to a 
primary development body.  The procedures in V13 identify the X3J3/S20 
document as the source of corrigenda items, with X3J3 approval followed by 
WG5 approval before an item can be forwarded to SC22 as a draft corrigenda; 
such items will be forwarded about once a year, starting after the November 
1992 X3J3 meeting.

In some sense V9 is the most significant of the WG5 resolutions, as it 
documents WG5's decision to produce a near-term (1995-96) revision of Fortran 
90.  It specifies X3J3 as the primary development body, providing an X3 "I" 
project for this development can be approved by June 30, 1993.  In its 
response to this resolution X3J3 concurs with the revision plan and agrees to 
the "I" project terms.  X3J3 also unanimously passed a separate motion 
recording its recommendation that the next revision be done as an "I" project 
and directing its chair to secure the necessary authorization for such a 
project.

Jerry Wagener


