Revised 8 May 2001, Jim Moore, Convener
The announcement and preliminary agenda for this meeting were circulated as N386.
The 40th meeting of ISO/IEC JTC1/SC22/WG9 will be hosted by the Ada-Europe conference in cooperation with the National Body of Belgium. Our host plans to provide coffee, tea and refreshments. In addition, there will be a computer data projector for our use.
The meeting will begin at 8:45 am and is expected to adjourn at 1:00 pm. At this time, the meeting room has not been identified.
The meeting is scheduled to begin at 0845.
A secretary for the meeting will be appointed at the beginning of the meeting.
The minutes of Meeting #39 appear in document N385. The document includes several corrections provided subsequent to Meeting #39:
[Agenda]
National Body Representatives:
WG9 Officers:
The Ada-Germany conference took place March 27-28 in Munich, with lively participation.
[Agenda]
Clyde Roby continues his fine work in maintaining WG9's web page.
The plenary meeting of SC22 will occur 17-21 September 2001 in Kona, Hawaii. At appropriate points in today's agenda, we will consider material to be presented at the SC22 meeting.
Discussions continue within JTC1 regarding restructuring with the goal of achieving greater market relevance. There appear to be three related proposals on the table:
Discussions continue within JTC1 itself and within subgroups of JTC1. The likely outcome is not obvious.
The Technical Corrigendum to the Ada Reference Manual was approved by SC22 on 26 February 2001 and sent to ITTF for publication. The Chair congratulates the project editors, Randy Brukardt and Erhard Ploedereder and the members of the ARG for this important accomplishment.
The current chair of SC22 is John Hill from the United States. Bob Mathis, former convener of WG9, briefly served as the US Head of Delegation to SC22. That job has now been taken by Rex Jaeschke.
At the last meeting of WG9, the Convener was given the following action item:
Action Item 39-6 (Convener): Ask Central Secretariat if they routinely grant permission for TRs to be reprinted. Otherwise we will have to find some way to make the Ravenscar TR widely available in the Ada community.
I have corresponded via email with M. Jacques-Olivier Chabot of ISO Central Secretariat on this issue. As a result of this interchange, I have learned the following:
The convener of WG9 has been reappointed to another three-year term that will expire at the SC22 plenary meeting in September 2003.
[Agenda]
The schedule for meetings #41 and #42 is proposed as follows:
[Agenda]
This is the "To Do" list for WG9. Some are informal action items assigned to various participants. Some are formal resolutions, which are not yet implemented. Some are suspense items awaiting action by other groups.
(Convener): Send a letter to Ada-Sweden inviting a representative from Sweden's National Body.
Status: CLOSED. The convener corresponded with Örjan Leringe in Sweden and Shayne Flint in Australia. The likelihood of representation from either nation seems low.
(Convener): Contact Prof. Alfred Strohmeier to determine if Springer-Verlaag can publish the ARM.
Status: OPEN. Discussions with Springer-Verlag are underway.
(ARG Chair): Draft a New Work Item Proposal for an Amendment to the Ada standard with a planned completion date of 2005.
Status: CLOSED. The Project Editor has drafted an NP for consideration at the meeting Leuven meeting of WG9.
[See Report of ARG]
(Convener): Prepare a "standing rule" that RGs develop new language features and APIs but the ARG determines how to package them, i.e. as part of the core standard, secondary standards, amendments, annexes etc., and determines how to express the optionality desirable in the features. ARG would act as a gatekeeper for language proposals that are submitted. WG9 would create new RGs as appropriate and would work in coordination with technical groups or professional societies.
Status: CLOSED. Convener has drafted a revised Charter for the ARG implementing the requirements noted in the action item. The revised Charter will be submitted for approval at the Leuven meeting of WG9.
[See Report of ARG]
(HRG Chair): Draft a New Work Item Proposal for the Technical Report providing guidelines and rationale for the use of the Ravenscar profile.
Status: OPEN.
(Convener): Ask Central Secretariat if they routinely grant permission for TRs to be reprinted. Otherwise we will have to find some way to make the Ravenscar TR widely available in the Ada community.
Status: CLOSED. See Convener's Report for description of Convener's conclusions.
(Convener): Send the HRG Charter to the HRG Chair for consideration of extension of scope.
Status: CLOSED. Convener sent Charter to HRG Chair. In the convener's opinion, there is no need for extension of scope.
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following standard be withdrawn when it reaches the end of its five-year life. The standard is relevant to the 1987 version of the Ada language standard rather than the current version:
Status: OPEN. This resolution has been reported to SC22 and endorsed (Resolution 99-19) at their plenary meeting in September 1999. JTC1 voted in March 2001 to approve withdrawal. Routine processing by ITTF should result in withdrawing the standards before the end of 2001.
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Technical Report be withdrawn when it reaches the end of its five-year review period. The Technical Report is relevant to the 1987 version of the Ada language standard rather than the current version:
Status: OPEN. This resolution has been reported to SC22 and endorsed (Resolution 00-22) at their plenary meeting in September 2000. JTC1 will ballot the withdrawal in early 2002. Implementation of the resolution can be expected before the end of 2002.
[Agenda]
[Agenda]
From Convener's Report, 1 July 1998, N345:
Project 22.35 -- (Type 2) TR 11735:1996 EXTensions for real-time Ada, Nasser Kettani, Editor
The contents of 11735 are substantively subsumed by the 1995 revision of 8652. This Technical Report will be withdrawn when usage of the 1987 version of the Ada language has diminished.
From SC22 N3178, Resolutions Prepared at the Thirteenth Plenary Meeting of ISO/IEC JTC 1/SC22 Nara, Japan, 2000-09-12/15:
Resolution 00-22: Standards for Periodic Review
ISO/IEC JTC 1/SC22 recommends to ISO/IEC JTC 1 that ... the following technical report be withdrawn at the end of its 5 year review period: ... ISO/IEC TR 11735:1996 - Extensions for real-time Ada.
[Agenda]
Project 22.31 -- IS 12227:1995 SQL/Ada Module Description Language (SAMeDL), Andreas Koeller, editor.
Resolution 36-3, N363:
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following standard be withdrawn when it reaches the end of its five-year life. The standard is relevant to the 1987 version of the Ada language standard rather than the current version:
Resolution 99-19, SC22 N3013:
ISO/IEC JTC1/SC22 recommends that the following standard be withdrawn:
[Agenda]
Project 22.10.04 -- IS 13813:1998 Generic packages of real and complex type declarations and basic operations for Ada (including vector and mattrix types), Don Sando and Ken Dritz, editors
Project 22.10.05 -- IS 13814:1998 Generic package of complex elementary functions for Ada, Jon Squire and Ken Dritz, editors
From Convener, email, 15 March 2001
As you know, every standard is reviewed at five years of age to determine if it should be confirmed (kept as is), revised, or withdrawn. This year we begin the five-year of the following WG9 standards:
I suspect that your first response is that these are not five years old. You're right, but the process begins this year with the following timetable:
(At this point, it is worth noting that fortuitous scheduling of meetings results in an SC22 recommendation to JTC1 being available for JTC1's autumn 2001 meeting. This is not the case for most of the SC's. Hence, the following)
Therefore, it is clear that we must develop our recommendations for the future of these two standards at our forthcoming meeting. Please be prepared to offer a position on the future of these two standards.
From Ken Dritz, email, 18 April 2001
13813 and 13814 are, of course, for Ada 83. I dug drafts of them, eight years old, out of my files; I don't think I ever saw the finished standards. I shall presume that my drafts reflect what was in the final standards.
13813 defines a generic complex types package, an array exceptions package, a generic real arrays package, and a generic complex arrays package. Of these, only the first is contained in Ada 95. As I recall, the reason for that was that we didn't want to standardize array subprograms "prematurely"; we wanted to wait until such future time as syntax and semantics for generalized array "sections" (multidimensional slices) could be defined in the core language. The generic complex types package in Ada 95 is functionally comparable to the one in 13813, but not identical.
13814 defines a generic complex elementary functions package. The generic complex elementary functions package in Ada 95 is functionally comparable to the one in 13814, but not identical. The biggest difference is that the latter separately imports a long list of complex operations as generic formal subprograms with box defaults (normally expected to be defined by an instantiation of the generic complex types packages at the place where the generic complex elementary functions package is instantiated), whereas the former imports just an instantiation of the generic complex types package.
Given that 13813 provides considerably more functionality than does the only part of it that was incorporated into Ada 95, it might be reasonable to reaffirm that standard. However, I believe there is a technical problem in doing so. The generic complex types package defined in 13813 renames an exception defined by the generic elementary functions package in 11430, which has been withdrawn. The generic complex elementary functions package also renames that exception.
I hope this proves to be useful. Say hello to all my old friends in WG9.
From WG9 N385, Minutes of November 2000 Meeting
The ARG is planning to begin discussions about future modifications of the Ada standard as either Technical Corrigenda, Amendments, or Revision. There was some discussion at this WG9 meeting about which method to use; the discussion centered around Amendments as the way to move forward. This will be the primary work of the ARG over the next few years.
WG9 must draft a New Work Item Proposal (NP) to go forward with an Amendment by 2005. ...
Action Item 39-3 (ARG Chair): Draft a New Work Item Proposal for an Amendment to the Ada standard with a planned completion date of 2005. [See Resolution 40-6.]
AIs will be written up similar to inputs to a Defect Report. A significant group of AIs could be grouped together to develop the appropriate document. Most compilers support or will support most of the changes suggested to the Ada language; thus, the ARG basically "approves" these changes. ...
There was discussion that Rapporteur Groups can develop new language features which are then input to the ARG (as gatekeeper of language proposals and new proposals of secondary standards) by technical groups or professional societies to determine how to package them (standard features, annexes, etc.) and how to express the optionality desired of these features. This will be a resolution at a future meeting.
Action Item 39-4 (Convener): Prepare a "standing rule" that RGs develop new language features and APIs but the ARG determines how to package them, i.e. as part of the core standard, secondary standards, amendments, annexes etc., and determines how to express the optionality desirable in the features. ARG would act as a gatekeeper for language proposals that are submitted. WG9 would create new RGs as appropriate and would work in coordination with technical groups or professional societies.
From Convener, email, 22 March 2001
After performing a bit of research, I have determined that a good way to capture this decision as a "standing rule" is to put it into the charter of the ARG. For the baseline charter, I used the statement of purpose that can be found in the current ARG Procedures. I then edited it to look a bit more like the other charters for WG9 Rapporteur Groups and to capture the ideas expressed in the Action Item.
I plan to offer this proposed Charter for approval at the Leuven meeting. [See Resolution 40-4.] As is usual, I hope to surface any issues prior to the meeting. Therefore, I request that you respond at the earliest possible opportunity if you wish to suggest changes.
From Convener, email, 12 April 2001
I have received no comments on the attached item. Therefore, I regard the issue as settled, aside from the formalities. The proposed charter for the ARG will be tabled at the Leuven meeting for approval by WG9. [See Resolution 40-4.]
The ARG met in Columbia, Maryland, USA, 17-19 November 2000, immediately following the WG9 meeting, for its usual three-day meeting. A number of amendment proposals were examined, some of which are getting close to general agreement. Notably, one of the amendments is the inclusion of the Ravenscar profile.
As a general guideline for amendments, the ARG agreed on the following points of emphasis:
The next meeting follows the WG9 meeting in Leuven.
Revised Charter of Ada Rapporteur Group [Resolution 40-4]
New Work Item Proposal for Amendment to Ada Language [Resolution 40-6]
[Agenda]
ISO/IEC 8652:1995 Information Technology--Programming Languages--Ada
Project 22.10.01, Randy Brukardt and Erhard Ploedereder, Project Editors
[Agenda]
Resolution 38-5, N372:
Having examined the draft of the planned United States National Body (USNB) contribution for 8652:1995/CORR, WG9 determines that the substantive content of the draft is a satisfactory basis for the text of the CORR. WG9 requests that the USNB resolve remaining editorial issues and effect contribution of the draft Corrigendum and supporting documents by 1 August 2000. The Convener is directed to commence a 30-day email ballot for approval of the CORR immediately upon receipt of the contribution from the USNB. Upon approval by WG9, the convener is directed to submit the CORR for approval by ISO/IEC JTC1/SC22.
Resolution 38-6, N372:
WG9 requests that the USNB contribute the text of 8652:1995/CORR (both the Corrigendum itself and the modified standard) in the form, at least, of HTML, PDF, and RTF files. Noting that the so-called "AARM" is not a formal standard, WG9 nevertheless requests that a new AARM be contributed in the same formats, accompanied by an appropriate disclaimer regarding its status.
From Convener:
WG9 approved the Technical Corrigendum and its supporting documents (N374, N375, N376, N377) by an email ballot that concluded September 2. There were no Negative votes and no comments. Following editorial preparation, the Technical Corrigendum and its supporting documents (N379, N380, N381, N382) have been submitted for approval by SC22. Approval is expected by the end of the year.
From SC22 Secretariat, SC 22 N 3185
Draft Technical Corrigendum Text and Letter Ballot for Draft Technical Corrigendum 1 for ISO/IEC 8652: 1995, Programming Language - Ada, 6 November 2000
From SC22 Secretariat, SC 22 N 3214
Summary of Voting on SC22 N 3185, DCOR 1 to ISO/IEC 8652:1995, Programming Languages - Ada
The following responses have been received on the subject of approval:
"P" Members supporting approval without comment 12 (Belgium, Canada, China, Denmark, Germany, Ireland, Japan, Netherlands, Norway, Russian Federation, UK, USA)
"P" Members supporting approval with comments 0
"P" Members not supporting approval 0
"P" Members abstaining 1 (France)
"P" Members not voting 8 (Austria, Brazil, Czech Republic, Egypt, Finland, Romania, Slovenia, Ukraine)
From SC22 Secretariat, Email to Keith Brannon (ITTF), 26 February 2001:
Please find attached the following document for publication:
SC 22 N 3185, DCOR 1 to ISO/IEC 8652:1995, Programming Languages - Ada
The summary of voting was circulated as SC 22 N 3214. I will forward to you the e-mail message that contains this document. There were no ballot comments on the DCOR text.
From WG9 N385, Minutes of November 2000 Meeting
Action Item 39-2 (Convener): Contact Prof. Alfred Strohmeier to determine if Springer-Verlaag can publish the ARM.
From Convener's Email of 27 March 2001
The current idea is that the document should have the title:
Consolidated Ada Reference Manual
Language and Standard Libraries
ISO/IEC 8652:1995(E) with Technical Corrigendum 1
and that the editors should be listed as:
S. Tucker Taft
Robert A. Duff
Randall L. Brukardt
Erhard Ploedereder
(The logic of the order of names is that the new edition would collate near the old edition in bibliographic databases.)
The document would NOT have change bars. As Alfred wrote, "After a year or so, nobody will be any longer interested in "changes", but the book will be still around, and the feeling will remain that there were RECENT changes in the language."
The size of the pages remains undecided. Randy and I prefer retaining the size of the currently available draft. Changing it would require reproofing all of the examples to ensure that lines have not wrapped inappropriately. We don't yet know if Springer-Verlag will agree.
ISO/IEC 18009:1999, Information Technology -- Programming Languages -- Ada: Conformity Assessment of a Language Processor
Project 22.18009, Erhard Ploedereder, Project Editor
[Agenda]
ISO/IEC 15291:1999, Information Technology--Programming Languages--Ada Semantic Interface Specification (ASIS)
Project 22.15291, Clyde Roby and Steve Blake, editors
From WG9 N385, Minutes of November 2000 Meeting
A few more implementations of ASIS are now available. It was recommended that a list of all test suites for ASIS be provided, perhaps available on the ASISWG website. ...
A few "bugs" have been uncovered, notably in one of the packages that had not been implemented when ASIS was standardized. This means that there probably will be a Corrigendum produced sometime in the future.
[Agenda]
ISO/IEC TR 15942:2000, Guidance for the use of the Ada Programming Language in High Integrity Systems
Project 22.15942 Brian Wichmann, Editor
From WG9 N385, Minutes of November 2000 Meeting
An AI describing Ravenscar will be sent to the ARG. HRG will produce guidelines and rationale on the use of Ravenscar in the form of a Technical Report.
Action Item 39-5 (HRG Chair): Draft a New Work Item Proposal for the Technical Report providing guidelines and rationale for the use of the Ravenscar profile.
Action Item 39-6 (Convener): Ask Central Secretariat if they routinely grant permission for TRs to be reprinted. Otherwise we will have to find some way to make the Ravenscar TR widely available in the Ada community.
Action Item 39-7 (Convener): Send the HRG Charter to the HRG Chair for consideration of extension of scope.
For convenience, the current Charter of the HRG appears in the Appendix to this document.
[Agenda]
None are anticipated.
[Agenda]
No unfinished business is anticipated.
[Agenda]
No new business is anticipated.
[Agenda]
We appreciate the comfortable accommodations provided by Ada-Europe and the National Body of Belgium. The following resolution expresses WG9's gratitude.
According to the JTC1 Directives, Rapporteur Groups serve from meeting to meeting of the parent body. The following resolution continues the existing RGs and appoints their Chairs until the next meeting of WG9.
[Agenda]
All resolutions are numbered provisionally and will be renumbered when the minutes are published.
The minutes of Meeting #39 as contained in document N385 are approved.
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 continues the following Rapporteur Groups until the next plenary meeting and expresses its grateful appreciation to their chairs for their service:
[Discussion] [Agenda]
WG9 schedules its next meeting as follows:
[Discussion] [Agenda]
WG9 adopts the following revision to the charter of its Ada Rapporteur Group:
Charter of the Ada Rapporteur Group
The Ada Rapporteur Group (ARG) is a subgroup of ISO/IEC JTC1/SC22/WG9, the JTC1 Working Group for Ada. The ARG has the following duties:
Language proposals originating in other Rapporteur Groups of WG9 will be referred to the ARG for disposition in the same manner as suggestions originating outside of WG9.
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standards be confirmed when they reach the end of their five-year review period:
[Discussion] [Agenda]
WG9 endorses the following New Work Item Proposal for an amendment to the Ada Language Standard and forwards it to SC22 for approval:
PROPOSAL FOR A NEW WORK ITEM
|
Date of presentation of proposal: |
Proposer: JTC1/SC22 |
|
Secretariat: ANSI |
ISO/IEC JTC 1 N XXXX |
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: |
|
Scope :This Amendment or amendments would modify or add capabilities to the language specifications of ISO/IEC 8652, the international standard for the programming language Ada. The target audience would be all users of Ada and all vendors of Ada language processors. Note: If appropriate, additional capabilities may be developed in the form of secondary standards rather than amendments. |
|
Purpose and justification: The international standard for Ada, ISO/IEC 8652, was published in 1995. A Technical Corrigendum, ISO/IEC 8652.Corr 1, corrected minor errors in the standard and was published in 2001. With 6 years' experience with the standard, and 10 years by the envisaged publication date of the Amendment, a number of shortcomings have been identified. The Amendment or amendments is intended to improve the standard in selected areas and integrate the progress of 10 more years of research and practice in programming languages into the Ada language standard. Note: Some of the amendments may also take the form of Secondary Standards; the proper mechanism will be chosen when the capability to be added has been specified in sufficient detail to allow an informed decision. |
|
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 _X__ an amendment or amendments to the following International Standard(s): ISO/IEC 8652 .................................... ____ a technical report , type ........... |
|
Relevant documents to be considered: The current international standard for Ada, ISO/IEC 8652. |
|
Cooperation and liaison: No formal liaison is anticipated. Informal liaison will be maintained with the various working groups that share an interest in Ada. |
|
Preparatory work offered with target date(s): Initial working drafts will be made available at plenary meetings of ISO/IEC JTC1/SC22 in the 2004-2007 time frame. |
|
Signature: James W. Moore, Convener, ISO/IEC JTC1/SC22/WG9 |
|
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 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: |
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: |
Closing date for voting: YYY-MM-DD |
Signature of JTC 1 Secretary: Lisa A. Rajchel |
|
NEW WORK ITEM PROPOSAL - PROJECT ACCEPTANCE CRITERIA |
|
|
|
Criterion |
Validity: |
Explanation: |
|
A Business Requirement |
|
|
|
A.1 Market Requirement |
Essential: X Desirable: Supportive: |
See above justification |
|
A.2 Regulatory Context |
Essential: Desirable: Supportive: X Not Relevant: |
The use of a standardized language is often a condition of a government acquisition, including acquisitions performed in a regulatory context. |
|
B. Related Work |
|
|
|
B.1 Completion/Maintenance of current standards |
Yes: X No: |
The work is related to the continued maintenance of the language specification, ISO/IEC 8652. |
|
B.2 Commitment to other organization |
Yes: No: X |
|
|
B.3 Other Source of standards |
Yes: No: X |
|
|
C. Technical Status |
|
|
|
C.1 Mature Technology |
Yes: X No |
The amendments or secondary standards will reflect existing technology and practice. In general, they will already be implemented in some, if not all, language processors prior to standardization. |
|
C.2 Prospective Technology |
Yes: N/A No: |
|
|
C.3 Models/Tools |
Yes: N/A No: |
|
|
D. Conformity Assessment and Interoperability |
|
|
|
D.1 Conformity Assessment |
Yes: No: X |
Conformity assessment for Ada language processors to ISO/IEC 8652 is standardized by ISO/IEC 18009. |
|
D.2 Interoperability |
Yes: No: X |
The work supports "portability" of source programs among various platforms. Some contemplated amendments or secondary standards are specifically geared towards improved interchange with other programming languages. |
|
E. Other Justification |
|
|
It is expected that, at least, the following national bodies will actively support this effort: Canada, Germany, Japan, United Kingdom, United States.
[Discussion] [Agenda]
WG9 expresses its gratitude to Ada-Europe and the National Body of Belgium for their gracious accommodations in hosting Meeting #40.
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to ??who?? for serving as secretary of Meeting #40.
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to Clyde Roby for maintaining the WG9 Web Page.
[Discussion] [Agenda]
Noting SC22's approval of the Technical Corrigendum and its subsequent submission to ITTF for publication, WG9 congratulates the Corrigendum editors, Randy Brukardt and Erhard Ploedereder.
[Discussion] [Agenda]
The meeting is anticipated to end by 1:00 pm.
[Agenda]
The HRG will synthesize the essential requirements of typical sector-specific standards for high integrity applications which have a bearing on Ada and its supporting tools. Guidance, including interpretation and amplification of Annex H will be developed for users, implementers, evaluators and certifiers. The guidance produced will be in a form suitable for reference in procurement.
Sector-specific standards to be considered are such as:
The HRG will undertake the following activities:
The HRG will produce and maintain an interpretations document.
The HRG will investigate pragma enhancement, such as additional parameters for restriction pragmas and additional pragmas.
The HRG will provide implementation advice, covering areas such as compilation and validation.
The HRG will produce a taxonomy of techniques for the construction and analysis of high integrity software, such as:
The HRG will investigate the interaction of language issues with high integrity requirements, such as:
The HRG will support the interoperation of high integrity software and tools with other systems, such as:
[Agenda]
N345 Convener's Report, 1 July 1998
N363 Minutes and Resolutions of Meeting #36
N367 Minutes and Resolutions for Meeting #37 of ISO/IEC JTC1/SC22/WG9, Friday, 22 October 1999, Redondo Beach, California, USA
N372 Draft Minutes and Resolutions for Meeting #38 of ISO/IEC JTC1/SC22/WG9, Friday, 30 June 2000, Potsdam, Germany
N373 SC22/WG9 Convener's Report, 11 July 2000
N374 DRAFT Submitted for WG9 Email Ballot, Programming Languages -- Ada, Defect Reports, Part 1, 2 August 2000
N375 DRAFT Submitted for WG9 Email Ballot, Programming Languages -- Ada, Defect Reports, Part 2, 2 August 2000
N376 DRAFT Submitted for WG9 Email Ballot, Programming Languages -- Ada, Records of Response 1, 2 August 2000
N377 DRAFT Submitted for WG9 Email Ballot, Programming Languages -- Ada, Technical Corrigendum 1, 2 August 2000
N378 Plenary Meeting Report of ISO/IEC JTC1/SC22, 11-15 September 2000, Nara, Japan
N379 DRAFT Submitted for SC22 Approval, Defect Reports Part 1, for ISO/IEC 8652:1995, Programming Languages -- Ada, 1 October 2000
N380 DRAFT Submitted for SC22 Approval, Defect Reports Part2, for ISO/IEC 8652:1996, Programming Languages -- Ada, 1 October 2000
N381 DRAFT Submitted for SC22 Approval, Records of Response, for ISO/IEC 8652:1995, Programming Languages -- Ada, 1 October 2000
N382 DRAFT Submitted for SC22 Approval, Technical Corrigendum 1, for ISO/IEC 8652:1995, Programming Languages -- Ada, 1 October 2000
N383 Announcement and Draft Agenda, Meeting #39 of ISO/IEC JTC1/SC22/WG9, Friday, 17 November 2000, Laurel, Maryland, USA
N385 Draft Minutes and Resolutions for Meeting #39 of ISO/IEC JTC1/SC22/WG9, Friday, 17 November 2000, Laurel, Maryland, USA.
N386 Announcement and Draft Agenda, Meeting #40 of ISO/IEC JTC1/SC22/WG9, Friday, 18 May 2001, Leuven, Belgium
Table of ISO Price Codes: http://www.iso.ch/infoe/order.html#PriceIntro
ITTF Web Site: http://www.iso.ch/ittf/
WG9 Web Site: http://www.open-std.org/jtc1/sc22/wg9/
ACAA Web Site: http://www.ada-auth.org/~acats/grab-bag.html
Ada Europe 2001 Conference Web Site: http://www.ada-europe.org/conference2001.html
[Agenda]
End of Document