<HTML>
<HEAD>
<!-- Created with AOLpress/2.0 -->
<TITLE>Charleston ISO/SC4 10303-25 Project Meeting Notes</TITLE>
</HEAD>
<BODY>
<H2 ALIGN=Center>
Charleston ISO/SC4 10303-25 Project Meeting Notes
</H2>
<P ALIGN=Center>
<BR>
<B><BIG>2000-10-18<BR>
David Price</BIG></B>
<P>
The project conducted a technical review of WG11 N143 the Part 25 Working
Draft 1 document mappings. The presentation of the mapping is an attachment
to these notes. During the technical review several issues were raised and
resolved. Those issues are described below. The project determined that the
next steps are to complete the update the document based on these issues
and to produce Working Draft 2 which will then be submitted to ballot to
become a Technical Specification.
<P>
Editor's Note - Unfortunately, the complete attendees list was lost. A subset
of those present included the following (apologies to any experts I omitted):
<P>
David Price<BR>
Don Sanderson<BR>
Phil Spiby<BR>
Ed Barkmeyer<BR>
Markus Maier<BR>
Heike Halkenhaeusser<BR>
Joe Trausch<BR>
Bill Burkett<BR>
Robin Lafontaine<BR>
Masaru Suzuki
<P>
1 - Change WD2 so that all the EXPRESS types in an interfaced schema may
be but are not required to be, included in the UML model regardless of their
visibility in the context schema. This results in a change to
<A HREF="clause5.html#clause5.4">clause 5.4 in WD2</A>.
<P>
2 - Change WD2 so that for an EXPRESS aggregation whether duplicates are
allowed and whether the ordering is significant is specified in the UML
representation.
<P>
3 - Change WD2 so that for the case of an EXPRESS single dimensional aggregation
that is not an array and the type of the aggregation is a named type, a UML
Association is created between the UML representation of the EXPRESS entity
with the aggregate as an attribute domain and the UML representation of the
EXPRESS named type. The names should be as the same as now. The UML attributes
of the UML association should address ordering, duplicates and cardinality.
The cardinality on inverse end of the UML Association has to be *.
<P>
4 -Change WD2 so that for an EXPRESS single dimensional array of named types,
a UML associationClass is created.
<P>
5 - Make EXPRESS ONEOF an explicit UML disjoint constraint between subclasses
of a common UML Class representing an EXPRESS entity that is a supertype
when specified in the EXPRESS supertype constraint.
<P>
6- Use the UML OR constraint, rather than UML XOR, in the mapping of EXPRESS
SELECT types.
<P>
7- Change the UML Class representing an EXPRESS defined type to be a subclass
of the UML Class that represents its underlying type.
<P>
8 - Make the "reverse-of" UML Association created in the mapping an EXPRESS
entity-valued attribute optional in the UML.
<P>
9 - For each EXPRESS derived attribute, create a UML method. This is an addition
to WD2 as derived attributes were out-of-scope in WD1.
</BODY></HTML>