[wg11] Technical comments to be addressed at March 15 Part 28 meeting

[Heidi L Preston]

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:



JP-1 
(FT)
10303-28
7.2.1.6 
8.2.1.6
Exception
te
EXPRESS REAL data type with precision need to be mapped. 
EXPRESS REAL data type with precision need to be mapped to xs:double 
without restriction of the precision.
JP-2 
(FT)
10303-28
10.2.13.1
First and second item
te
xs:IDREF and xs:IDREFS are not suitable for the values of the map 
directive
These items should be deleted.


US-3
7.4.3/ 8.4.3
Para 1, NOTE 1
tech
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.
Modify the wording to include renames of SELECTS.
 

US-6
Annex C, 7.5.3.3, 8.5.3.5
 
tech
exp:complexEntity requires the nillable attribute.  The 'entities' 
attribute should be optional.
Make exp:complexEntity nillable.

US-8
Annex C, 7.5.3.3, 8.5.3.5
 
tech
The current xs:sequence in complexEntity is problematic.  It is unclear 
how the current configuration does anything meaningful.
Change the contents of the xs:sequence in exp:complexEntity to be: 
<xs:any namespace=”##any” processContents=”skip” maxOccurs=”unbounded”/>
US-9
7.3.4.2/ 8.3.4.2
 
tech
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.
Resolve Su
US-10
7.3.4/ 8.3.4, 7.2.2/ 8.2.2
 
tech
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 : 
<xs:element ref==”ex:arraySize” use=”optional”/>
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.
TYPE symmetric_tensor4_2d = SELECT (anisotropic_ symmetric_tensor4_2d); 
END_TYPE;
TYPE anisotropic_symmetric_tensor4_2d = ARRAY [1:6] OF 
context_dependent_measure;END_TYPE;
Fea_constants : symmetric_tensor4_2d;
Modify  applicable cl

***************************************************************************
Heidi Preston
Electric Boat Corporation
Advanced Technology Group D604
(860) 433-8649
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.steptools.com/pipermail/wg11/attachments/20070306/711cd805/attachment.htm