#14 incorrect handling of INVERSE?

[Tom Thurman]

The INVERSE declaration doesn't include the ability to
identify a source TYPE if there is a SELECT type
between the entity type with the forward attribute
declaration and the entity type with the target of the
SELECT type. The included snippet is accepted by
Express-engine and should not be accepted:

SCHEMA test;
ENTITY part_feature;
associated_definition : string;
INVERSE
feature_shape :
SET[0:?] OF usage_concept_usage_relationship FOR
associated_usage;
END_ENTITY; -- part_feature

TYPE usage_concept = SELECT
(part_feature);
END_TYPE; -- usage_concept
ENTITY usage_concept_usage_relationship;
associated_usage : usage_concept;
name : string;
END_ENTITY; -- usage_concept_usage_relationship
END_SCHEMA;

[Thomas Thurman]

Logged In: YES
user_id=353340

according to the express committee the existing behavior is
correct. The bug should be closed.