<br><font size=2 face="sans-serif">The Part 28 DIS ballot resolution meeting
will take place on March 15. Attached please find the technical comments
that will be addressed at that meeting. If you will not be attending
the meeting please be sure to review these comments, and let me know PRIOR
to the meeting if there are any issues with them:<br>
<br>
<br>
</font>
<table border>
<tr valign=top>
<td><font size=1 face="Arial">JP-1</font><font size=1 face="Tahoma"> </font>
<div align=center>
<p><font size=1 face="Arial">(FT)</font></div>
<td><font size=2 face="Arial">10303-28</font>
<td><font size=2 face="Arial">7.2.1.6</font><font size=1 face="Tahoma">
</font>
<p><font size=2 face="Arial">8.2.1.6</font>
<td><font size=2 face="Arial">Exception</font>
<td><font size=2 face="Arial">te</font>
<td><font size=2 face="Arial">EXPRESS REAL data type with precision need
to be mapped. </font>
<td><font size=2 face="Arial">EXPRESS REAL data type with precision need
to be mapped to xs:double without restriction of the precision.</font>
<tr valign=top>
<td><font size=1 face="Arial">JP-2</font><font size=1 face="Tahoma"> </font>
<div align=center>
<p><font size=1 face="Arial">(FT)</font></div>
<td><font size=2 face="Arial">10303-28</font>
<td><font size=2 face="Arial">10.2.13.1</font>
<td><font size=2 face="Arial">First and second item</font>
<td><font size=2 face="Arial">te</font>
<td><font size=2 face="Arial">xs:IDREF and xs:IDREFS are not suitable for
the values of the map directive</font>
<td><font size=2 face="Arial">These items should be deleted.</font></table>
<br><font size=2 face="sans-serif"><br>
</font>
<table border>
<tr valign=top>
<td><font size=2 face="Arial">US-3</font>
<td><font size=2 face="Arial">7.4.3/ 8.4.3</font>
<td><font size=2 face="Arial">Para 1, NOTE 1</font>
<td><font size=2 face="Arial">tech</font>
<td><font size=2 face="Arial">When the defined data type is a rename of
a SELECT, it should be treated the same as a defined data type whose underlying
type is a SELECT, that is, a group should be created instead of an instance
element.</font>
<td><font size=2 face="Arial">Modify the wording to include renames of
SELECTS.</font>
<td><font size=2 face="Arial"> </font></table>
<br>
<table border>
<tr valign=top>
<td><font size=2 face="Arial">US-6</font>
<td><font size=2 face="Arial">Annex C, 7.5.3.3, 8.5.3.5</font>
<td><font size=2 face="Arial"> </font>
<td><font size=2 face="Arial">tech</font>
<td><font size=2 face="Arial">exp:complexEntity requires the nillable attribute.
The 'entities' attribute should be optional.</font>
<td><font size=2 face="Arial">Make exp:complexEntity nillable.</font></table>
<br>
<table border>
<tr valign=top>
<td><font size=2 face="Arial">US-8</font>
<td><font size=2 face="Arial">Annex C, 7.5.3.3, 8.5.3.5</font>
<td><font size=2 face="Arial"> </font>
<td><font size=2 face="Arial">tech</font>
<td><font size=2 face="Arial">The current xs:sequence in complexEntity
is problematic. It is unclear how the current configuration does
anything meaningful.</font>
<td><font size=2 face="Arial">Change the contents of the xs:sequence in
exp:complexEntity to be: </font>
<br><font size=2 face="Arial"><xs:any namespace=”##any” processContents=”skip”
maxOccurs=”unbounded”/></font>
<tr valign=top>
<td><font size=2 face="Arial">US-9</font>
<td><font size=2 face="Arial">7.3.4.2/ 8.3.4.2</font>
<td><font size=2 face="Arial"> </font>
<td><font size=2 face="Arial">tech</font>
<td><font size=2 face="Arial">The current construct for the SELECT groups
creates a reference to each subtypes group for entities in the working
select list. This creates a potential for ambiguity when two items
in the select group have a common item in their subtype groups. When
something shows up in the working select list that is a subtype of another
item in the list, or when two items show up which are both supertypes of
the same item, there is ambiguity. Also, abstract elements should
not be included in this list.</font>
<td><font size=2 face="Arial">Resolve Su</font>
<tr valign=top>
<td><font size=2 face="Arial">US-10</font>
<td><font size=2 face="Arial">7.3.4/ 8.3.4, 7.2.2/ 8.2.2</font>
<td><font size=2 face="Arial"> </font>
<td><font size=2 face="Arial">tech</font>
<td><font size=2 face="Arial">For a SELECT type that has any collection(s)
in its list of choices, the complexType for that SELECT must include an
optional ex:arraySize ref :</font><font size=1 face="Tahoma"> </font>
<p><font size=2 face="Arial"><xs:element ref==”ex:arraySize” use=”optional”/></font>
<p><font size=2 face="Arial">Also, for an attribute whose underlying type
is a SELECT type with one item that has a collection, we need to provide
optional ex:arraySize attribute on the accessor element. I.E.</font>
<p><font size=2 face="Arial">TYPE symmetric_tensor4_2d = SELECT (anisotropic_
symmetric_tensor4_2d); END_TYPE;</font>
<p><font size=2 face="Arial">TYPE anisotropic_symmetric_tensor4_2d = ARRAY
[1:6] OF context_dependent_measure;END_TYPE;</font>
<p><font size=2 face="Arial">Fea_constants : symmetric_tensor4_2d;</font>
<td><font size=2 face="Arial">Modify applicable cl</font></table>
<br><font size=2 face="sans-serif"><br>
***************************************************************************<br>
Heidi Preston<br>
Electric Boat Corporation<br>
Advanced Technology Group D604<br>
(860) 433-8649</font>