Revised 6 June 2002 by Jim Moore, Convener
The next meeting of ISO/IEC JTC1/SC22/WG9 will be collocated with the Ada-Europe conference. It is scheduled to begin at 9:00 am on Friday, 21 June. The local organizer advises me that a coffee break will be provided. We anticipate that a computer data projector will be available as well as an overhead projector for transparencies.
Conference and venue information can be obtained at the conference web site.
The announcement and preliminary agenda for this meeting were circulated as N401.
|
The meeting is scheduled to begin at 9:00 am. |
|
We anticipate that Erhard Ploedereder, the President of Ada-Europe, will provide some welcoming remarks on behalf of Ada-Europe and the conference. |
|
A volunteer is requested to serve as meeting secretary. |
|
This agenda will be considered, amended if necessary, and approved. |
|
Background |
The draft minutes of Meeting #41 are document N400. The minutes include corrections suggested by John Barnes, Randy Brukardt, Pascal Leroy, Jim Moore and Erhard Ploedereder. |
|
|
|
|
Resolution |
[Agenda]
|
Canada |
Stephen Michell (HOD) |
[Report] |
|
France |
Jean-Pierre Rosen (HOD) |
[Report] |
|
Germany |
Erhard Ploedereder (HOD) |
[Report] |
|
Italy |
Tullio Vardanega (HOD) |
[Report] |
|
Japan |
Kiyoshi Ishihata (HOD) |
[Report] |
|
Switzerland |
(Unable to attend) |
[Report] |
|
UK |
John Barnes (HOD), Alan Burns |
[Report] |
|
USA |
Randy Brukardt (Acting HOD), Currie Colket, Tucker Taft |
[Report] |
|
Convener |
Jim Moore |
|
Chair of ARG |
Pascal Leroy |
|
Chair of ASIS RG |
Currie Colket |
|
Chair of HRG |
Alan Burns |
|
Project Editors |
Randy Brukardt |
|
Those sending regrets include: |
Ted Baker, Ken Dritz, Clyde Roby, Alfred Strohmeier, Joyce Tokar |
|
|
|
|
|
|
|
|
|
|
Tullio Vardanega, email 31 May 2002: a) I am currently trying to reconstitute an interest group [in Italy] to follow up and interact with my participation in the WG9 activities. b) I have accepted Pascal Leroy's invitation at becoming an observer in the ARG and I will attend their meeting at Vienna |
|
|
Kiyoshi Ishihata, email 25 May 2002: JIS standard of Ada was (finally) published on February 20, 2002. We translated only Chapter 1 to Japanese. For all other parts of ARM, we refer to the English version. All parts of the original ARM text are included in the JIS standard. |
|
|
Alfred Strohmeier, email 24 May 2002: No report from Switzerland, for the simple reason that there was no activity related to the Ada standard. |
|
|
|
|
|
|
[Agenda]
I am very pleased to see that the Italian National Body has chosen to participate in WG9. I welcome Tullio Vardanega as their representative. Italy participates as a "P" (Participating) Member of WG9 despite the fact that Italy is only an "O" (Observing) Member of our parent body, SC22. You may recall that it was WG9 that requested the change in JTC1 procedures that permits this situation. I am pleased that our effort has produced concrete benefits for us.
I am also pleased with Springer-Verlag's publication of the Consolidated Reference Manual, which merges the text of the Technical Corrigendum with the 1995 standard. Our gratitude goes to Alfred Strohmeier for arranging the publication, to Randy Brukardt for preparing copy suitable for hardcopy publication, and to both of them for arranging the distribution of copies to those who played key roles in the development of the Corrigendum.
Both Ada-Europe and ACM SIGAda have submitted a request for Category C liaison with WG9. I hope that WG9 will "confirm" the requests at this meeting and send them on to SC22 for the sequence of approvals authorizing the liaison relationship. Liaison participation by these two organizations will permit WG9 to utilize the technical expertise of their respective memberships.
Although SC22's approval is only the first in the sequence needed to authorize the liaison relationship, I will choose to treat it as the substantive approval, regarding the actions by JTC1 and ITTF to be administrative in nature. Accordingly, I will implement the liaison relationship immediately upon approval by SC22. I expect this to occur at their plenary meeting in August.
It should be noted that SIGAda's parent organization, ACM, has not yet given their approval to the liaison request. Of course, no action to implement the liaison relationship will be taken until this approval is received.
I anticipate that the first benefit of the liaison relationship will be the ability to more effectively staff the membership of our Rapporteur Groups. For some time, the Chairs of our Rapporteur Groups have permitted informal participation by individuals who have not been formally authorized by their National Bodies -- a practice that goes beyond the procedures of JTC1. Following SC22 approval of the liaison, I plan to rationalize participation in Rapporteur Groups by identifying each participant as either a representative of their National Body or a representative of a liaison organization. This will restore our compliance with the procedures of JTC1 while retaining our ability to draw upon a diverse base of technical talent.
Prior to the fall 2002 meeting of WG9, I plan to take the following administrative steps:
Until we can implement these steps, I ask that each Rapporteur Group chair continue their current informal practices for managing the membership of their RG. They have my full confidence and support in performing this.
As you know, one year ago, WG9 requested free availability of Technical Report 15942. This request has not yet been implemented because of an unfortunate sequence of events. If the matter had gone according to plan, the request would have been approved at the plenary meeting of SC22 in September, then approved at the plenary meeting of JTC1 in November. Because of the events of September 11, the SC22 plenary was poorly attended, falling short of a quorum. It was agreed that any contested issue would be subjected to confirmation by letter ballot. Free availability for the Technical Report brought objection from one National Body -- on the principle of free availability rather than anything specific to the request. The request was approved by a subsequent letter ballot, but missed the JTC1 meeting. Recently, it was approved by letter ballot of JTC1 and submitted to ITTF for implementation. I continue to track the issue.
Many of you are aware that the US Army, via its contract with The MITRE Corporation, had been funding the editor of the Amendment project, as well as the participation of the Convener in WG9. The Army elected to reduce that funding level in February, due in part to the financial demands of the current war. Regrettably, we lost the ability to fund the editor's work in this manner. I believe that this event must force us to reconsider the scope of the amendment project. Later in the meeting, I have scheduled an agenda item for that purpose.
Although funding for the WG9 Convener continues through September 2002, funding beyond that point is not assured. I offer my personal assurance that I will continue to execute the responsibilities of the Convener until my term ends in September 2003.
[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.
|
Resolution 38-4 |
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:
For status, see [Project Editor Maintenance Report, 11735] |
|
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. For status, see [Report of the Annex H Rapporteur Group] |
|
Action Item 40-2 |
(UK): Make a recommendation regarding the changes necessary for 13813. For status, see: [Project Editor Maintenance Report, 13813] |
|
Action Item 40-3 |
(ARG Chair): Upon receipt of the UK recommendation, consider the packaging appropriate for the functionality of the current 13813. For status, see: [Project Editor Maintenance Report, 13813] |
|
Resolution 40-6 |
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be confirmed when it reaches the end of its five-year review period:
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be withdrawn when it reaches the end of its five-year review period:
For status, see: [Project Editor Maintenance Report, 13813] |
|
Resolution 40-7 |
WG9 endorses the following New Work Item Proposal [see N388] for amendments to the Ada Language Standard and forwards it to SC22 for approval. For status, see: [Project Editor Maintenance Report, 8652] |
|
Resolution 40-8 |
ISO/IEC JTC1/SC22/WG9 requests that SC22 request JTC1 and any other appropriate bodies to take action to ensure that ISO/IEC TR 15942 be made freely available on a web site. For status, see [Project Editor Maintenance Report, 15942] |
[Agenda]
|
Background |
Meeting #43 was scheduled by email ballot [N403] for December 13, 2002 in Houston, TX in conjunction with the SIGAda conference. |
|
|
|
|
Resolution |
[Agenda]
|
Background |
|
|
Open Items |
|
|
Prior Discussion |
From the Minutes of Meeting #41 [N400]: Report of ARG Chair:... It becomes evident that at this stage integrating new features in the language in a way that is both compatible with existing code, and not too disruptive to implementations, is extremely challenging. Other than for the Editor of the project, there is no funding for this language design effort. This means that the work that is needed for the amendment is done on a voluntary basis, and in practice that relatively little progress takes place between meetings. The Rapporteur feels that relatively few amendment AIs will be mature enough in 2005 for inclusion in the official Amendment document. Note that the situation is different for AIs that have to do with normal maintenance of the language, because in these cases it is much easier to understand the problem at hand and the impact of proposed solutions. The procedures of the ARG are being revised to (1) deal with the fact that we are now going to work on extensions to the language, (2) put them in accordance with the rule of the parent bodies and (3) reflect existing practice. The revised procedures have been drafted by the Editor and Rapporteur of the ARG, and submitted to the convener of WG 9 for review. They are expected to be approved by the ARG at its next meeting, and will be presented at the next meeting of WG 9. One of the significant changes of the new procedures has to do with the disposition of comments submitted to the ada-comment mailing list. Because the ARG is soliciting input from the Ada community regarding possible amendments to the language, a sizeable number of suggestions have been received by email. Previously, each email received on ada-comment would result in an AI. But the ARG felt that if the same rule were applied to suggestions for amendments, there would be a danger of spending precious ARG time on proposals that are not well thought-out or would have an unacceptable impact on the Ada community. Therefore, the Editor and the Rapporteur are in charge of doing an initial triage of the comments, only creating AIs for those that seem to deserve detailed consideration by the ARG. A new category of document, ACs (for Ada Commentaries) is created to record the suggestions and any discussion pertaining to them. ARG members may request that ACs be turned into AIs if they think a suggestion has some value. These new procedures will be presented officially to WG9 at the next meeting. France suggested that those who submit suggestions for Ada 2005 should first send them to their own national body before sending the suggestion to the ARG. The purpose would be to determine that their is some support for the proposal before burdening the ARG. Pascal will take this suggestion to the ARG meeting for further consideration. |
|
Report |
The ARG met in Bloomington, MN, in October and in Cupertino, CA, in February. As is now customary, about 1/3rd of each meeting was spent on "normal" AIs, i.e. corrections to problems in the existing RM, and 2/3rds of each meeting was spent on amendment AIs. Good progress was made on amendments AIs. A few (relatively simple) amendment AIs are ready for approval at this meeting (see list below). But more importantly a number of major amendments have reached a point where they are stable enough that there is a consensus among the ARG that the technical solution is sound. The next step is to write the RM wording for these amendments, which is not a small feat given that they may have a sizeable impact on the language. Amendments that have reached this point include unchecked unions, handling of mutually dependent types, multiple inheritance through the use of interfaces, package Directory_Operations, and private with clauses, among others. These are all important improvements to the language, and barring unexpected technical difficulties, chances are that they will make it into the final amendment document. The ARG has also started exploring more controversial or speculative amendments, like downward closures or assertions, but these topics still need a lot of brainstorming before it can be decided whether they are worth pursuing or not. Some vendors have voiced concerns over the usefulness of some of the extensions being considered by the ARG, on the basis that it is unclear if the implementation effort can be justified. This is a legitimate concern, although it is nearly impossible to get any hard data regarding (1) the implementation cost and (2) the benefits to the Ada community of each amendment. It would be good if the ARG could get some guidance on the scope of the revision (especially considering funding difficulties) although it is unclear how this should be achieved. The ARG has a number of proposals for extensions from the Ada community, but this input has been in general quite disappointing, either because equivalent capabilities already exist, or because the proposed extensions would be too complex or too expensive to integrate in the language. However, very useful input was recently received from the IRTAW regarding possible real-time extensions. A "call for APIs" was circulated in the Ada community explaining that independent groups could undertake standardization work on APIs or reusable libraries, with some guidance from the ARG. The ARG has its "usual" motion for the June meeting for approval of a series of AIs. The cited AIs can be retrieved from the ACAA web site for AIs. Amendment AIs: AI95-00257-01/04 2002-05-10 -- Restrictions for implementation-defined entities AI95-00260-01/04 2002-05-10 -- How to control the tag representation in a stream AI95-00267-01/04 2002-05-10 -- Fast float to integer conversions AI95-00273-01/02 2002-05-09 -- Use of PCS should not be normative Normal AIs: AI95-00085-01/08 2002-05-09 -- Append_File, Reset and positioning for Stream_IO AI95-00161-01/07 2002-05-14 -- Default-initialized objects AI95-00225-01/03 2002-05-14 -- Aliased current instance for limited types AI95-00229-01/05 2002-05-14 -- Accessibility rules and generics AI95-00233-01/03 2002-05-09 -- Inheritance of components of generic formal derived types AI95-00238-01/03 2002-05-09 -- What is the lower bound of Ada.Strings.Bounded.Slice? AI95-00240-01/04 2002-05-09 -- Stream attributes for limited types in Annex E AI95-00242-01/02 2001-10-18 -- Surprise behavior of Update AI95-00246-01/05 2002-05-14 -- View conversions between arrays of a by-reference type AI95-00247-01/02 2002-05-14 -- Alignment of composite types AI95-00272-01/02 2002-05-10 -- Pragma Atomic and slices The procedures of the ARG have been revised by the Editor and the Rapporteur based on the input of the convener of WG9 (see document N400 for the justifications of this revision). They were reviewed by the ARG at the Bloomington meeting, and have been approved without substantial changes. They are now formally submitted to WG9 for approval. The revised procedures are contained in N406. They are also available at the ARG web site. |
|
|
|
|
Resolutions |
[Agenda]
|
Background |
|
|
Open Items |
|
|
Prior Discussion |
From Minutes of Meeting #41 [N400]: Currie Colket mentioned that the ASIS RG is revising its charter. The convener noted that charter revisions must be approved by WG9. ASIS RG is considering the preparation of a New Work Item Proposal to revise and extend ASIS to keep pace with Ada 2005. The ASIS RG may reconsider some of the design goals for the specification. |
|
Report |
|
|
|
|
|
Resolutions |
|
[Agenda]
|
Background |
|
|
Open Items |
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. Status: OPEN. The spring 2001 meeting of the HRG confirmed that they wish to move ahead on drafting a Technical Report providing advice on the usage of the Ravenscar profile. They developed a list of contents and assigned an author to each section. They plan to develop a first draft within six months. They plan to bring an NP to the WG9 meeting following completion of the initial draft. |
|
Prior Discussion |
From Minutes of Meeting #40, [N389]: The recent meeting of the HRG confirmed that they wish to move ahead on drafting a Technical Report providing advice on the usage of the Ravenscar profile. They developed a list of contents and assigned an author to each section. They plan to develop a first draft within six months. They plan to bring an NP to the WG9 meeting following completion of the initial draft. The HRG also discussed the continuing role of Annex H of ISO/IEC 8652. They discussed the desirability of changing its title to High-Integrity rather than Safety and Security. The HRG might recommend that the fourth section of Annex H should be reworked to better fit with the recently completed TR 15942. They also considered tracking the usage of relevant pragmas implemented by various vendors. It is understood that the HRG may work with the University of York or other institutions in obtaining material that might be incorporated into a Technical Report. From Minutes of Meeting #41 [N400]: The HRG has produced an initial 35-page draft of a TR providing guidance on usage of the Ravenscar profile. At yesterday's meeting, they confirmed the structure and the style of the guide. By the next meeting of WG9, they will produce a substantially completed draft. They meeting also reviewed the contents of Annex H of ISO/IEC 8652:1995. The International Real-time Ada Workshop (IRTAW) will look at real-time issues during its meeting in April 2002. The HRG could draft a New Work Item Proposal and send it and the existing draft forward to SC22 so the SC22 could begin the approval of a New Work Item. Alan said that the NP had not yet been drafted for two reasons: (1) there was not a good estimate of the resources available; and (2) they desired a method to be sure that the report could be made freely available. The Convener described the procedures for making materials publicly available. After the options were described, Alan suggested that the University of York (UK) could publish a draft and then contribute it to ISO for further processing. Alan mentioned that there were no plans to revise TR 15942. |
|
Report |
|
|
|
|
|
Resolutions |
|
[Agenda]
[Agenda]
|
Document Status |
ISO/IEC 8652:1995 Information Technology--Programming Languages--Ada, 22.10.01, Randy Brukardt and Erhard Ploedereder, Project Editors, supported by the Ada Rapporteur Group. ISO/IEC 8652:1995/COR.1:2001, Technical Corrigendum to Information Technology--Programming Languages--Ada, 22.10.01, Randy Brukardt and Erhard Ploedereder, Project Editors, supported by the Ada Rapporteur Group. |
|
Project Status |
Working Draft, 8652:1995/AMD.1, Randy Brukardt and Pascal Leroy, Project Editors, supported by the Ada Rapporteur Group The request for subdivision [N388] of Project 22.10.01 was endorsed by WG9 Resolution 40-7 [N389], approved by SC22 N3310 on 2001-09-12, and forwarded to JTC1. |
|
Open Items |
Resolution 40-7WG9 endorses the following New Work Item Proposal [see N388] for amendments to the Ada Language Standard and forwards it to SC22 for approval. Status: CLOSED. The request was forwarded to SC22 as a request for subdivision of the existing project for ISO/IEC 8652. The subdivision was reported approved by SC22 in their document N3310 and forwarded to JTC1. JTC1 has not objected. |
|
Report |
|
|
|
|
[Agenda]
|
Document Status |
ISO/IEC TR 11735:1996, Information Technology--EXTensions for Real-Time Ada, 22.35, Nasser Kettani, Project Editor JTC1 has voted to withdraw this standard, an action that will be implemented by year-end 2002. The Technical Report addressed the Ada 87 language and is effectively replaced by the 1995 language standard. |
|
Open Items |
Resolution 38-4: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. |
|
Report |
None |
|
|
|
[Agenda]
|
Document Status |
ISO/IEC 13813:1998, Information Technology--Programming Languages--Generic Packages of Real and Complex Type Declarations and Basic Operations for Ada (including Vector and Matrix Types), 22.10.04, Don Sando and Ken Dritz, Project Editors WG9 is considering the question of maintenance to this standard. The standard addresses the Ada 87 language. Portions were effectively included in the 1995 language standard. ISO/IEC 13814:1998, Information Technology--Programming Languages--Generic Package of Complex Elementary Functions for Ada, 22.10.05, Jon Squire and Ken Dritz, Project Editors WG9 has voted to withdraw this standard by year-end 2004. (The action awaits approval by JTC1.) The standard addressed the Ada 87 language and is effectively replaced by the 1995 language standard. |
|
Open Items |
Resolution 40-6:ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be confirmed when it reaches the end of its five-year review period:
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be withdrawn when it reaches the end of its five-year review period:
Status: OPEN. The recommendations above were endorsed by SC22 Resolution 01-07 at their September 2001 plenary meeting. They have been forwarded to JTC1 for approval (during 2003) and implementation by ITTF (during 2004). Action Item 40-2(UK): Make a recommendation regarding the changes necessary for 13813. Status: CLOSED. Initial report was included in N393. Initial draft revision submitted by the editor was N397. Reflecting additional consideration, a further draft and a final report from the UK were circulated as N404 and N405, respectively. The material has been forwarded to the ARG for their consideration and recommendation. Action Item 40-3(ARG Chair): Upon receipt of the UK recommendation, consider the packaging appropriate for the functionality of the current 13813. Status: OPEN. The recommendation was forwarded 6 June 2002. |
|
Prior Discussion |
From Ken Dritz, email, 18 April 200113813 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. From Minutes of Leuven meeting, [N389]At the suggestion of Barnes, we separate the discussion of the two standards. There is consensus that 13814 should be withdrawn. Discussion continues on the future of 13813. Michell asks if WG9 currently has the expertise needed to revise 13813 because the needed changes might not be simple. Tokar suggests that we might leave the standard in place for now and ask the ARG to include the functionality in the planned amendment to 8652. No one knows of any vendor implementations of the standard but Barnes says that implementation by users is straightforward. We break for coffee. Following the break, the convener suggests the following plan:
There is general agreement with this approach. From Minutes of Bloomington meeting, [N400]The report of the UK was submitted prior to the meeting. [It is included in the minutes.] On the morning of the meeting, the editor of 13813, Don Sando, submitted an initial working draft [N397] to implement the recommendation of the UK. As the UK had not had an opportunity to study the draft, it was decided that the UK should determine that the draft is appropriate to the recommendation and then forward both the draft and the recommendation to the ARG. |
|
Report |
From Don Sando (Editor), email, 4 March 2002Many thanks for an excellent review; I am very pleased that you caught the one major problem prior to submission to WG9. I have attached my latest draft (in Word) ... [N404] From John Barnes, email 5 June 2002... I now attach the final report [N405] from the UK regarding 13813. |
|
Resolution |
[Agenda]
|
Document Status |
ISO/IEC 15291:1999, Information Technology--Programming Languages--Ada Semantic Interface Specification (ASIS), 22.15291, Steve Blake and Clyde Roby, Project Editors, supported by the ASIS Rapporteur Group. |
|
Open Items |
None |
|
Report |
Email, Clyde Roby, 26 May 2002: No update for the ASIS document at this time. |
|
|
|
[Agenda]
|
Document Status |
ISO/IEC TR 15942:2000, Guidance for the Use of Ada in High Integrity Systems, 22.15942, Brian Wichmann, Project Editor, supported by the Annex H Rapporteur Group. |
|
Open Items |
Resolution 40-8: ISO/IEC JTC1/SC22/WG9 requests that SC22 request JTC1 and any other appropriate bodies to take action to ensure that ISO/IEC TR 15942 be made freely available on a web site. Status: OPEN. The request [See N390] was forwarded to SC22 for endorsement. SC22 approved the request by letter ballot (see SC22 N3360, 2002-01-14). JTC1 has approved the request (see SC22 N3403). The document has been forwarded to ITTF for implementation of the request. |
|
Report |
None |
|
|
|
[Agenda]
|
Document Status |
ISO/IEC 18009:1999, Conformity Assessment of an Ada Language Processor, 22.18009, Erhard Ploedereder, Project Editors, supported by the Ada Rapporteur Group. |
|
Open Items |
None |
|
Report |
None |
|
|
|
[Agenda]
[Agenda]
|
Report |
Email from Ted Baker, 23 May 2002I have nothing much new to report as Liaison to WG15 and IEEE PASC. The only active project related to Ada is POSIX 1003.5g, and that is only marginally active. I sent out an e-mail on that back in April, requesting (again) volunteers to help with the project. There was one new response, from Alejandro Alonso, which I forwarded to Diane Schleicher. I have been following e-mail of the Austin Group, which has taken over the job of maintaining and updating the consolidated Unix-POSIX specifications. It seems this consolidation has increased the C-centricity of the project. One member of the group suggested, I think not entirely in jest, that the C language, C++ language, and POSIX C API standards be brought together under one group. The notion was that the C language can be considered "core" C++, and the POSIX API can be considered part of the standard libraries. I append my previous e-mail, for those who may have missed it: The POSIX 1003.5g project is intended to provide an update to the POSIX (IEEE STD 1003.5-1999, ISO/IEC 14519) to include additional real-time extensions needed by for avionics. In particular, it would provide Ada bindings for some of the real-time features added to the POSIX C standards more recently than the previous amendment to 1003.5 (which was the last *revision* of ISO/IEC 14519). The Project Authorization for 1003.5g is due to expire by the end of the current calendar year. Diane Schleicher (see e-mail address in the "cc" field above), who is heading up the editing of this project, is funded to work on it, but her working group is small and by comparison with the other 1003.5 projects she has not gotten much support from other working group members. She is considering asking for an extension to the authorization (PAR) from the IEEE, but I expect they will be skeptical, given: (1) that a long time has past since the project started and there is not yet a draft in ballot; (2) there does not appear to be a lot of people supporting the project. If you or any person or organization you know of cares to see that this project is completed, I suggest you contact Diane and volunteer to be listed as a participant or potential member of the balloting group. Showing a substantial and well balanced (between users and implementers) working group and balloting group is important in the IEEE process. |
|
|
|
[Agenda]
|
Note regarding procedure |
In procedural terms, this portion of the meeting will be conducted in the form of a "Committee of the Whole." Typically, discussion of a business item requires the tabling of a motion and discussion for and against the proposed motion. Instead, a possible outcome of this discussion would be the phrasing of a motion, either for immediate consideration or for a subsequent email ballot. Other outcomes might include formation of an ad hoc group for further study or referral to an existing Rapporteur Group. |
|
Terms of Discussion |
The discussion will consider three topics:
|
|
|
|
[Agenda]
|
None is anticipated. |
[Agenda]
|
Background |
Ada-Europe has submitted a request for Category C Liaison with SC22/WG9. [See N402] |
|
|
|
|
Resolution |
[Agenda]
|
Background |
ACM SIGAda has submitted a request for Category C Liaison with SC22/WG9. [See N407] Email from Currie Colket, Chair of SIGAda, 6 June 2002: Dear Mr. Jim Moore, Convenor of WG9: Please find attached a "Request for Establishment of Category C Liaison between SC 22/WG 9 and the Association for Computing Machinery's (ACM's) Special Interest Group on Ada (SIGAda)". We request ISO/IEC JTC1/SC22 WG9 consider this request and approve it at your next meeting on 21 June 2002. We recognize that it must be approved up the ISO chain before an approval becomes final. For your information, ACM also has an approval cycle for such liaisons with external organizations. The following approvals are required: 1. Headquarters ACM must staff the liaison request for legal/financial obligations. 2. The Special Interest Group Governing Board (SGB) Executive Committee (EC) must approve the liaison request. The SGB is a board consisting of a representative of each of the ACM SIGs. There are approximately 30-40 SIGs. Each is a professional volunteer. It meets twice a year. To conduct business more efficiently the SGB EC was created. It consists of SGB volunteers elected by the individual SIGs. 3. The ACM Executive Committee (EC) must finally approve the liaison request. The ACM EC consists of the volunteer and professional staff governing ACM. Currently the ACM HQ has completed its staffing activities and has forwarded the request for approval to Alain Chesnais, the Chair of the SGB EC. Consequently the ACM staff believes the Liaison Request is in the best interest of ACM and should be eventually approved. The SGB EC will be meeting this weekend (for its next scheduled meeting of the SGB EC). The Liaison Request is expected to be approved by the SGB EC. Alain Chesnais is personally in favor of the liaison agreement and will lend his support for its approval at the SGB EC and at the ACM EC. Alain Chesnais knows of the deadlines associated with the agenda for the WG9 meeting and has told me that I should go ahead and submit the Liaison Request to WG9, as if it had already been approved by the ACM EC. Consequently, the Liaison Request is submitted for WG9 consideration. We think this is an important step that will benefit the entire Ada community. We look forward to its approval by WG9 and the subsequent approvals of ISO and the Ada EC. I will keep you informed as it completes its approval cycle through ACM. On behalf of ACM SIGAda, |
|
|
|
|
Resolution |
[Agenda]
We appreciate the comfortable accommodations provided by Ada-Europe. The following resolution expresses WG9's gratitude.
We appreciate the services of the meeting Secretary. The following resolution expresses WG9's gratitude.
We appreciate the continuing services of the WG9 Webmaster. The following resolution expresses WG9's gratitude.
The printed version of the Consolidated Ada Reference Manual was published this year by Springer-Verlag. The following resolution thanks the responsible parties.
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]
|
|
|
[Agenda]
Resolutions will be renumbered when the minutes are produced.
The minutes of Meeting #41 as contained in document N400 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 continuing service:
[Discussion] [Agenda]
WG9 schedules future meetings as follows:
[Discussion] [Agenda]
In accordance with 3.3.1.1 of the JTC1 Directives, ISO/IEC JTC1/SC22/WG9 confirms the Category C liaison request of Ada-Europe contained in N402 and forwards the request to SC22 for its consideration and any actions needed to effect approval of the liaison. The convener of WG9 is directed to implement the liaison relationship upon approval by SC22.
[Discussion] [Agenda]
In accordance with 3.3.1.1 of the JTC1 Directives, ISO/IEC JTC1/SC22/WG9 confirms the Category C liaison request of ACM SIGAda contained in N407 and forwards the request to SC22 for its consideration and any actions needed to effect approval of the liaison. The convener of WG9 is directed to implement the liaison relationship upon approval by SC22 and SIGAda's parent organization, the Association for Computing Machinery.
[Discussion] [Agenda]
WG9 approves the procedures of the ARG as described in N406.
[Discussion] [Agenda]
WG9 receives N405, Recommendation on ISO/IEC 13813 from the UK, and N404, Working Draft of a Revised ISO/IEC 13813. To consider the recommendations of the UK:
WG9 expresses its appreciation to the UK, John Barnes, and Don Sando for their diligent efforts in preparing this material.
[Discussion] [Agenda]
WG9 approves the following AIs as written by the ARG, subject to their final editorial correction by the ARG, for incorporation into the planned Amendment to ISO/IEC 8652:
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to Ada-Europe for their gracious accommodations in hosting Meeting #42.
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to ??? for serving as Secretary of Meeting #42.
[Discussion] [Agenda]
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to Clyde Roby for his continuing service in maintaining the WG9 Web Page.
[Discussion] [Agenda]
Noting the recent publication of the printed version of the Consolidated Ada Reference Manual, ISO/IEC JTC1/SC22/WG9 congratulates and thanks Alfred Strohmeier and Randy Brukardt for their efforts in completing this project.
[Discussion] [Agenda]
|
The meeting is planned for adjournment by 1:00 pm. |
[Agenda]
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 Minutes and Resolutions for Meeting #38 of ISO/IEC JTC1/SC22/WG9, Friday, 30 June 2000, Potsdam, Germany
N378 Plenary Meeting Report of ISO/IEC JTC1/SC22, 11-15 September 2000, Nara, Japan
N385 Minutes and Resolutions for Meeting #39 of ISO/IEC JTC1/SC22/WG9, Friday, 17 November 2000, Laurel, Maryland, USA.
N388 Request for Subdivision of Project ISO/IEC 8652:1995
N389 Minutes, Meeting #40 of ISO/IEC JTC1/SC22/WG9, Friday, 18 May 2001, Leuven, Belgium
N390 Request to Make a Technical Report Freely Available on the Web
N393, Detailed Agenda, Meeting #41 of ISO/IEC JTC1/SC22/WG9, Friday, 5 October 2001, Bloomington, Minnesota, USA
N397, Initial Working Draft of Revised ISO/IEC 13813
N400, Minutes, Meeting #41 of ISO/IEC JTC1/SC22/WG9, Friday, 5 October 2001, Bloomington, Minnesota, USA
N401, Announcement and Draft Agenda, Meeting #42 of ISO/IEC JTC1/SC22/WG9, Friday, 21 June 2002, Vienna, Austria
N402, Request for Establishment of Category C Liaison between ISO/IEC JTC1/SC 22/WG 9 and Ada-Europe
N403, Email Ballot Result, Fall 2002 Meeting of WG9
N404, Working Draft, Revision of ISO/IEC 13813
N405, Recommendation on ISO/IEC 13813 from the UK
N406, Procedures of the Ada Rapporteur Group
N407, Request for Establishment of Category C Liaison between ISO/IEC JTC1/SC 22/WG 9 and ACM SIGAda
ISO Web Site: http://www.iso.ch/
JTC1 Web Site: http://www.jtc1.org/
SC22 Web Site: http://www.open-std.org/jtc1/sc22/
WG9 Web Site: http://www.open-std.org/jtc1/sc22/wg9/
ACAA Web Site: http://www.ada-auth.org/
ACAA Web Site for ARG Minutes: http://www.ada-auth.org/arg-minutes.html
ACAA Web Site for AIs: http://www.ada-auth.org/cgi-bin/cvsweb.cgi/AIs/
Ada-Europe Web Site: http://www.ada-europe.org/
Ada-Europe 2002 Conference Web Site: http://www.ada-europe.org/conference2002.html
SIGAda Web Site: http://www.acm.org/sigada/
[Agenda]
End of Document