6 ballot objections, comments, and editorial comments were received. The following table summarizes the resolutions. Complete text of each objection, comment, or editorial comment and its detailed resolution follows the table. Number Balloter's ID Resolution -------- ------------- ---------- ERN #1 [Cragun-1] Reject ERN #2 [Hoelzl-1] Accept as marked ERN #3 [Riley-1] Reject ERN #4 [Moore-1] Reject ERN #5 [Karocki-1] Accept as marked ERN #6 [Karocki-2] Accept as marked _____________________________________________________________________________ OBJECTION Enhancement Request Number 1 don.cragun@sun.com .5 aardvark report (rdvk# 1) [Cragun-1] Wed, 16 Jun 2004 19:55:17 -0500 (CDT) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject__X__ Technical Reviewers' Response: The PASC SSWG-RT Working Group and the PASC Ada Working Group are trying to extend the life of IEEE Std 1003.5-1999 by five years, because they believe that the standard is still useful to some Ada programmers interested in POSIX functionality. The Technical Reviewers acknowledge that, ideally, IEEE Std 1003.5-1999 would be revised to align with the 2004 edition of ISO/IEC 9945. However, at this point, there are not enough people in the Ada/POSIX community with enough funding to undertake the revision effort. Therefore, the choice is between withdrawing and reaffirming the standard. The balloting group, which includes developers as well as current users of IEEE Std 1003.5-1999, has indicated its support of reaffirming IEEE Std 1003.5-1999 with a 93% affirmative vote. In addition, the recently approved IEEE Std 1003.13-2003 profile standard (a revision of IEEE Std 1003.13-1998) defines Ada profiles as well as C profiles, and the Ada profiles are based on IEEE Std 1003.5-1999. It may also be noted that a language binding such as 1003.5 depends only indirectly on the base standard 1003.1, as 1003.5 defines a complete set of Ada APIs that only very loosely follow 1003.1. In particular, the threads APIs of 1003.1 are used to implement Ada tasking, and so do not appear as APIs in 1003.5. In fact, one can implement 1003.5 using a freestanding runtime system, with no UNIX kernel needed. _____________________________________________________________________________ Page: 0 Line: 0 Section: 0 Problem: This standard is an Ada Language binding to ISO/IEC 9945-1:1990. Since ISO/IEC 9945-1:1990 has been superseded by ISO/IEC 9945-1:2002, 9945-2:2002, 9945-3:2002, and 9945-4:2002; it is not appropriate to reaffirm this standard. Action: Revise IEEE Std 1003.5 to align with the common revised IEEE, ISO/IEC, and Open Group standard; or withdraw IEEE Std 1003.5-1999. _____________________________________________________________________________ EDITORIAL Enhancement Request Number 2 w.hoelzl@ieee.org .5 aardvark report (rdvk# 2) [Hoelzl-1] Wed, 16 Jun 2004 19:55:17 -0500 (CDT) _____________________________________________________________________________ Accept_____ Accept as marked below__X__ Duplicate_____ Reject_____ Technical Reviewers' Response: The Technical Reviewers have reviewed the balloter's comments and accept most of the balloter's proposed corrections. Since this is a reaffirmation ballot, no changes can be made to the published standard. However, typographical and editorial errors can be corrected via IEEE standards errata sheets. The IEEE Editorial Staff has reviewed the balloter's proposed corrections and agree that they are sufficiently editorial in nature to be eligible for publication in an IEEE standards errata sheet. The Technical Reviewers will work with the IEEE Editorial Staff in preparing an errata sheet for the reaffirmed standard. Electronic copies of IEEE standards errata sheets can be obtained from the IEEE website at ; paper copies can be ordered from IEEE Customer Service at 1-800-678-4333 in the United States and Canada or 1-732-981-0060 outside the United States and Canada. The IEEE also includes any relevant errata sheets in paper copies of standards ordered from the IEEE. _____________________________________________________________________________ Page: 0 Line: 0 Section: 0 Problem: title page: < proviced by the Ada. > provided by the Ada language. p103 < implementationdefinedsystem process. > implementation defined system process. p104 < shall be closed, as if > shall be closed as if p151 < POSIX.POSIX_Error with error code > POSIX_Error with error code p212 < Sockets Detailed Network Interface option is supported:An > Sockets Detailed Network Interface option is supported: An p242 < If the Synchronized I/Ooption and the Ioption is supported:f > If p247 < In other wordsshall, > In other words, p265 < Map CRto NL on input > Map CR to NL on input p293 < possibilit > possibility p327 < restriction on the alignment of First > restriction on the alignment of First. p376 < POSIX.POSIX_Error > POSIX_Error p379 < Nno raw data > No raw data p424 < The Set__Period procedure > The Set_Period procedure p426 < Value parameter. that exist. Each option, > Value parameter. Each option, p466 < e.g.because > e.g. because p488 < protocol-specificwhether > protocol-specific whether < different destination peer , > different destination peer, p491 < protocol-specificwhether > protocol-specific whether < protocol-specificfeatures > protocol-specific features < protocol-specificcalls > protocol-specific calls p493 < protocol-specificwhether > protocol-specific whether p494 < protocol-specificand > protocol-specific and p495 < Expedited dataare > Expedited data are p505 < protocolspecificsocket address types > protocolspecific socket address types p506 < protocol-specificancillary data > protocol-specific ancillary data p507 < protocol-specificancillary data > protocol-specific ancillary data p508 < protocolspecificspecifications > protocolspecific specifications p516 < protocol-specificfunction > protocol-specific function p521 < protocol-specificwhether > protocol-specific whether p526 < Socket os not a valid descriptor. > Socket is not a valid descriptor. p529 < Socket os not a valid descriptor. > Socket is not a valid descriptor. p532 < Socket os not a valid descriptor. > Socket is not a valid descriptor. p533 < Socket os not a valid descriptor. > Socket is not a valid descriptor. p534 < Socket os not a valid descriptor. > Socket is not a valid descriptor. p563 < Two Ada 83constructs > Two Ada 83 constructs p592 < in whicn the subsystems are written. > in which the subsystems are written. p595 < NOTE: As of Ada 95there is > NOTE: As of Ada 95 there is p598 < to accept either a pathname of a File_Descriptor. > to accept either a pathname or a File_Descriptor. p607 < IN other words, > In other words, p616 < A.14 of the Ada RM {1}adarm states > A.14 of the Ada RM {1} states p620 < using Ada 83and this standard. > using Ada 83 and this standard. p627 < Protected operations serve ..., but are > p631 < e.g.where > e.g. where p643 < for Ada 83compilers, > for Ada 83 compilers, p693 < pathconf(), _PC_PATH_MAX() > pathconf(), _PC_PATH_MAX p703 < . . . . . . . . . . . . . . POSIX > (delete duplicate line) p799 < The following behavior for XTI functions is specified:ax > The following behavior for XTI functions is specified: p819 < Accept_Connectoin, procedure . . . 508 > Accept_Connection, procedure . . . 508 p829 < Events and =t Event_Requires_Attention > Events and Event_Requires_Attention < Events and =t Look > Events and Look, p838 < Interoperability of =t File_Type and =t File_Descriptor > Interoperability of File_Type and File_Descriptor p866 < The Option Value =t Unspecified, > The Option Value Unspecified, < The =t Communications_Provider_Info > The Communications_Provider_Info Action: Make the above editorial changes. _____________________________________________________________________________ OBJECTION Enhancement Request Number 3 jriley@dcscorp.com .5 aardvark report (rdvk# 6) [Riley-1] Wed, 16 Jun 2004 19:55:17 -0500 (CDT) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject__X__ Technical Reviewers' Response: The balloting group disagrees with the contention that the standard is obsolete and useless. In fact, the balloting group includes current users of the standard. Also see the rationale for the rejection of [Cragun-1]. _____________________________________________________________________________ Page: 0 Line: 0 Section: 0 Problem: The document as it stands does not reflect the current POSIX standard. Also, the structure of the API is based on Ada 83 and does not effectively use madern, widely used Ada 95 constructs. The document is obsolute and useless as it stands. Action: Either delete the document as obsolete or redo to reflect the new POSIX standard and utilize appropriate programming features reflecting modern programming practice. _____________________________________________________________________________ EDITORIAL Enhancement Request Number 4 james.w.moore@ieee.org .5 aardvark report (rdvk# 5) [Moore-1] Wed, 16 Jun 2004 19:55:17 -0500 (CDT) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject__X__ Technical Reviewers' Response: The standard follows PASC naming and publication conventions. Namely, the amendment is published in the context of its base standard (and any previous amendments to the base standard). In this way, the standard and all its amendments become available to users of the standard in the form of a single coherent document. _____________________________________________________________________________ Page: 1 Line: 0 Section: 0 Problem: Why does page 1 claim that it is part of an amendment when it is obviously not the amendment but rather the base standard as amended? Action: Remove the part of the title that claims it is the amendment. _____________________________________________________________________________ EDITORIAL Enhancement Request Number 5 pkar@ieee.org .5 aardvark report (rdvk# 3) [Karocki-1] Wed, 16 Jun 2004 19:55:17 -0500 (CDT) _____________________________________________________________________________ Accept_____ Accept as marked below__X__ Duplicate_____ Reject_____ Technical Reviewers' Response: The Technical Reviewers have reviewed the balloter's comment and accept the balloter's proposed correction. Since this is a reaffirmation ballot, no changes can be made to the published standard. However, typographical and editorial errors can be corrected via IEEE standards errata sheets. The IEEE Editorial Staff has reviewed the balloter's proposed correction and agree that it is sufficiently editorial in nature to be eligible for publication in an IEEE standards errata sheet. The Technical Reviewers will work with the IEEE Editorial Staff in preparing an errata sheet for the reaffirmed standard. Electronic copies of IEEE standards errata sheets can be obtained from the IEEE website at ; paper copies can be ordered from IEEE Customer Service at 1-800-678-4333 in the United States and Canada or 1-732-981-0060 outside the United States and Canada. The IEEE also includes any relevant errata sheets in paper copies of standards ordered from the IEEE. _____________________________________________________________________________ Page: 557 Line: 3 Section: B.1.9.1 Problem: "or eturn the error code" Action: "or return the error code" _____________________________________________________________________________ EDITORIAL Enhancement Request Number 6 pkar@ieee.org .5 aardvark report (rdvk# 4) [Karocki-2] Wed, 16 Jun 2004 19:55:17 -0500 (CDT) _____________________________________________________________________________ Accept_____ Accept as marked below__X__ Duplicate_____ Reject_____ Technical Reviewers' Response: The Technical Reviewers have reviewed the balloter's comment and accept the balloter's proposed correction. Since this is a reaffirmation ballot, no changes can be made to the published standard. However, typographical and editorial errors can be corrected via IEEE standards errata sheets. The IEEE Editorial Staff has reviewed the balloter's proposed correction and agree that it is sufficiently editorial in nature to be eligible for publication in an IEEE standards errata sheet. The Technical Reviewers will work with the IEEE Editorial Staff in preparing an errata sheet for the reaffirmed standard. Electronic copies of IEEE standards errata sheets can be obtained from the IEEE website at ; paper copies can be ordered from IEEE Customer Service at 1-800-678-4333 in the United States and Canada or 1-732-981-0060 outside the United States and Canada. The IEEE also includes any relevant errata sheets in paper copies of standards ordered from the IEEE. _____________________________________________________________________________ Page: 607 Line: 2 Section: B.6.3.1 Problem: "IN another words" Action: "In another words"