From isaak@csac.zko.dec.com Tue May 31 06:24:19 1994 Received: from crl.dec.com by dkuug.dk with SMTP id AA19934 (5.65c8/IDA-1.4.4j for ); Tue, 31 May 1994 16:25:15 +0200 Received: by crl.dec.com; id AA24256; Tue, 31 May 94 10:22:01 -0400 Received: by csac (5.65/fma-100391/BobG-15-Feb-93);id AA03569; Tue, 31 May 1994 10:24:19 -0400 Date: Tue, 31 May 1994 10:24:19 -0400 From: isaak@csac.zko.dec.com (Jim Isaak-NEW: respond via isaak@csac.enet.dec.com) Message-Id: <9405311424.AA03569@csac> To: sc22wg15@dkuug.dk Subject: EWOS Liaision to WG15 X-Charset: ASCII X-Char-Esc: 29 Below is a note from Jeremy Tucker with some insight on the status of the EWOS Liaision request. He identifies 3 points in his note, which seem to cover the areas of interest to EWOS in WG15 work. And, I might note that this covers all of our currently assigned projects as I read it. I would appreciate feedback before the SC22 meeting in September on any particular ways of stating areas of anticipated liaision, from experts or member bodies. Thanks, Jim Isaak ============================================== Return-Path: flambe::tuckerj@dodo.logica.co.uk Received: by csac (5.65/fma-100391/BobG-15-Feb-93); id AA28885; Fri, 20 May 1994 09:34:23 -0400 Date: Fri, 20 May 1994 09:34:17 -0400 From: flambe::tuckerj@dodo.logica.co.uk To: "Jim Isaak" Cc: "Dave Rayner" Subject: EWOS liaison to SC22/WG15 Jim, I was glad to be able to meet you last week and learn about the work of SC22/WG15 at first hand. I found the meeting very useful, and I hope that the resolutions we were able to draft will speed up progress in SGFS and help us in our profiling work. I've seen the letter from Mr. Cote to Luc van den Berghe about the request for liaison from EWOS, in which he says he will ask you to identify the projects that are targeted. From our side, the focus of the liaison is on functional standardisation (in the form of ISPs), from three points of view: (1) POSIX standards that we would expect to reference in ISPs for OSE profiles - this could be any of them; (2) POSIX profiles that may be submitted for processing towards ISP, or that may be referenced in other ISPs; (3) conformance in the POSIX world, in order to develop appropriate conformance text in TR 10000 and appropriate conformance statements in draft ISPs. We will be particularly interested in issues that arise when POSIX specifications are combined in profiles - whether with each other or with other types of specification. We shall need to work out when and how to state that such specifications "work with each other", for example such that a file written through one API can be read through another. I hope this helps. With best wishes, Jeremy