Draft IEEE PAR for the Common Revision AUSTIN-3R1 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IEEE Standards Board Jan98 Project Authorization Request (PAR) Page1(Rev V9) 1. Sponsor Date 2. Assigned Project 3. PAR Approval of Request Number DATE [ ] [P1003 ] ________ [ ] PAR Signature Page Received {IEEE Staff to check Box} 4. Project Title and Working Group/Sponsor for this Project Document type : {Place an X in only one option below} [X] Standard for {Document stressing the verb "SHALL"} [ ] Recommended Practice for {Document stressing the verb "SHOULD"} [ ] Guide for {Document stressing the verb "MAY"} TITLE: [Information Technology -- Portable Operating System Interface (POSIX)] {Copyright release at the end of this form must be submitted with appropriate signatures by postal mail or FAX (1-732-562-1571)} Name of Working Group(WG) : [The "Austin" Joint Working Group ] Name of Official Reporter (usually the WG Chair): [Andrew Josey] Title in WG: [ ] IEEE/Affiliate Memb # [ ]{Required} Organization: [ ] Telephone: [ ] Address: [ ] FAX: [ ] City/State/Zip: [ ] EMAIL: [ ] Name of WG Chair (if different than Reporter): [ ] IEEE/Affiliate Memb # [ ]{Required} Organization: [ ] Telephone: [ ] Address: [ ] FAX: [ ] City/State/Zip: [ ] EMAIL: [ ] Name of Sponsoring Society and Committee: [Computer Society / PASC] [The Open Group / OGTGbase] [ISO JTC1/SC22/WG15] Name of Sponsoring Committee Chair: [ ] Organization: [ ] Telephone: [ ] Address: [ ] FAX: [ ] City/State/Zip: [ ] EMAIL: [ ] 5. Describe this Project by answering each of four questions below: 5a. Update an existing PAR? {Yes/No} [NO] If Yes: Indicated PAR number/approval date [ ] If YES: Attach letter indicating changes/rationale for changes. If Yes: Is this PAR in ballot now? [ ] {Yes/No} 5b. Choose one from the following: b1 -[ ] New Standard b2 -[XX] Revision of existing standard {number and year} [ ] 1003.1-1990 and approved supplements 1003.2-1992 and approved supplements ISO/IEC 9945-1:1996 and approved supplements ISO/IEC 9945-2:1993 and approved supplements The Open Group Single UNIX Specification Version 2 b3 -[ ] Supplement to existing standard {number and year} [ ] 5c. Choose one from the following: c1 -[XX] Full Use (5-year life cycle) c2 -[ ] Trial Use (2-year cycle) 5d. Fill in Target Completion Date to IEEE RevCom [ ] October 2001 6. Scope of Proposed Project {what is being done, including technical boundaries on the work} [ ] {This should be brief (less than 5 lines recommended)} 1003.1-1990 and its supplements + 1003.2-1992 plus its supplements + SUSv2 XSH5 + XCU5 + XBD5 + Portability Considerations from 1003.1/1003.2 plus additional rationale and notes from 1003.1 and 1003.2 + amendments to 1003.1/.2 approved by 12/31/99 - legacy features - obsolescent features + IFF(1003.1g is approved by 12/31/99) then XNS5 & resolutions passed by OGTGnet concerning the included sections of XNS5 + issues raised by IEEE/ISO Interps against .1/.2 and resolutions passed by OGTGbase concerning the included sections of SUSv2 + harmonization of options vs. feature groups. Implies "no curses" in the common standard. What about 1003.2d? As written, this is included. Should we exclude it? Add the overarching requirements (no gratuitous breakage, etc.) PAR Form Page 2 of 3 (RevV9) 7. Purpose of Proposed Project: {why it is being done, including intended users, and benefits to users} [ ] {This should be brief (less than 5 lines recommended)} Provide a single standard addressing the needs of users of all the documents being revised and supported by as much of the overall industry as possible. Address problems discovered during the lifetimes of the current documents. The current standards are approaching ten years or more in age; and this is the promised revision, whose scope is being expanded by including accepted practise based on the contents of the Single UNIX Specification. 8. Intellectual Property {Answer each of the questions below} 8a.Are you aware of any patents relevant to this project? [XX] {Yes, with detailed explanation below/ No} [The "compress" utility may be covered by Unisys' LZW patent ] {Explanation} 8b. Are you aware of any copyrights relevant to this project? [XX] {Yes, with detailed explanation below/ No} [Base documents are copyrighted by their owning organizations. It is the intent of the people doing the work that this be sorted out. ] {Explanation} 8c. Are you aware of any trademarks relevant to this project? [XX] {Yes, with explanation below/ No} [POSIX is a registered trademark of the IEEE; UNIX is a registered trademark of The Open Group.] {Explanation} 9. Are you aware of other standards or projects with a similar scope? [XX] {Yes, with explanation below/ No} [Projects within ISO, IEEE, and Open Group will be open to work together on this single, common standard. Also, there is a complex interaction with ISO C.] {Explanation} 10. International Harmonization Is this standard planned for adoption by another international organization? [YES] {Yes/No/?? if you don't know at this time} If Yes: Which International Organization [ISO/IEC JTC1/SC22/WG15] If Yes: Include coordination in question 13 below If No: Explanation [ ] 11. Is this project intended to focus on health,safety or environmental issues? [NO] {Yes/No/?? if you don't know at this time} If Yes: Explanation? [ ] 12. Proposed Coordination/Recommended Method of Coordination 12a. Mandatory Coordination SCC 10 (IEEE Dictionary) by DR IEEE Staff Editorial Review by DR SCC 14 (Quantities, Units and Letter symbols) by DR 12b. Coordination requested by Sponsor and Method: [SC22/WG15 ] by [CO] {circulation of DRafts/LIaison memb/COmmon memb} [OGTGbase ] by [CO] {circulation of DRafts/LIaison memb/COmmon memb} [PASC SSWG ] by [CO] {circulation of DRafts/LIaison memb/COmmon memb} [PASC SUWG ] by [CO] {circulation of DRafts/LIaison memb/COmmon memb} [SC22/WG14 ] by [LI] {circulation of DRafts/LIaison memb/COmmon memb} [SC22/WG20 ] by [LI] {circulation of DRafts/LIaison memb/COmmon memb} If 1003.1g is approved by 12/31/99, [PASC DSWG ] by [CO] {circulation of DRafts/LIaison memb/COmmon memb} [OGTGnet ] by [CO] {circulation of DRafts/LIaison memb/COmmon memb} {Choose DR or LI or CO for each coordination request} 12c. Coordination Requested by Others: [ ] {added by staff} Additional Explanation Notes: {Item Number and Explanation} [ ]{If necessary, these can be continued on additional pages} PAR Copyright Release and Signature Page Page 3 Rev(V9) 1. Sponsor Date 2. Assigned Project of Request Number [ ] [P ] Title [ ] I hereby acknowledge my appointment as Official Reporter (usually the WG Chair) to the [ ] {Name of Working Group} In consideration of my appointment and the publication of the Standards Publication identifying me, at my option, as an Official Reporter, I agree to avoid knowingly incorporating in the Standards Publication any copyrighted or proprietary material of another without such other's consent and acknowledge that the Standards Publication shall constitute a "work made for hire" as defined by the Copyright Act, and, that as to any work defined, I agree to and do hereby transfer any right or interest I may have in the copyright to said Standards Publication to IEEE. Signature of Official Reporter ______________________ Date _________ Name of Official Reporter (usually the WG Chair): [ ] Title in WG: [ ] IEEE Memb # [ ] Organization: [ ] Telephone: [ ] Address: [ ] FAX: [ ] City/State/Zip: [ ] EMAIL: [ ] Submitted by: (This MUST be the Sponsor Chair or the Sponsor's Liaison Representative to the IEEE Standards Board) Signature of Submitter____________________________ Date ____________ Name of Sponsor Committee Chair: [ ] Relationship to Sponsor: [ ] Organization: [ ] Telephone: [ ] Address: [ ] FAX: [ ] City/State/Zip: [ ] EMAIL: [ ] The submitter must be the sponsoring committee's liaison to the IEEE Standards Board or the chair of the sponsoring committee. The PAR will not be submitted to the Standards Board without the signature of the Official Reporter and the Sponsor Committee Chair. Once the PAR is completed, it shall be forwarded to the person designated by the sponsor as responsible for submitting it to the Standards Board New Standards Committee/NESCOM (normally the sponsoring committee's liaison to the IEEE Standards Board). Be certain to include all attachment sheets and supporting correspondence. The submitter will be notified in writing when the PAR is received and when the PAR will be considered for approval by the Standards Board. After the Standards Board meeting, the submitter and official reporter will be notified in writing of the action taken. Signature by IEEE Officer: _________________________Date: ___________ Title: _____________________________