[ubl] UN/CEFACT Release ebXML Core Component Technical Specificationfo r Public Review

["CRAWFORD, Mark" <MCRAWFORD@lmi.org>]

Title: UN/CEFACT Release ebXML Core Component Technical Specification for Public Review

 

UN/CEFACT

United Nations Centre for Trade Facilitation and Electronic Business

UN/CEFACT PRESS RELEASE

   

UN/CEFACT Release ebXML Core Component Technical Specification for Public Review

Geneva, Switzerland, 4 March 2002 - 
UN/CEFACT’s Electronic Business Transition ad-hoc Working Group (eBTWG) is 
announcing the release of its ''ebXML Core Component Technical Specification, 
Part 1, Version 1.8'' (http://www.unece.org/cefact/ebxml/ebXML_CCTS_Part1_V1-8.pdf) 
for Public Review under its Open Development Process.

Under this process 
all interested parties have the opportunity to review, comment on, and 
contribute to Technical Specifications. This step is a critical part of the 
UN/CEFACT Open Development Process. Comments from the public frequently raise 
fundamental process and technical issues - missed by the expert project team 
member – therefore considerably improved the specifications. This public review 
period ends 4 May 2002. Please submit your comments to Hans Armfelt Hansell 
<e-mail: hans.hansell@unece.org > 
(Deputy Director - Trade Development and Timber Division).

In order to 
assist in the review and commenting, the Technical Specification has each line 
start with a unique line number to allow placements of comments against them. 
For each comment, reviewers shall provide the specification's line number range, 
the comment itself, the rational for the comment, and suggestion for 
change.

After the end of the review period the project team will review 
all the comments, criticisms, and suggestions from the public, and further 
refine and improve the specification. As changes are made, the updated document 
and disposition log will be republished at the web site. This will allow 
everyone to not only see the changes, but also the rational behind them and 
reasons for suggestions that were not accepted. Experience has shown that 2or 3 
iterations are enough to address the public comments and to build consensus for 
the final version of the specification.

Hartmut Hermes, Core Component 
Project Team Lead
Klaus-Dieter Naujok, eBTWG 
Chair