PROPOSAL FOR A NEW WORK ITEM

Date of presentation of proposal:
2003-08-15

Proposer:
UK National Body

Secretariat:
ANSI

ISO/IEC JTC 1/SC 22 N 3632  

A proposal for a new work item shall be submitted to the secretariat of the ISO/IEC joint technical committee concerned with a copy to the ISO Central Secretariat.

Presentation of the proposal - to be completed by the proposer Guidelines for proposing and justifying a new work item are given in ISO Guide 26.

Title (subject to be covered and type of standard, e.g. terminology, method of test, performance requirements, etc.)
A Technical Report of the Conflicts between the ISO/IEC 9945 (POSIX®) Standard and the Linux Standard Base Specification.

Scope (and field of application)
The scope of this new work item proposal is for a Type 3 Technical Report (informative)
detailing the conflicts between ISO/IEC 9945 (POSIX) and the Linux Standard Base.

Purpose and justification - attach a separate page as annex, if necessary

The purpose of the TR would be to scope the areas of conflict between the specifications, and then to pass
the resulting report to the appropriate technical committee for consideration with the aim of future harmonization
between the standards efforts. The justification is that the May 2003 Linux Study Group meeting has recommended
future action towards adopting Linux as a JTC1 standard, and  most likely adopting the Linux Standard Base (LSB)
specification as a PAS. Thus this TR will become directly relevant for future harmonization activities.

 

 

Programme of work

If the proposed new work item is approved , which of the following document(s) is (are) expected to be developed?
____ a single International Standard more than one International Standard (expected number: ........ )
____ a multi-part International Standard consisting of .......... parts
____ an amendment or amendments to the following International Standard(s) ....................................
_X__ a technical report , type ...3.......

Relevant documents to be considered

ISO/IEC 9945:2003 Parts 1 to 4
The Linux Standard Base Specification Version 1.9

 

Cooperation and liaison
The Open Group
The Austin Group
The Linux Standard Base

Preparatory work offered with target date(s)
A complete draft is enclosed with this proposal. This is thought to be complete as of the submission date.

Signature:

Will the service of a maintenance agency or registration authority be required? ......No..............
- If yes, have you identified a potential candidate? ................
- If yes, indicate name .............................................................

Are there any known requirements for coding? .......No............
-If yes, please specify on a separate page

Are there any known requirements for cultural and linguistic adaptability? ..No.......
- If yes, please specify on a separate page

Does the proposed standard concern known patented items? ........No.........
- If yes, please provide full information in an annex

Comments and recommendations of the JTC 1 Secretariat - attach a separate page as an annex, if necessary

Comments with respect to the proposal in general, and recommendations thereon:
It is proposed to assign this new item to JTC 1/SC 22

Voting on the proposal - Each P-member of the ISO/IEC joint technical committee has an obligation to vote within the time limits laid down (normally three months after the date of circulation).

Date of circulation:
2003-08-26

Closing date for voting:
2003-11-26

Signature of SC 22 Secretary:
Matt Deane

NEW WORK ITEM PROPOSAL - PROJECT ACCEPTANCE CRITERIA

 

 

Criterion

Validity

Explanation

A Business Requirement

 

 

A.1 Market Requirement

Essential _X_
Desirable ___
Supportive ___

ISO 9945 (POSIX) is be an important standard in use throughout the world. There is a significant investment in applications developed for the ISO POSIX standard. With the emergence of a standardization initiative for the Linux operating system there are some areas of conflict that have been identified between the Linux Standard Base  (LSB) specification and the ISO POSIX standards. There is an essential market requirement that the conflicts be resolved so that an application can be written to conform to both standards. Hundreds of millions of dollars of applications are built upon these standards.
 

A.2 Regulatory Context

Essential ___
Desirable ___
Supportive ___
Not Relevant _X_

 

B. Related Work

 

 

B.1 Completion/Maintence of current standards

Yes _X_
No__

This TR will be used as consideration input for a future revision of the
ISO/IEC 9945 standard (POSIX). This TR will also provide guidance to the
LSB (et al) effort to move closer to POSIX.

B.2 Commitment to other organization

Yes _X_
No___

The Austin Group (a joint working group of ISO/IEC SC22/WG15, The Open Group and the IEEE, that maintains and the develops the POSIX specifications and the core volumes of the Single UNIX Specification).

B.3 Other Source of standards

Yes _X_
No___

The May 2003 Linux Study Group meeting has recommended future
action towards adopting Linux as a JTC1 standard, and most
likely adopting the Linux Standard Base (LSB) specification
as a PAS. Thus this TR will become directly relevant for future
harmonization activities.

 

C. Technical Status

 

 

C.1 Mature Technology

Yes _X_
No___

 

C.2 Prospective Technology

Yes ___
No_X_

The TR is a report on the current state of the art. 

C.3 Models/Tools

Yes ___
No_X_

POSIX and the LSB already have a set of tools to discover deviations from their specifications.

D. Conformity Assessment and Interoperability

 

 

D.1 Conformity Assessment

Yes ___
No_X_

 

D.2 Interoperability

Yes ___
No_X_

 

E. Other Justification

 

This NP was initiated as a result of a resolution from the May 2003
Linux Study Group.

Notes to Proforma

A. Business Relevance. That which identifies market place relevance in terms of what problem is being solved and or need being addressed.

A.1. Market Requirement. When submitting a NP, the proposer shall identify the nature of the Market Requirement, assessing the extent to which it is essential, desirable or merely supportive of some other project.

A.2 Technical Regulation. If a Regulatory requirement is deemed to exist - e.g. for an area of public concern e.g. Information Security, Data protection, potentially leading to regulatory/public interest action based on the use of this voluntary international standard - the proposer shall identify this here.

B. Related Work. Aspects of the relationship of this NP to other areas of standardization work shall be identified in this section.

B.1 Competition/Maintenance. If this NP is concerned with completing or maintaining existing standards, those concerned shall be identified here.

B.2 External Commitment. Groups, bodies, or fora external to JTC1 to which a commitment has been made by JTC for cooperation and or collaboration on this NP shall be identified here.

B.3 External Std/Specification. If other activities creating standards or specifications in this topic area are known to exist or be planned, and which might be available to JTC1 as PAS, they shall be identified here.

C. Technical Status. The proposer shall indicate here an assessment of the extent to which the proposed standard is supported by current technology.

C.1 Mature Technology. Indicate here the extent to which the technology is reasonably stable and ripe for standardization.

C.2 Prospective Technology. If the NP is anticipatory in nature based on expected or forecasted need, this shall be indicated here.

C.3 Models/Tools. If the NP relates to the creation of supportive reference models or tools, this shall be indicated here.

D. Any other aspects of background information justifying this NP shall be indicated here.

D. Conformity Assessment and Interoperability

D.1 Indicate here if Conformity Assessment is relevant to your project. If so, indicate how it is addressed in your project plan.

D.2 Indicate here if Interoperability is relevant to your project. If so, indicate how it is addressed in your project plan.