PROPOSAL FOR A NEW WORK ITEM
 

Date of presentation of proposal: 
2003-09-30

Proposer: 
JTC 1/SC 22 (Oslo Res. 03-01)

Secretariat: 
ANSI

ISO/IEC JTC 1/SC 22 N 3657 

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:  Native COBOL Syntax for XML Support

Scope (and field of application): Programming Language COBOL

Purpose and justification:  Provide an easy way to read and write XML data. XML is ubiquitous and COBOL users have expressed a strong immediate requirement for this support.  COBOL vendors are starting to design solutions in response to this user demand, and at least one vendor has produced an implementation. Users want XML support to be standardized.  WG4 has reviewed an existing design and agrees that it is a good starting point to enable the COBOL community to manipulate XML. 

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 .....2...... 

Relevant documents to be considered: 

1.  ISO/IEC 1989:2002, Programming Languages – COBOL

2.  Extensible Markup Language (XML) 1.0 (Second Edition) W3C Recommendation 6 October 2000, Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler.

Cooperation and liaison –  none

Preparatory work offered with target date(s)

 

Stage 3, SC22 combined registration and PDTR ballot (3 months)

                                                start                                                                            September 1, 2004

                                                close                                                                           December 1, 2004

 

 

 

Stage 3, second SC22 PDTR ballot (3 months)

                                                start                                                                            June 1, 2005

                                                close                                                                           September 1, 2005

 

Stage 4, JTC1 DTR ballot (3 months):   {Content is final at this point}

                                                start                                                                            March 1, 2006

                                                close                                                                           June 1, 2006

 

Stage 5, TR to ITTF (within 2 months of DTR ballot close)                                August 1, 2006

 

     {Note:  Stage 5, TR to ITTF - if only one public review:  November 1, 2005}

 

Signature:  Don Schricker, Convenor, SC22/WG4

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/WG4.

The proposed project editor is Don Schricker, the convener.

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-09-30

Closing date for voting: 
2003-12-30

Signature of JTC 1/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 ___

Easy access to XML from COBOL is essential

A.2 Regulatory Context

Essential ___
Desirable ___
Supportive ___
Not Relevant _X__

 

B. Related Work

 

 

B.1 Completion/Maintence of current standards

Yes ___
No_X__

 

B.2 Commitment to other organization

Yes ___
No__X_

 

B.3 Other Source of standards

Yes ___
No__X_

 

C. Technical Status

 

 

C.1 Mature Technology

Yes _X__
No___

The definition of the XML language is stable and is the basis for the COBOL design in the proposed technical report.

C.2 Prospective Technology

Yes ___
No_X__

 

C.3 Models/Tools

Yes ___
No_X__

 

D. Conformity Assessment and Interoperability

 

 

D.1 Conformity Assessment

Yes ___
No_X__

 

D.2 Interoperability

Yes ___
No_X__

 

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.