<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<title>WG10 four week review N317</title>
<base>
</head>
<body>
<h2><a name="top12345"></a>WG10 four week review N317</h2>
<p><b> Ballot owner </b>David Price</p>
<p><b> Email </b><a href="mailto:dmprice@us.ibm.com">dmprice@us.ibm.com</a></p>
<p><a href="#issues" target="_self">Issues in Number order</a>
, <a href="#docorder" target="_self">Issues in Document/Clause order</a>
, <a href="#sum" target="_self">Summary of Issues</a>
, <a href="#details" target="_self">Ballot control information</a>
<a name="issues"></a>
<h2>Issues</h2>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_1"></a>CEV_1</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> 5.2.1 Information requirements documentation <br>1. units of functionality <br>duplicate word (which) in text:-<br>the name of the AM in which which the UoF </td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_2"></a>CEV_2</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 4 Application module content overview</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> Section 5 has the statement<br>This subclause provides a complete list of the UoFs defined in the AM and defined in any other AM used directly or indirectly by the AM. <br>This is an important statement and should be included in the overview section 4<br>I don't think the indirect AMs should be listed - See next issue </td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_3"></a>CEV_3</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Major Technical</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> Secetion 5.2.1 Information requirements documentation states<br>This subclause provides a complete list of the UoFs defined in the AM and defined in any other AM used directly or indirectly by the AM.<br>I firmly believe that an AM should only reference the UoFs that it addresses directly.<br>1. the higher level the module the longer this list of indirect AMs/UoFs will get.<br>2. the indirect list can be generated automatically from the USE FROM statements<br>3. the HTML modules repository does this already<br>4. this is another list that needs to be checked and is only informative as the USE FROM statements are the definitive information<br>5. Module developers have not consistently followed this rule, some modules have the full list and some don't<br></td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> Remove the requirement for the indirect AMs/UoFs</td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_4"></a>CEV_4</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> Last line of section "5.3.4.1 Global rules as supertype constraints and using subtype constraints" - "the that purpose" should be "that purpose"<br>In the cases where any constraint may be written using an EXPRESS subtype constraint instead of a global rule, a subtype constraint may be specified for the that purpose. </td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_5"></a>CEV_5</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> 5.3 The module interpreted model - repeated word (the)<br>The MIM documents the interpretation of the the information requirements into the common resources</td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_6"></a>CEV_6</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> 5.3.3 Concept completion and assignment <br>What does the word <br>prepended <br>mean. Not in my dictionary</td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<a name="docorder"></a>
<h2>Issues in Document/Clause Order</h2>
<h3>Document : Guidelines for the content of application modules Revision 0.7</h3>
<h4>Clause : 4 Application module content overview</h4>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_2"></a>CEV_2</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 4 Application module content overview</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> Section 5 has the statement<br>This subclause provides a complete list of the UoFs defined in the AM and defined in any other AM used directly or indirectly by the AM. <br>This is an important statement and should be included in the overview section 4<br>I don't think the indirect AMs should be listed - See next issue </td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<h4>Clause : 5 Specification of application module content</h4>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_1"></a>CEV_1</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> 5.2.1 Information requirements documentation <br>1. units of functionality <br>duplicate word (which) in text:-<br>the name of the AM in which which the UoF </td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_4"></a>CEV_4</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> Last line of section "5.3.4.1 Global rules as supertype constraints and using subtype constraints" - "the that purpose" should be "that purpose"<br>In the cases where any constraint may be written using an EXPRESS subtype constraint instead of a global rule, a subtype constraint may be specified for the that purpose. </td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_5"></a>CEV_5</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> 5.3 The module interpreted model - repeated word (the)<br>The MIM documents the interpretation of the the information requirements into the common resources</td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_6"></a>CEV_6</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Editorial</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> 5.3.3 Concept completion and assignment <br>What does the word <br>prepended <br>mean. Not in my dictionary</td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> </td></tr>
</table>
<hr>
<table border= "0">
<tr><td valign="top"><b>Issue number : </b></td><td><a name="CEV_3"></a>CEV_3</td></tr>
<tr><td valign="top"><b>Originator : </b></td><td> Chris Vaughan</td></tr>
<tr><td valign="top"><b>E Mail address : </b></td><td> <a href="mailto:chris_vaughan@bigfoot.com">chris_vaughan@bigfoot.com</a></td></tr>
<tr><td valign="top"><b>Document : </b></td><td> Guidelines for the content of application modules Revision 0.7</td></tr>
<tr><td valign="top"><b>Clause : </b></td><td> 5 Specification of application module content</td></tr>
<tr><td valign="top"><b>Category : </b></td><td> Major Technical</td></tr>
<tr><td valign="top"><b>Issue Date :</b></td><td> 9 Nov 2000</td></tr>
<tr><td valign="top"><b>Issue : </b></td><td> Secetion 5.2.1 Information requirements documentation states<br>This subclause provides a complete list of the UoFs defined in the AM and defined in any other AM used directly or indirectly by the AM.<br>I firmly believe that an AM should only reference the UoFs that it addresses directly.<br>1. the higher level the module the longer this list of indirect AMs/UoFs will get.<br>2. the indirect list can be generated automatically from the USE FROM statements<br>3. the HTML modules repository does this already<br>4. this is another list that needs to be checked and is only informative as the USE FROM statements are the definitive information<br>5. Module developers have not consistently followed this rule, some modules have the full list and some don't<br></td></tr>
<tr><td valign="top"><b>Proposed Solution/Remarks :</b></td><td> Remove the requirement for the indirect AMs/UoFs</td></tr>
</table>
<hr>
<a name="sum"></a>
<h2>Summaries of Issues</h2>
<h3>By Document/Category</h3>
<table border= 1; width= 95%>
<tr>
<td>Document</td>
<td>Category</td>
<td>Number</td>
<td>Issues</td>
</tr>
<tr>
<td>Guidelines for the content of application modules Revision 0.7</td>
<td>Editorial</td>
<td> 5</td>
<td><a href="#CEV_1" target="_self">CEV_1</a>, <a href="#CEV_2" target="_self">CEV_2</a>, <a href="#CEV_4" target="_self">CEV_4</a>, <a href="#CEV_5" target="_self">CEV_5</a>, <a href="#CEV_6" target="_self">CEV_6</a></td>
</tr>
<tr>
<td>Guidelines for the content of application modules Revision 0.7</td>
<td>Major Technical</td>
<td> 1</td>
<td><a href="#CEV_3" target="_self">CEV_3</a></td>
</tr>
</table><hr>
<h3>By Category</h3>
<table border= 1; width= 95%>
<tr>
<td>Category</td>
<td>Number</td>
<td>Issues</td>
</tr>
<tr>
<td>Editorial</td>
<td> 5</td>
<td><a href="#CEV_1" target="_self">CEV_1</a>, <a href="#CEV_2" target="_self">CEV_2</a>, <a href="#CEV_4" target="_self">CEV_4</a>, <a href="#CEV_5" target="_self">CEV_5</a>, <a href="#CEV_6" target="_self">CEV_6</a></td>
</tr>
<tr>
<td>Major Technical</td>
<td> 1</td>
<td><a href="#CEV_3" target="_self">CEV_3</a></td>
</tr>
</table><hr>
<h3>By Document/Resolution Status</h3>
<table border= 1; width= 95%>
<tr>
<td>Document</td>
<td>Resolution Status</td>
<td>Number</td>
<td>Issues</td>
</tr>
<tr>
<td>Guidelines for the content of application modules Revision 0.7</td>
<td> </td>
<td> 6</td>
<td><a href="#CEV_1" target="_self">CEV_1</a>, <a href="#CEV_2" target="_self">CEV_2</a>, <a href="#CEV_3" target="_self">CEV_3</a>, <a href="#CEV_4" target="_self">CEV_4</a>, <a href="#CEV_5" target="_self">CEV_5</a>, <a href="#CEV_6" target="_self">CEV_6</a></td>
</tr>
</table><hr>
<h3>By Resolution Status</h3>
<table border= 1; width= 95%>
<tr>
<td>Resolution Status</td>
<td>Number</td>
<td>Issues</td>
</tr>
<tr>
<td> </td>
<td> 6</td>
<td><a href="#CEV_1" target="_self">CEV_1</a>, <a href="#CEV_2" target="_self">CEV_2</a>, <a href="#CEV_3" target="_self">CEV_3</a>, <a href="#CEV_4" target="_self">CEV_4</a>, <a href="#CEV_5" target="_self">CEV_5</a>, <a href="#CEV_6" target="_self">CEV_6</a></td>
</tr>
</table><hr>
<a name="details"></a>
<h2>Documents being reviewed</h2>
<ul>
<li>Guidelines for the content of application modules Revision 0.7</li>
</ul><hr>
<h2>Categories of Issue</h2>
<ul>
<li>Editorial</li>
<li>Minor Technical</li>
<li>Major Technical</li>
</ul><hr>
<h2>Clauses within Documents</h2>
<ul>
<li>1 Scope</li>
<li>2 Normative references</li>
<li>3 Terms, definitions and abbreviations</li>
<li>4 Application module content overview</li>
<li>5 Specification of application module content</li>
<li>Annex A Conformance testing concepts for application modules</li>
<li>Annex B Examples</li>
</ul><hr>
<small><strong>
<p>Program ManageBallotIssues</p>
<p>Version 1.3.14</p>
<p>Warning: This program is provided without warranty. To obtain the latest version contact chris_vaughan@bigfoot.com, API Systems Ltd.</p>
</small></strong>
<p><a href="#top12345" target="_self"><strong>go to top of page</a></strong></p>
<hr>
<p><small><strong>DateStamp 9 Nov 2000 12:1:15</strong></small></p>
</body>
</html>