From owner-sc22wg5@open-std.org  Mon Jan 15 15:32:11 2007
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dmo5
Delivered-To: sc22wg5-dmo5@open-std.org
Received: by open-std.org (Postfix, from userid 521)
	id 8277C3DFCB; Mon, 15 Jan 2007 15:32:11 +0100 (CET)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
X-Greylist: delayed 1627 seconds by postgrey-1.18 at pingo.cv.ihk.dk; Mon, 15 Jan 2007 15:32:10 CET
Received: from balin.rl.ac.uk (balin.rl.ac.uk [130.246.135.155])
	by open-std.org (Postfix) with ESMTP id 98D572B3A2
	for <sc22wg5@open-std.org>; Mon, 15 Jan 2007 15:32:01 +0100 (CET)
X-RAL-MFrom: <j.k.reid@rl.ac.uk>
X-RAL-Connect: <jkr.cse.rl.ac.uk [130.246.9.202]>
Received: from jkr.cse.rl.ac.uk (jkr.cse.rl.ac.uk [130.246.9.202])
	by balin.rl.ac.uk (8.12.8/8.12.8) with ESMTP id l0FE4mc4032455;
	Mon, 15 Jan 2007 14:04:49 GMT
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
	by jkr.cse.rl.ac.uk (8.12.10/8.12.8) with ESMTP id l0FE4mwF015614;
	Mon, 15 Jan 2007 14:04:48 GMT
Message-ID: <45AB8A00.2040008@rl.ac.uk>
Date: Mon, 15 Jan 2007 14:04:48 +0000
From: John Reid <j.k.reid@rl.ac.uk>
Reply-To: j.k.reid@rl.ac.uk
Organization: Rutherford Appleton Laboratory
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060209 Fedora/1.7.12-1.1.2.legacy
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: WG5 <sc22wg5@open-std.org>
Subject: Final processing of standards
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.39
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

WG5,

John Hill, SC22 chairman, had a face-to-face with Keith Brannon of ITTF in 
Geneva on Tuesday, January 9, 2007. The result is detailed in
ISO/IEC JTC 1/SC22 N4174, which is available as

      http://www.open-std.org/jtc1/sc22/def/n4174.pdf

The good news for us is:

3. Over the past few years several of SC 22's project editors [the people
    who do the work of developing and maintaining the text of standards] have
    had some difficulties working with ITTF's ISO editors. As a result, SC
    22's project editors have had lots of additional work to do to assure
    that ITTF's administrators have not made substantive changes to the text
    of the standards.

    To address this concern SC 22 instructed me to ask that ITTF adopt the
    following process. Brannon agreed for all but the front matter (i.e.,
    boilerplate):

    o  The SC 22 project editor sends the approved format file (currently
       PDF) together with any additional source files necessary to the ITTF
       editor who verifies the text and identifies necessary changes.

    o  The ITTF editor lists the changes ITTF requires and then sends them to
       the SC 22 project editor.

    o  The SC 22 project editor constructs a new approved format and source
       files and sends them to the ITTF editor.

    o  The second and third steps are repeated until no further changes are
       needed.

Let's hope this really happens.

John.