From owner-sc22wg5@open-std.org Fri Sep 22 13:11:45 2006 Return-Path: X-Original-To: sc22wg5-dmo5 Delivered-To: sc22wg5-dmo5@open-std.org Received: by open-std.org (Postfix, from userid 521) id 724FD26C0A; Fri, 22 Sep 2006 13:11:45 +0200 (CET DST) X-Original-To: sc22wg5@open-std.org Delivered-To: sc22wg5@open-std.org Received: from dkuug.dk (ptah.dkuug.dk [195.215.30.66]) by open-std.org (Postfix) with ESMTP id C14E52178E for ; Fri, 22 Sep 2006 13:11:44 +0200 (CET DST) Received: from mk-smarthost-2.mail.uk.tiscali.com (mk-smarthost-2.mail.uk.tiscali.com [212.74.114.38]) by dkuug.dk (8.12.10/8.9.2) with ESMTP id k8MBALVI031437 for ; Fri, 22 Sep 2006 13:10:31 +0200 (CEST) (envelope-from j.k.reid@rl.ac.uk) Received: from mk-smarthost-3.mail.uk.tiscali.com ([212.74.114.39]) by mk-smarthost-2.mail.uk.tiscali.com with ESMTP; 22 Sep 2006 12:06:37 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AQAAADpgE0WLcQICBwQKBwYd Received: from 88-105-178-197.dynamic.dsl.as9105.com ([88.105.178.197]:2766) by mk-smarthost-3.mail.uk.tiscali.com with esmtp (Exim 4.30) id 1GQird-000Hzz-Ip; Fri, 22 Sep 2006 11:06:37 +0000 Message-ID: <4513C3BE.30303@rl.ac.uk> Date: Fri, 22 Sep 2006 12:06:38 +0100 From: John Reid Reply-To: j.k.reid@rl.ac.uk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: wg5 Subject: SC22 London Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0 () Sender: owner-sc22wg5@open-std.org Precedence: bulk WG5, The SC22 meeting ended a day early (hurrah!), which gives me a chance to give you an early report. I will confine myself to the four items on which I asked for SC22 actions (see section 5 of my report, N1662). Best wishes, John. 1. Fortran 2008 It seems that a New Work Item (NWI) does not need to be established for the revision of a standard. This is a relief to me since I thought it was needed and had not prepared the document. It was agreed (Resolution 06-16) that ISO/IEC 1539-1:2004 is now under revision. Actually, this could have been deferred until next year since our schedule says that the first draft will be submitted in October 2007. I decided not to defer it since the truth of the matter is that the standard is 'under revision' and I do not want it to look as if the schedule is slipping. 2. TR on further interoperability with C Resolution 06-14 instructs the secretariat to conduct a NWI ballot on a type 2 TR on further interoperability with C. I will send the document that I circulated by email a couple of months ago to the secretariat next week when I am back in my office (and make it N1667). 3. Final processing of documents A significant concern for WG5 is the final processing of documents by ITTF. You will recall that changes were made to Corrigendum 1 without consultation. Last year, SC22 passed this resolution: .............................................. Resolution 05-06: Document Submission to ITTF JTC 1/SC 22 notes that its project editors have been having substantial problems with the publication process. For example, in a number of recent publications, internal bookmarks were removed, rendering the documents difficult to navigate. JTC 1/SC 22 instructs its Secretariat to request the ITTF to allow the following mode of processing to be applied at the request of the project editor before publication of a JTC 1/SC 22 standard, TR, or corrigendum. 1. The project editor sends the approved format file (currently PDF) together with any additional source files necessary for ITTF to note and verify changes. 2. The ITTF lists the changes it requires. 3. The project editor constructs a new approved format and source files and sends them. 4. Steps 2. and 3. are repeated until no changes are needed. The purpose of this procedure is to improve the quality of the final document. Unanimous .............................................. This resolution seems to have been completely ignored by ITTF. My suggestion was that John Hill (SC22 chairman) speak directly with the person in charge of publications at ITTF and I got the procedure (steps 1-4) repeated in a new resolution that instructs John to do this. 4. Free availability of documents Another significant concern for WG5 is the free availability of documents, specially TRs. Other WGs, specially C, felt even more strongly than us about it and there was a break-out session to discuss it. John Hill was also charged with asking ITTR for a document outlining the requirements for free availability to be created. The best that is available now is http://www.open-std.org/jtc1/sc22/open/n4114.pdf A resolution asked for TR's like ours, which contain no self-contained implementatable specifications, to be freely available. There was also a separate resolution on TR 19767 (enhanced module facilities) to be made freely available with the following rationale: ISO/IEC TR 19767 is not a standalone document. It is of little use without the base document ISO/IEC 1539-1:2004. The free availability of this document will promote awareness of existing JTC 1 work and will create sales of current JTC 1 documents. JTC 1/SC22 believes that this request falls under the rules for the selection of criteria contained in JTC 1/SC22 N 4114 (JTC 1 N 7269). We could not see a reason in N 4114 for making the two earlier TRs freely available, since they depend on an outdated standard that is now available for a nominal price ($30). I think that they, too, should be available for a nominal price, but pricing is outwith the scope of SC22. It was suggested that we should raise this matter through our national bodies.