IEEE-SA STANDARDS BOARD
PROJECT AUTHORIZATION REQUEST (PAR) FORM

1. Sponsor Date
of Request
1996-10-28 

2. Assigned Project
Number
P1372

Confer with Staff

3. PAR Approval
Date
_____________

Leave Blank
4. PROJECT TITLE, COPYRIGHT AGREEMENT, AND WORKING GROUP FOR THIS PROJECT
I will write/revise a Standards Publication with the following TITLE (Check only one, Spell out all acronyms) TITLE: Standard for Information Technology - Portable Operating Sustem Interface (POSIX) - Part 1: System Application Programming Interface (API) (Language Independent)
I hereby acknowledge my appointment as Official Reporter (usually the W.G. Chair) to the  [P1372 Working Group]
(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 any 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 not so defined, I agree to and do hereby transfer any right or interest I may have in the copyright to said Standards Publication to IEEE.
 
NAME: DATE:[1996-10-25] 
(Signature of Official Reporter/W.G. Chair)
Type or print name of Working Group Chair:  [Keld Jørn Simonsen]
Title: [Consultant] IEEE Member No: [DKXUG 17]
Company: [Selskabet for Rational Almen Planlægning] Telephone: [+45 3122 65X3] 
Address: [Sankt Jørgens Allé 8] FAX: [+45 3325 65X3] 
City: [København V] State: [Denmark]  ZIP: [DK-1615] E-mail: [Keld@dkxug.dk] 
5. Describe This Project:   (Choose ONE from each group below.)
 
(a) Update existing PAR.         [X] YES       [..] NO        Is this in ballot now? [..] YES    [X] NO
            (Indicate PAR Number/Approval Date.) [P1372 1993-09-15] 
   
(b) [X] New standard
[..] Revision of existing standard {number and year} [...] 
[..] Amendment to an existing standard {number and year} [...] 
[..] Corrigendum to an existing standard {number and year} [...] 
   
(c) [X] Full Use (5-year life cycle)
[..] Trial Use (2-year life cycle)
   
(d) FILL IN TARGET COMPLETION DATE for submittal to IEEE Standards Review Committee (Rev-Com)  [1998-10]

6. Scope of Proposed Project:  (What is being done, including the technical boundaries of the project)

[To provide a computer language independent specification to IEEE Std 1003.1-1996 (including the system APIs, the realtime and threads amendments and the technical corrigenda)]
 


7. Purpose of Proposed Project:  (Why it is being done, including intended user(s) and benefits to user(s).)

[Meet JTC1/SC22 objective for Language Independent Specification.
 Provide a normative reference for binding to specific programming languages.
 Provide a core document for Language independent extention work.
 Capabilities provided are the same as for IEEE Std 1003.1 as referenced above.]
 


8. Sponsor:  (Give full name; spell out all acronyms.)

Society/Committee: [Computer Society/Portable Applications Standards Committee]
 


9.
(a.1)Are you aware of any patents relevant to this project
[..] YES (Attach an explanation)    [X] NO        [..] DO NOT KNOW

(a.2)Are you aware of the possibility of any copyrights relevant to this project

[..] YES (Attach an explanation)    [X] NO        [..] DO NOT KNOW

(a.3)Are you aware of the possibility of any trademarks relevant to this project

[..] YES (Attach an explanation)    [X] NO        [..] DO NOT KNOW

(b)Are you aware of any other projects with a similar scope?

[..] YES (Attach an explanation)    [X] NO        [..] DO NOT KNOW
(c)Is this standard intended to form the basis of an international standard?
[X] YES    [..] NO (Attach an explanation)        [..] DO NOT KNOW
(d)Is this project intended to focus on health, safety, or environmental issues?
[..] YES (Attach an explanation)    [X] NO        [..] DO NOT KNOW
10. Proposed Coordination/Recommended Method of Coordination
      (Coordination is accomplished by the following: Circulation of Drafts or Liaison Membership or Common Membership)
 
(a)  Mandatory Coordination:
SCC 10 (IEEE Dictionary) Circulation of Drafts
  SCC 14 (Quantities, Units and Letter symbols) Circulation of Drafts  
       
(b) IEEE Coordination Requested by Sponsor: (Use addtional page if necessary)
If you believe your project will require a Registration Authority, please list IEEE RAC (refer to Working Guide.)
(If no coordination is required, please attach an explanation)
       
COORDINATION METHOD OF CIRCULATION
[ASC X3T5.4] [X] circ./drafts  [..] liaison memb.  [..] common memb.
       
[ISO/IEC JTC1/SC22/WG15 US-TAG] [X] circ./drafts  [..] liaison memb.  [..] common memb.
       
[ISO/IEC JTC1/SC22/WG11] [..] circ./drafts  [..] liaison memb.  [X] common memb.
       
[X] circ./drafts  [..] liaison memb.  [..] common memb.
       
[X] circ./drafts  [..] liaison memb.  [..] common memb.
       
(c) Additional Coordination Requested by Others:  (Leave blank - To be completed by the Standards Staff.)
 
 
 



11. Submitted By:  (This must be the Sponsor Chair or the Sponsor's Liaison Representative to the IEEE Standards Board.)
 
Signature of Submitter:: Date:[10-29-1996]  IEEE Member No.: [0450X055]
Name:  [Lowell Johnson] Title: [PASC Sponsor Chair]
Company: [Unisys] Telephone: [612 635 73X5] 
Address: [167, 32nd Avenue] FAX: [612 635 50X8] 
City: [New Brighton] State: [MN]  ZIP: [55112] E-mail: [3lgj@rsxl.unisys.com] 
 DO NOT WRITE BELOW THIS LINE
Signature IEEE Officer:______________________Date:_____________________
 
Title:_______________________________________________________________