<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">CSTSWG colleagues --<o:p></o:p></p>
<p class="MsoNormal">At the FF-CSTS Splinter meeting at the Spring 2007 CSTSWG (San Antonio) meeting, Tim Pham accepted the action item “TP will analyse the events reported via the Notify operation in the F-CLTU specification, in order to determine if/which
of those should be carried forward in FF-CSTS.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In response to that action item, Tim and I have reviewed the F-CLTU NOTIFY and have mapped the F-CLTU NOTIFY events and parameters against the Buffered and Sequence-Controlled Data Processing procedures. The results are in the attached
spreadsheet. There are 3 columns: CLTU NOTIFY, Buffered Data Processing, and Sequence-Controlled Data Processing. For each F-CLTU notification, the equivalent notification for the two DP procedures is called out, as well as which “flavor” of the NOTIFY those
notifications appear in (core NOTIFY, Data Processing NOTIFY, Buffered Data Processing NOTIFY, or S-C Data Processing NOTIFY).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In most cases, the CLTU NOTIFY events are echoed in the respective Data Processing procedures’ NOTIFY operations. In a few cases, an F-CLTU notification does not have an equivalent in either DP-derived procedure, but they could be provided
via the separate Notification or Throw Event procedure.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The color coding and notes are documented on the NOTIFY Notes tab.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>