From owner-sc22wg5@dkuug.dk  Tue Jun 22 17:31:17 2004
Received: (from majordom@localhost)
	by dkuug.dk (8.12.10/8.9.2) id i5MFVHh9047277
	for sc22wg5-domo; Tue, 22 Jun 2004 17:31:17 +0200 (CEST)
	(envelope-from owner-sc22wg5@dkuug.dk)
X-Authentication-Warning: ptah.dkuug.dk: majordom set sender to owner-sc22wg5@dkuug.dk using -f
Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.60])
	by dkuug.dk (8.12.10/8.9.2) with ESMTP id i5MFV9E7047272
	for <sc22wg5@dkuug.dk>; Tue, 22 Jun 2004 17:31:12 +0200 (CEST)
	(envelope-from dnagle@erols.com)
Received: from 66-44-57-74.s328.tnt2.lnhva.md.dialup.rcn.com ([66.44.57.74])
	by smtp01.mrf.mail.rcn.net with smtp (Exim 3.35 #7)
	id 1BclsU-0004sG-00; Tue, 22 Jun 2004 10:03:58 -0400
From: Dan Nagle <dnagle@erols.com>
To: j3@j3-fortran.org, sc22wg5@dkuug.dk
Subject: Re: (j3.2004) New terminology when Modules TR 19767 is integrated
Date: Tue, 22 Jun 2004 10:05:27 -0400
Organization: Purple Sage Computing Solutions, Inc.
Message-ID: <f1fgd051u0uhl49h3blf6fv1rbvhbspgv6@4ax.com>
References: <200406212031.i5LKV6He025654@math.jpl.nasa.gov>
In-Reply-To: <200406212031.i5LKV6He025654@math.jpl.nasa.gov>
X-Mailer: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0 () 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dkuug.dk id i5MFVFE7047273
Sender: owner-sc22wg5@dkuug.dk
Precedence: bulk

Hello,

I prefer the "Pasadena Two-Step" approach.

First, the TR is incorporated as-is into the IS.
Then, a separate paper makes any CCR improvements
which may seem desirable.

FWIW

-- 
Cheers!

Dan Nagle
Purple Sage Computing Solutions, Inc.

On Mon, 21 Jun 2004 13:31:06 -0700, Van.Snyder@jpl.nasa.gov wrote:

>
>When the Modules Technical Report 19767 is integrated into the standard,
>new terminology would simplify wording in several places without changing
>the substance of the TR.
>
>The term I propose to introduce is "package," meaning "a module and all
>of its submodules."
>
>Something like
>
>[13:12+]
>
><<2.2.4 Package>>
>
>A <<package>> consists of a module and all of its descendant submodules.
>A package is not a program unit or a scoping unit.  A <<package component>>
>is a module or a submodule.
>
>Then change <<2.2.4 Module>> to <<2.2.4.1 Module>> and <<2.2.5 Submodule>>
>to <<2.2.4.2>> Submodule.
>
>Most of the edits for pages 14 (heading for Table 2.2), 46, 55, 56, 59,
>60, 84, 113, 115, 251, 259 (C1211a), 280, 283, 415, 422 and 435 could be
>simplified, either by replacing "module or submodule" by "package" or
>"package component" or by replacing "module" by "package component"
>instead of introducing a parallel sentence or list item (e.g. 422:14-17).
>
>I do not propose that the TR be amended, only that the new terminology
>be introduced when the TR is integrated into the next revision of the
>standard.  The promise regarding TR's is "integrated without change,"
>not "integrated word-for-word."  I believe "integrated without change"
>means "integrated without change to its substance."