[wg11] P11e2: FDIS -> IS
Jochen Haenisch
Jochen.Haenisch at epmtech.jotne.com
Wed May 19 13:10:09 EDT 2004
Hei Phil,
attached are recently forwarded SEDS. 866, 910, 911 may be resolved for the
IS-version; 915 maybe not. You will have an opinion on that :-)
In addition the items below.
----------------------------------------------------------------------------
-------------------
The type labels issue that you just sent an email about.
----------------------------------------------------------------------------
-------------------
On page 226:
Could you verify that WR2 for domain2_approval should be removed?
----------------------------------------------------------------------------
-------------------
Also: These examples without entities: according to the pruning of
non-referenced defined types, the 1994-schemas would indeed be empty. There
should be a disclaimer accordingly, or three dots after SCHEMA and before
END_SCHEMA.
======================================================
Günther had the following (I have only scanned them ...):
Chapter G.3.2, page 206, Example 1:
The single quotes used there are typographical quotes not ASCII(27) !
Therefore a cut and paste of examples leads to errors.
Note that this kind of wrong quoting character is used in other places as
well.
----------------------------------------------------------------------------
-------------------
On page 224:
Example 1: The enumeration "gender" uses the reserved word "unknown" !
----------------------------------------------------------------------------
-------------------
Chapter G.5.5, page 230, Example 1 and paragraph above example:
Example does not compile, because reference to "binary_entity_relationship"
in SUBTYPE OF instead of
"binary_relationship". Paragraph above refers also to the wrong entity_name.
Furthermore not clear how to handle a case of
...
end_one : SET OF GENERIC_ENTITY
...
or
...
end_one : AGGREGATE OF GENERIC_ENTITY
...
What would be the rules in these cases?
----------------------------------------------------------------------------
-------------------
Chapter G, especially ordering of G.5.5 and G.5.3.2 :
There can be cases constructed where the normal ordering of steps leads to
wrong results.
-------------------------------------------------------------------------
SCHEMA import; -- Example Test_G55_Ex_2.txt
ENTITY action_assignment ABSTRACT;
set_of_items : SET [1 : ?] OF action_items;
items : action_items;
END_ENTITY;
TYPE configuration_effectivity = NUMBER;
END_TYPE;
TYPE action_item_203e2 = SELECT BASED_ON action_items WITH
(configuration_effectivity);
END_TYPE;
TYPE action_items = EXTENSIBLE GENERIC_ENTITY SELECT ;
END_TYPE;
TYPE action_items_2 = EXTENSIBLE GENERIC_ENTITY SELECT
(action_assignment);
END_TYPE;
ENTITY applied_action_assignment
SUBTYPE OF (action_assignment);
SELF\action_assignment.set_of_items : SET [1 : 5] OF action_items;
SELF\action_assignment.items : configuration_effectivity;
END_ENTITY;
END_SCHEMA;
-------------------------------------------------------------------------
Doing G.5.3.2 first converts extensible Selects into standard selects. By
this
step G.5.5 cannot be applied since the "GENERIC_ENTITY" is no longer there.
----------------------------------------------------------------------------
-------------------
Chapter G.4.4 :
It is not explicitly written, that the pruning step has to be iterative
until no more changes occur. Since pruning of rules could lead to things in
the artifact schema which should not be there. Example below:
-------------------------------------------------------------------------
SCHEMA s1;
ENTITY e1;
END_ENTITY;
ENTITY thing;
END_ENTITY;
ENTITY function_thing_local;
END_ENTITY;
ENTITY function_thing_inp;
END_ENTITY;
ENTITY e2 SUBTYPE OF (e1);
END_ENTITY;
ENTITY e3 SUBTYPE OF (e1);
END_ENTITY;
SUBTYPE_CONSTRAINT sc_total_over FOR e1;
TOTAL_OVER (e2, e3);
END_SUBTYPE_CONSTRAINT;
RULE e2_and_e3 FOR (e2, e3);
-- rule body
WHERE
wr1 : f2(TRUE);
END_RULE;
FUNCTION f1(inp : function_thing_inp) : BOOLEAN;
LOCAL
a : function_thing_local;
END_LOCAL;
RETURN(TRUE);
END_FUNCTION;
FUNCTION f2(inp : BOOLEAN) : BOOLEAN;
LOCAL
a : function_thing_local;
END_LOCAL;
RETURN(TRUE);
END_FUNCTION;
END_SCHEMA; -- end s1
SCHEMA import;
REFERENCE FROM s1 (function_thing_inp);
REFERENCE FROM s1 (e2);
END_SCHEMA; -- end import
------------------------------------------------------------------------
Without iteration this would lead to inclusion of "f2" and
"function_thing_local" which are per se not part of the longform.
To get rid of "function_thing_local" a pruning of entities which are not
referenced and not brought into the schema through USE_FROM or
REFERENCE_FROM has to take place.
======================================================
Ed, Tom Kramer and Peter Denno had the following one:
In Part 11.2:2003, clause 9.2.5.2, after the normative text, the following
NOTE
is to be found:
"NOTE The phrase ONEOF(a,b,c) reads in natural language as 'an instance
shall
consist of one and only one of the entity data types a,b,c.'"
The NOTE does not correctly convey the intent of the normative text.
Proposed change:
Either: The words "one and only one" should be replaced by "at most one"
or: the words "shall consist of one and only one" should be replaced by
"shall not consist of more than one". (I prefer the latter.)
======================================================
Darla has this one:
Part11e2FDIS says in 9.5.3.2
If a generic data type is used as the result type of a function, or as the
type of a local variable within a function or procedure, type labels [sic]
references are required for this usage.
should be written like this:
If a generic data type is used as the result type of a function, or as the
type of a local variable within a function or procedure, type label
references are required for this usage.
======================================================
Regards,
Jochen
<<SEDS-866-STEP-Part11ed2FDIS.txt>>
<<SEDS-911-10303-11-FDIS-ed2-RootPrimarySchemaDefs.txt>>
<<SEDS-910-STEP-11ed2-attribute-renaming.txt>>
<<SEDS-915-10303-11-FDIS-ed2-Use-from-all.txt>>
____________________________________________________________
Jochen Haenisch E-mail: Jochen.Haenisch at epmtech.jotne.com
EPM Technology AS Home of the EXPRESS Data Manager
P.O Box 6629 Etterstad Tel: Int + 47 23 17 17 26; mobile: Int + 47
922 60 274
N-0607 Oslo Fax: Int + 47 23 17 17 01
Norway Web: http://www.epmtech.jotne.com
-------------- next part --------------
From: Allison Barnard Feeney [abf at cme.nist.gov]
Sent: Thursday, August 21, 2003 11:09 AM
To: SC4seds
Cc: expressIF
Subject: SEDS on part 11 FDIS
Categories: Action Items - To Do
Section 1. GENERAL INFORMATION (completed by SC4 Secretariat/WG Convener):
SEDS Report Number: 866
Date Submitted: 2003-08-21
Status: Open
Assigned WG:
SEDS Team Leader:
SEDS Team Members:
Section 2. ENHANCEMENT AND DISCREPANCY INFORMATION (completed by Author
of SEDS Report):
Author: Allison Barnard Feeney
Email Address: abf at nist.gov
Part and Clause where Issue Originates: 10303-11e2 FDIS, G.4.4 example
5 Other Parts Affected by the Issue: none Related Issues:
Summary/Abstract/Keywords: typo in express example
Problem Description: The keyword TYPE is missing from the type
declaration in example 5 of
schema s3.
Conditions Under Which the Issue Was Discovered: Preparation for
validation of express e2 tools.
Proposed Solution (Optional): Add the keyword TYPE before t31 in type
declaration in schema s3.
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:
--
Allison Barnard Feeney
NIST
100 Bureau Drive, Stop 8260
Gaithersburg, MD 20899-8260
USA
301-975-3181 - phone
301-975-4694 - fax
abf at nist.gov - email
-------------- next part --------------
Section 1. GENERAL INFORMATION (completed by SC4 Secretariat/WG Convener):
SEDS Report Number: 911
Date Submitted: 2004-01-13
Status: Open 2004-01-13
Assigned WG: 11
SEDS Team Leader:
SEDS Team Members:
Section 2. ENHANCEMENT AND DISCREPANCY INFORMATION (completed by Author of SEDS Report):
Author: Jochen Haenisch (jochen.haenisch at epmtech.jotne.com); Allison Barnard Feeney (abf at nist.gov)
Part/Clause Affected by the Issue: ISO/FDIS 10303-11e2 G.2, G.4
Other Parts Affected by the Issue: none
Problem Description: The terms root schema and primary schema are introduced in annex G but are not defined.
Conditions Under Which the Issue Was Discovered:
Proposed Solution (Optional):
Add definitions for root schema and primary schema in clause 3.3
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:
-------------- next part --------------
Section 1. GENERAL INFORMATION (completed by SEDS Coordinator):
SEDS Report Issue Number: 910
Date Submitted: 2004/01/12
Status and date: Open 2004-01-12
SEDS Team Leader:
SEDS Team Members:
Section 2. ENHANCEMENT AND DISCREPANCY INFORMATION (completed by author of SEDS Report):
Author: Jochen Haenisch (jochen.haenisch at epmtech.jotne.com); Allison Barnard Feeney (abf at nist.gov)
Submitted by:
Part/Clause Affected by the Issue: ISO/FDIS 10303-11e2 G.5.6, 4th bullet
Other Parts Affected by the Issue:
Problem Description:
An e2 redeclaration of an attribute (see entity E4 in E2003_Schema) that is renamed in a supertype
(see E3 in E2003_Schema) (and, thus, in e1 results in a DERIVED attribute in E3 in E1994_Schema)
shall in e1 result in a redeclaration with reference to the original attribute definition, not any
intermediate one (see E4 in E1994_Schema).
(* E2 schema *)
SCHEMA E2003_SCHEMA;
ENTITY T1;
END_ENTITY;
ENTITY T2
SUBTYPE OF (T1);
END_ENTITY;
ENTITY T3
SUBTYPE OF (T2);
END_ENTITY;
ENTITY E1;
e1a1 : T1;
e1a2 : T1;
END_ENTITY;
ENTITY E2
SUBTYPE OF (E1);
END_ENTITY;
ENTITY E3
SUBTYPE OF (E2);
SELF\E1.e1a1 RENAMED e1a1_r : T2;
SELF\E1.e1a2 RENAMED e1a2_r : T2;
END_ENTITY;
ENTITY E4
SUBTYPE OF (E3);
SELF\E3.e1a1_r : T3;
SELF\E3.e1a2_r : T3;
END_ENTITY;
END_SCHEMA;
(* E1 schema *)
SCHEMA E1994_SCHEMA;
ENTITY T1;
END_ENTITY;
ENTITY T2
SUBTYPE OF (T1);
END_ENTITY;
ENTITY T3
SUBTYPE OF (T2);
END_ENTITY;
ENTITY E1;
e1a1 : T1;
e1a2 : T1;
END_ENTITY;
ENTITY E2
SUBTYPE OF (E1);
END_ENTITY;
ENTITY E3
SUBTYPE OF (E2);
SELF\E1.e1a1 : T2;
SELF\E1.e1a2 : T2;
DERIVE
e1a2_r : T2 := SELF\E1.e1a2;
e1a1_r : T2 := SELF\E1.e1a1;
END_ENTITY;
ENTITY E4
SUBTYPE OF (E3);
SELF\E1.e1a1 : T3;
SELF\E1.e1a2 : T3;
END_ENTITY;
END_SCHEMA;
Conditions under which the issue was discovered: EXPRESS e2 to EXPRESS e1 short to longform benchmarking
Proposed Solution (Optional):
change text from
- the derivations of the attribute values shall be
SELF\<supertype name>.<old attribute name>
To
- the derivations of the attribute values shall be
SELF\<supertype where attribute is defined>.<original attribute name>
Section 3. RESPONSE INFORMATION (completed by SEDS Team Leader):
Accepted/Rejected (date):
If Accepted, Resolution:
If Rejected, Reason:
Solution:
Comments:
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:
-------------- next part --------------
Section 1. GENERAL INFORMATION (completed by SC4 Secretariat/WG Convener):
SEDS Report Number: 915
Date Submitted: 2004-03-02
Status: Open 2004-03-09
Assigned WG: 11
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:
More information about the wg11
mailing list