A proposal for a new work item shall be submitted to the secretariat of the ISO/IEC joint technical committee concerned with a copy to the ISO Central Secretariat.

Presentation of the proposal - to be completed by the proposer Guidelines for proposing and justifying a new work item are given in ISO Guide 26.
 

Title (subject to be covered and type of standard, e.g. terminology, method of test, performance requirements, etc.)  Technical Report of Type 2 on Enhanced Module Facilities in Fortran

Scope (and field of application)  This report will specify an extension of ISO/IEC 1539-1 (Fortran) with the intention that the semantics and syntax described shall be incorporated in the next revision of this Standard exactly as they are specified therein unless experience in the implementation and use of this feature has identified any errors which need to be corrected, or changes are required in order to achieve proper integration, in which case every reasonable effort will be made to minimise the impact of such integration changes on existing commercial implementations.

Purpose and justification - attach a separate page as annex, if necessary  In large programs, composed of many modules, a change in a low-level module can cause a "compilation cascade:" Everything that depends on the low-level module is re-compiled, even if there are no changes in its interface, and everything that depends on those modules is re-compiled, etc.  This report proposes to allow (but not require) that a module be specified by an interface part that is accessible by use association, and one or more implementation parts (submodules) that are not directly accessible by use association. It will also allow large modules to be broken into parts that can share private data. To add this feature within the revision of ISO/IEC 1539-1 that is currently in hand would risk delaying its whole timetable. A Technical Report can be considered by the Technical Committee during the months of formal voting on the revised Standard and therefore will not delay it. It is envisaged that the TR and the revised Standard may be finally published at about the same time.

Programme of work If the proposed new work item is approved , which of the following document(s) is (are) expected to be developed?  ____ a single International Standard more than one International Standard (expected number: ........ )  ____ a multi-part International Standard consisting of .......... parts  ____ an amendment or amendments to the following International Standard(s) ....................................  __xx__ a technical report , type 2

Relevant documents to be considered ISO/IEC 1539-1 (Fortran)

Cooperation and liaison None.

Preparatory work offered with target date(s) 2003-02 Committee draft TR submitted for approval.  2004-02 Draft TR submitted for approval.

Signature:

Will the service of a maintenance agency or registration authority be required? No  - If yes, have you identified a potential candidate? ................ - If yes, indicate name ............................................................. Are there any known requirements for coding? No  -If yes, please specify on a separate page Are there any known requirements for cultural and linguistic adaptability? No  - If yes, please specify on a separate page Does the proposed standard concern known patented items? No  - If yes, please provide full information in an annex

Comments and recommendations of the JTC 1 Secretariat - attach a separate page as an annex, if necessary
 

Comments with respect to the proposal in general, and recommendations thereon: It is proposed to assign this new item to JTC 1/SC 22 The proposed project editor is Dr Van Snyder ([email protected]) of the USA.

Voting on the proposal - Each P-member of the ISO/IEC joint technical committee has an obligation to vote within the time limits laid down (normally three months after the date of circulation).
 

Date of circulation:  2001-10-10

Closing date for voting:  2002-01-11

Signature of JTC 1/SC 22 Secretary: Matt Deane

Notes to Proforma

A. Business Relevance. That which identifies market place relevance in terms of what problem is being solved and or need being addressed.

A.1. Market Requirement. When submitting a NP, the proposer shall identify the nature of the Market Requirement, assessing the extent to which it is essential, desirable or merely supportive of some other project.

A.2 Technical Regulation. If a Regulatory requirement is deemed to exist - e.g. for an area of public concern e.g. Information Security, Data protection, potentially leading to regulatory/public interest action based on the use of this voluntary international standard - the proposer shall identify this here.

B. Related Work. Aspects of the relationship of this NP to other areas of standardization work shall be identified in this section.

B.1 Competition/Maintenance. If this NP is concerned with completing or maintaining existing standards, those concerned shall be identified here.

B.2 External Commitment. Groups, bodies, or fora external to JTC1 to which a commitment has been made by JTC for cooperation and or collaboration on this NP shall be identified here.

B.3 External Std/Specification. If other activities creating standards or specifications in this topic area are known to exist or be planned, and which might be available to JTC1 as PAS, they shall be identified here.

C. Technical Status. The proposer shall indicate here an assessment of the extent to which the proposed standard is supported by current technology.

C.1 Mature Technology. Indicate here the extent to which the technology is reasonably stable and ripe for standardization.

C.2 Prospective Technology. If the NP is anticipatory in nature based on expected or forecasted need, this shall be indicated here.

C.3 Models/Tools. If the NP relates to the creation of supportive reference models or tools, this shall be indicated here.

D. Any other aspects of background information justifying this NP shall be indicated here.

D. Conformity Assessment and Interoperability

D.1 Indicate here if Conformity Assessment is relevant to your project. If so, indicate how it is addressed in your project plan.

D.2 Indicate here if Interoperability is relevant to your project. If so, indicate how it is addressed in your project plan.