From malcolm@nag.co.uk  Tue Nov  3 18:41:04 1998
Received: from red.nag.co.uk (red.nag.co.uk [192.156.217.2])
	by dkuug.dk (8.8.7/8.8.7) with SMTP id SAA24548
	for <sc22wg5@dkuug.dk>; Tue, 3 Nov 1998 18:40:50 +0100 (CET)
	(envelope-from malcolm@nag.co.uk)
Received: from sedi8.nag.co.uk by red.nag.co.uk via SMTP (920330.SGI/920502.SGI)
	for sc22wg5@dkuug.dk id AA27171; Tue, 3 Nov 98 17:39:41 GMT
Received: by sedi8.nag.co.uk (920330.SGI/920502.SGI)
	for @red.nag.co.uk:sc22wg5@dkuug.dk id AA05586; Tue, 3 Nov 98 17:39:22 GMT
From: malcolm@nag.co.uk (Malcolm Cohen)
Message-Id: <9811031739.AA05586@sedi8.nag.co.uk>
Subject: Re: Date of next year's WG5 meeting
To: sc22wg5@dkuug.dk
Date: Tue, 3 Nov 1998 17:39:19 +0000 (GMT)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>  > If you do correct them, then the J3 dates should also be changed
>  > (making the likely guess that the 2 meetings will be back to back).
> 
> Whereas it seems like a good guess, wouldn't it be good to actually
> co-ordinate with the host before just declaring that the date has
> changed?

Thank you; as it happens NAG would prefer the J3 meeting to be the week
before the new date of the WG5 meeting (i.e. 7-11 June 99) as we have other
activities on during the week of 21-25 June which would make organising the
J3 meeting more difficult (probably not completely impossible, but certainly
more difficult).

I expect we can discuss this further and make another decision next week.

Cheers,
-- 
...........................Malcolm Cohen, NAG Ltd., Oxford, U.K.
                           (malcolm@nag.co.uk)


