Date of presentation of proposal: |
Proposer: ISO/IEC JTC 1/SC 22 |
Secretariat: ANSI |
ISO/IEC JTC 1/SC 22 N 3277 |
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.) |
Scope (and field of application) Library extensions of broad interest to users of C++ (possible examples include hashtables, regular expressions, and extensions for C99 compatibility), and potential future directions for the standard C++ library. |
Purpose and justification - attach a separate page as annex, if necessary |
Programme of work
If the proposed new work item is approved , which of the following document(s) is (are) expected to be developed? |
Relevant documents to be considered ISO/IEC 14882 Programming Languages - C++ |
Cooperation and liaison none |
Preparatory work offered with target date(s) 2003 |
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 ................ Are there any known requirements for cultural and linguistic adaptability? .... no ....... Does the proposed standard concern known patented items? ...... no ............. |
Comments with respect to the proposal in general, and recommendations thereon: |
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: |
Closing date for voting: |
Signature of JTC 1/SC 22 Secretary: |
NEW WORK ITEM PROPOSAL - PROJECT ACCEPTANCE CRITERIA |
|
|
Criterion |
Validity |
Explanation |
A Business Requirement |
|
|
A.1 Market Requirement |
Essential ___ |
|
A.2 Regulatory Context |
Essential ___ |
|
B. Related Work |
|
|
B.1 Completion/Maintence of current standards |
Yes ___ |
|
B.2 Commitment to other organization |
Yes ___ |
|
B.3 Other Source of standards |
Yes ___ |
|
C. Technical Status |
|
|
C.1 Mature Technology |
Yes ___ |
|
C.2 Prospective Technology |
Yes _ xx __ |
|
C.3 Models/Tools |
Yes ___ |
|
D. Conformity Assessment and Interoperability |
|
|
D.1 Conformity Assessment |
Yes ___ |
|
D.2 Interoperability |
Yes ___ |
|
E. Other Justification |
|
|
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.