Next ISO TC184/SC4 meeting, 9-14 March 2003 - EXPRESS 2.0

[Phil Spiby]

Howard,

Thank you for raising this issue to a wider audience and supporting our work
at getting EXPRESS 2 out for FDIS ballot. 

The required technical consensus was reached at the Stockholm meeting last
summer.  It is therefore important a revised document is made available at
the earliest possible opportunity which reflects the technical consensus. 
Jochen Haenish and Kjell Bengston have both assured me that the document
will be available at the San Diego meeting (but probably not before).

This revised document will need WG11 review to ensure the technical
consensus has been correctly captured. A small WG11 meeting may be required
after the San Diego meeting to resolve any issues arising from the review.

Member bodies should ensure WG11 resources are available to review the
document and support the quick resolution of any issues which may arise. 

Phil


> -----Original Message-----
> From: owner-wg11 at steptools.com 
> [mailto:owner-wg11 at steptools.com] On Behalf Of Howard Mason
> Sent: 17 February 2003 17:10
> To: wg11 at steptools.com; SC4Pmembers at tc184-sc4.org; 
> sc4ppc at tc184-sc4.org
> Subject: Next ISO TC184/SC4 meeting, 9-14 March 2003 - EXPRESS 2.0
> 
> 
> 
> With the forthcoming completion of a number of STEP 
> application protocols based on 
> the modular approach, it has become urgent for SC4 to 
> complete and issue the new 
> version 2.0 of the EXPRESS language (ISO 10303-11), which 
> provides a number of key 
> capabilities to support the exploitation of modules.
> 
> I encourage all member bodies to ensure that they have 
> adequate representation at 
> the forthcoming meeting in San Diego to ensure that consensus 
> can be reached on the 
> remaining issues, and that the document can proceed to FDIS 
> ballot immediately 
> after the meeting.
> 
> The alternative would be a severe disruption to the SC4 
> delivery plans in 2003.
> 
> Thank you for your support.
> 
> Howard Mason
> Chairman, ISO TC184/SC4
> 
> ********************************************************************
> This email and any attachments are confidential to the 
> intended recipient and may also be privileged. If you are not 
> the intended recipient please delete it from your system and 
> notify the sender. You should not copy it or use it for any 
> purpose nor disclose or distribute its contents to any other person.
> ********************************************************************
>