<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN
class=769214419-09092004>All,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=769214419-09092004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004>This is a call for
anyone interested in helping specify the first draft of the Part 25 Edition 2
standard clause on how to use UML 1.5 to represent EXPRESS 2. This might be
called "A UML Profile for EXPRESS". The result will be roughly the
equivalent of EXPRESS-G diagrams, only done using UML.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004></SPAN></FONT><FONT
face=Arial size=2><SPAN class=769214419-09092004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004>A UML Profile for
EXPRESS might have the following characteristics:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=769214419-09092004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004>- each UML Class
representing an EXPRESS entity type would be stereotyped or tagged in some
manner</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004>- each UML Class or
other concept representing EXPRESS defined types would be stereotyped or tagged
in some manner</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004><SPAN
class=769214419-09092004>- allow the mixture of UML Classes and other UML
notations that do not represent EXPRESS along with those that do on the same UML
diagrams, in the same UML package and UML model</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=769214419-09092004> </SPAN></FONT></DIV>
<DIV><FONT face=Arial><FONT size=2>Note that this is not a call for a MOF model
of EXPRESS, that<SPAN class=769214419-09092004> will </SPAN>be a separate
item<SPAN class=769214419-09092004> planned for Part 25 Edition 3 and will be
based on UML 2. However, if anyone has already done work in this area, please
feel free to share it with the group. We'll make time on the Seattle agenda for
a short presentation if you want.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2>Expanding the Part 25 Edition 2 generic
EXPRESS to UML <SPAN class=769214419-09092004>1.5 </SPAN>mapping to support
EXPRESS 2 is also a separate item.<SPAN class=769214419-09092004> This will be
included in Part 25 Editoin 2.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=769214419-09092004>The plan is to walk
through the first draft of Part 25 Edition 2 at the Seattle STEP
meeting.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=769214419-09092004>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=769214419-09092004>David</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2>Phone +44 207 704 0499</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Mobile +44 7788 561308</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>8 Highbury Place, Flat 5</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>London, UK</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>N5 1QZ</FONT></DIV>
<DIV> </DIV></BODY></HTML>