Austin Group announces POSIX Revision Draft 1

*** Subject:  Austin Group announces POSIX(R) Revision Draft 1 now available

Date: Fri, 30 Jun 2006 15:57:33 +0100


Dear All,

I am pleased to announce the availability of draft 1 of
Revision to the Austin Group specifications.
This is the first draft of the revision project and is a committee
draft, for the full roadmap to the revision see Austin/284

This is available from the Austin Group web site, you need
to login using your individual id and password at
        http://www.opengroup.org/austin/login.html

The review period commences on July 1st and completes at 8am UK local
time on September 1st.

All comments on these documents should be sent in Aardvark format to
the Austin Review  reflector, Please read the following documents at
the download point prior to sending in comments:

        - Committee draft development procedures
        - Committee document maintenance procedures
        - How to submit a review comment
        - Draft reviewers notes.

I attach the reviewers notes.
Happy reviewing!
regards

Andrew

--------------------------------------------------------------------------
Draft 1 Reviewers Notes = Please Read

These notes accompany Draft 1. Draft 1 is the first committee draft.
Balloting for this draft is confined to the Austin Group only. These
notes should be read prior to reviewing this draft.

The review period for Draft 1 commences July 1st 2006 and completes at
8am UK local time on September 1 2006. A face to face meeting to review
comments is scheduled for September 12-16 2006.

The document is the first draft of this revision cycle and is a
committee draft. The purpose of the draft 1 review is to ensure that the
changes arising from finalized interpretations and SD/5 have been
applied as the review group intended. Thus, for this draft objections
can only be accepted on certain sections of the document that changed
for these reasons. 


     1. An objection will only be accepted if it relates to a change
        resulting from a finalized interpretation (see
        http://www.opengroup.org/austin/interps/ ) or changes arising
        from SD/5 (see Austin/280r1 and Austin/302 ). 
        
        To assist in determining these differences, changes are denoted
        with change bars. An objection to a change must relate to the
        material change and not be for a different matter at the same
        line (note that many of the change bars are due to the editorial
        changes to support the revision, for example the string
        "1003.1-2001" is changed to "1003.1-200x" where it refers in the
        context of the document itself). Please also note that the
        change bars are automatically generated, and often mark the line
        before and after the change as well as the change.
        
        You may raise an objection to a section of the document that has
        not been changed if (and only if) a change is needed for
        alignment with text that has changed elsewhere and the change is
        needed to make the document self-consistent.
        
        If possible when raising an objection it would be helpful for
        reviewers to include a reference to the corresponding Austin
        Group Interpretation or the SD/5 reference, if known. 
        
        If an objection relates to an unchanged part of the document,
        then please file a defect report against the current approved
        standard. The revision project will address defect reports
        against the approved standard until at least June 2007. This is
        recommended if you also require an interpretation against the
        current approved standard. Bug reports against the draft
        revision will not normally lead to interpretations against the
        current approved standard.
        
     2. You may raise a comment on any part of the document
     3. You may raise an editorial comment on any part of the document

Bugs can be reported at http://www.opengroup.org/austin/bugreport.html

Defect reports against the current standard should continue to be sent
to http://www.opengroup.org/austin/defectreport.html

Summary of the Changes
Detailed change history is given on each manual page. The Austin Group
interpretations and Austin/280r1 and Austin/302 should be consulted.

Note that some editorial changes are not noted in the change history,
one notable example in XSH is the global change made to the statement
for reentrant functions; another editorial change has been to italicize
the variable math_errhandling in the maths functions.

Change Request Reports
As there has been no previous ballot rounds, there are no change request
reports for this draft.

For the change requests raised on this draft, as usual there are four
dispositions:

     1. Accept - we agreed with the problem and made the suggested
        change as suggested
     2. Accept as marked - we agreed with the problem and made an
        alternate change to resolve it.
     3. Duplicate - this request is a duplicate of another request,
        please see the other request for the resolution
     4. Reject - we did not agree with the problem statement. 

Where a response is other than an ACCEPT the disposition is documented
in the header text section of the ERN


Known problems and Features
      * Any pages thrown blank, or orphaned tables or sections will be
        fixed up in the final proof document.
      * The front matter and introduction sections still require further
        updates.
      * The index pages are informational only, they would require
        further updates for production.
      * The Referenced Documents section will be updated in the next
        draft.
      * Some technical issues raised by defect reports have yet to be
        finalized and missed the cutoff for this draft (June 12 2006).
        These will be incorporated in future drafts.
      * Reviewers may need to refer to the interpretations repository
        and Austin/280r1 and Austin/302.
      * Change Bars 
        
        These are produced by an automated tool. Please note the
        following:
        
             1. The change bars relate to all changes including
                editorial (i.e. font changes, spelling changes,
                hyphenation, number reformatting).
             2. In some document constructs (e.g list constructs) the
                change bar tool may put out a change bar on the line
                preceeding the change as well as the changed line.
             3. The change bar tool may also put out a line for document
                formatting changes that are not visible to the eye , for
                example deletions, and insertions of page breaks.

________________________________________________________________________
Summary of Key technical CHANGES
      * The changes are too many to list all of them here. Refer to the
        Austin Group Interpretations, Austin/280r1 and Austin/302.
      * One change that should be checked is the separation of _Exit(),
        _exit() and exit() to two separate pages (in XSH).



---
Andrew Josey
The Open Group
Austin Group Chair