SEDS on EXPRESS: USE FROM on

[Bernd G. Wenzel]

Hi Lothar,

would you please elaborate a bit more what it is that "schema developers
like to do"? I don't happen to see the semantic difference.

Thanks.

:-) Bernd
----------------------------------
Dipl.-Inform. Bernd G. Wenzel
Management & IT Consultant
Ganghofer-Str. 7b
DE-83043 Bad Aibling
Germany

Office Phone: ++49-(0)8061-936360
Mobile Phone: ++49-(0)170-9983565
Facsimile:    ++49-(0)8061-92018
E-Mail:       bg_wenzel at csi.com
Home Phone:   ++49-(0)8061-37232


----- Original Message ----- 
From: "Lothar Klein" <lothar.klein at lksoft.com>
To: <seds at tc184-sc4.org>
Cc: "Rob Bodington" <rob.bodington at eurostep.com>; "'SC4 WG11'"
<wg11 at steptools.com>; "pfAeroFW, ISOWG12" <ISOWG12 at IMC7.EMS.LMCO.COM>
Sent: Tuesday, March 02, 2004 3:34 PM
Subject: SEDS on EXPRESS: USE FROM on


>
> Hi,
> during the todays SC4 "WG3/WG12 Modules Coordination" meeting in Ft.
> Lauderdale the requirements as written down in SEDS below got briefly
> discussed.
>
> Lothar
>
> -- 
> // Lothar Klein, LKSoftWare GmbH
> // Steinweg 1, 36093 Kuenzell, Germany
> // +49 661 933933-0, Fax: -2
> // url: http://www.lksoft.com
>
>
> Section 1.  GENERAL INFORMATION (completed by SC4 Secretariat/WG
Convener):
>
> SEDS Report Number:
> Date Submitted:
> Status:
> Assigned WG:
> SEDS Team Leader:
> SEDS Team Members:
>
>
> Section 2.  ENHANCEMENT AND DISCREPANCY INFORMATION (completed by Author
of SEDS Report):
>
> Author: Lothar Klein
> Email Address: lothar.klein at lksoft.com
> Part and Clause where Issue Originates: ISO 10303-11, clause 11.1
> Other Parts Affected by the Issue:
> Related Issues:
> Summary/Abstract/Keywords: USE FROM *all* on non-data-type items
> Problem Description:
> With a USE FROM *all* only all the data types get interfaced, but not
> functions, procedures and constants. To get them in as well an
> additional REFERENCE FROM *all* would be needed. Since USE FROM on a
> data type takes precedence over a REFERENCE FROM this is not what
> schema developer like to do.
>
> Conditions Under Which the Issue Was Discovered:
> Module development
>
> Proposed Solution (Optional):
> After this sentence
> "If there are no named_types specified, all of the named data types
>  declared within or use’d by the foreign schema are treated as if
>  declared locally."
> add
>
> "In addition all of the following EXPRESS items declared within or
> referenced by the foreign schema are made visible in the current
> schema:
>  - Constant;
>  - Function;
>  - Procedure."
>
>
>
> Section 3.  RESPONSE INFORMATION (completed by SEDS Resolution Team
Leader):
>
>
> If Accepted, Resolution:
>
>
> Section 4.  FOLLOW-UP INFORMATION (completed by WG Convener):
>
> Class:
> Priority:
> Impact of Change:
> Further Action Required:
> Action Required by SEDS Coordinator/WG Conveners/QC/SC4:
>