From rinehuls@access.digex.net  Mon Sep  9 17:44:25 1996
Received: from access5.digex.net (qlrhmEbBUV1EY@access5.digex.net [205.197.245.196]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id RAA19071 for <sc22docs@dkuug.dk>; Mon, 9 Sep 1996 17:44:23 +0200
Received: from localhost (rinehuls@localhost) by access5.digex.net (8.6.12/8.6.12) with SMTP id LAA08899 ; for <sc22docs@dkuug.dk>; Mon, 9 Sep 1996 11:44:19 -0400
Date: Mon, 9 Sep 1996 11:44:19 -0400 (EDT)
From: "william c. rinehuls" <rinehuls@access.digex.net>
X-Sender: rinehuls@access5.digex.net
To: sc22docs@dkuug.dk
Subject: Document SC22 N2267
Message-ID: <Pine.SUN.3.94.960909113749.8444B-100000@access5.digex.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

(Note:  US Contribution on SC22 Work Program)
________________________________________________________________________
ISO/IEC JTC 1/SC22
Programming languages, their environments and system software interfaces
Secretariat:  U.S.A.  (ANSI)



ISO/IEC JTC 1/SC22
N2267



September 1996



TITLE:                United States Contribution on SC22 Work Program
                      Management



SOURCE:               Secretariat, ISO/IEC JTC 1/SC22



WORK ITEM:            N/A



CROSS REFERENCE:      SC22 N2129, N2228



DOCUMENT TYPE:        United States Contribution



ACTION:               To SC22 Member Bodies for information.

                      THIS DOCUMENT WILL BE DISCUSSED UNDER AGENDA ITEM
                      11.2 AT THE SEPTEMBER 1996 JTC 1/SC22 PLENARY.



Address reply to:
ISO/IEC JTC 1/SC22 Secretariat
William C. Rinehuls
8457 Rushing Creek Court
Springfield, VA 22153  USA
Tel:  +1 (703) 912-9860
Fax:  +1 (703) 912-2973
email:  rinehuls@access.digex.net

__________________________________________________________________________

     US CONTRIBUTION ON SC WORK PROGRAM MANAGEMENT

In accordance with the Urgent Request contained in JTC 1 SC22 
N 2228, the US National Body committee responsible for SC22 
(SC22 TAG) recently reviewed the Program of Work of SC22.  In 
conducting this review, the SC22 TAG made the following assumptions:

For projects were there was no active development (or revision) at present,  
the US response is based on if the US would participate in a maintenance 
or revision activity.

For projects where the US is not presently participating in the development, 
the US determined its response based on commercial interest by a US 
based concern in the activity.  In other words, if there is a supplier or a 
consumer of the standard, or products based on the standard, the US 
indicated the project should be pursued.

The US NB is actively participating and providing resources to all of SC22's 
projects, except as noted in the following 2 lists:

The US believes the following projects should be pursued, but is not 
participating in the development:

22.09.01	APL	
22.09.02	Character repertoire of APL	
22.24.01	Extended APL	
22.24.02	Character repertoire of Extended APL	
22.14		Guidelines for Language Bindings	
22.16		Language Independent Procedure Calling Mechanism
22.13		Guidelines for the Preparation of Prog. Lang.
		Standards
22.14766	Guide for POSIX National Profiles 
22.30.01	Framework for internationalization	
22.30.02.01	Functionality for Internationalization of 
		Applications	
22.30.02.02	International String Ordering 
22.30.02.03	Specification of cultural conventions
22.15.01	Guidelines for Prep. of Conformity Clauses in 
		Prog. Lang. Standards	
22.15.02	Test Methods for Prog. Lang. Processors
	



The US has no interest in the following projects:

22.46		Guidelines for Prep. of Language Independent 
		Service Specs	
22.21.01.01	POSIX System Interface (LIS)
22.21.03.01	POSIX System Administration	
22.47.1		PCTE Abstract Specification	
22.47.1		PCTE C Language Binding	
22.47.1		PCTE Ada Language Binding	
22.47.2		PCTE Object Oriented Extensions (for all parts)	
22.47.3		PCTE Fine Grain Objects Extensions (for all 
		parts)	
22.47.4		PCTE Part 4: C++ Binding	
22.47.5		PCTE Part 5: IDL Binding
22.12		Industrial Realtime Fortran
22.27.01	Form Interface Management System (FIMS)	
22.27.02	FIMS COBOL Binding
22.14977	Method of Defining Syntactic Metalanguage

______________________end of document SC22 N2267 ______________________

