<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 5.50.4913.1100" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#fff8e0>
<DIV><FONT size=2>Dear (acting) WG11 convenor,</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>In October 2001, we exchanged some emails about the lack of
clear status of Part28 document and about the lack of answers to issues raised
on an intermediate working draft of this part (WG11 N173).</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>From that date, I have received no other answer about these
issues and the status of Part28 keeps on being unclear to me.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>So, as Myrtle Beach approaches and in preparation of WG11
meetings, I resend my whole list of questions:</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I) Project management issues:</FONT></DIV>
<DIV>- do you have any indication from the project leader about the planned
dates for the release of ISO/TS 10303-28?</DIV>
<DIV>- can/should we still consider that there will be a ISO/TS 10303-28
document (resulting from the resolutions of issues on the balloted CDTS) ?<BR>-
who is the actual or acting project leader of ISO/TS 10303-28 (the guy who signs
off)?</DIV>
<DIV>- who is the actual or acting editor of the document ISO/TS 10303-28
(the guy who signs off)?</DIV>
<DIV>- what is the latest WG11 document for ISO/TS 10303-28?</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>II) Editorial/technical issues on the document WG11 N173
:</FONT><BR>
<DIV><FONT size=2>1 - there is no information about the element
DOCTYPE:</FONT></DIV>
<DIV><FONT size=2> - is it mandatory? For all the
bindings?</FONT></DIV>
<DIV><FONT size=2> - what is its required
content?</FONT></DIV>
<DIV><FONT size=2> - what is the meaning of the value SYSTEM
found in the examples?</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>2 - there is no information about the meaning of the symbols
?, *, +, % in the specification of the elements (e.g. see 6.1). In
comparison to P21 where all grammar syntax elements are explained, this is
considered as a lack in P28.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>3 - OSEB: it is not clear how an entity that has
several supertypes shall be processed when they inherit, from their supertypes,
attributes that have the same name</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>4 - OSEB: it is not clear whether a value of a derived
attribute or of an inverse attribute shall or shall not be provided in XML data
files. Add a subclause in §9.9 about that</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>
<DIV><FONT size=2>5 - OSEB: it is not clear whether a value shall or shall not
be provided in XML data files for Where rules or Unique rules. Add a subclause
in §9.9 about that.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV></DIV>
<DIV><FONT size=2>6 - OSEB: it is not clear how an instance of an entity shall
be encoded when this entity has a derived attribute, inherited from a
supertype</FONT></DIV>
<DIV><FONT size=2> - How shall the value of the derived
attribute be encoded?</FONT></DIV>
<DIV><FONT size=2> - shall a value be provided for the
attribute of the supertype?</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>7 - OSEB: it is not clear how an attribute value that is an
empty aggregate shall be encoded (e.g. if the value of a inverse attribute is to
be exported)</FONT></DIV>
<DIV><FONT size=2> - shall the attribute be present or not?
(NB: there may be a problem with the #REQUIRED in the !ATTLIST of aggregate
types)</FONT></DIV>
<DIV><FONT size=2> - how the empty collection shall be
represented? enpty string ""?</FONT></DIV>
<DIV><FONT size=2> </FONT><FONT size=2></FONT></DIV>
<DIV><FONT size=2>8 - annexes E and G deal with about the same topic (URN). They
should be merged in one annex.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>9 - annex E: the name of the AIM schema of AP203 is
config_control_design (without _schema)</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2><FONT size=2><FONT face=Arial>10 - annex E: the way an Express
schema is identified is not satisfactory as the concept of version is not so
clear (becuase intermediate drafts, TCs and amendments need also to be
considered. </FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT size=2><FONT face=Arial>An Express schema should only be
identified by its ASN1 registration code and Part28 should
specify:</FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT size=2><FONT
face=Arial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=2><FONT size=2><FONT size=3>
<P
align=center>urn:iso10303-28:<I>p28_binding</I>/iso_standard-<I>isonum</I>/schema
identifier/<I>schema_name</P></I></FONT></DIV></FONT></FONT>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>11 - §10.3 - The meaning and the structure of the element
!NOTATION should be explained</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>12 - §10.3 - The meaning and the structure of the element
!ENTITY should be explained, especially because of the name of the element which
has a precise meaning in ISO 10303-11</FONT><FONT size=2>.</FONT></DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT size=2>13 - according to annex E and annex G:</FONT></DIV>
<DIV><FONT size=2> - use of "</FONT><FONT
size=2>urn:iso10303-28:osb/" before a schema name should be replaced by
"</FONT><FONT size=2>urn:iso10303-28:oseb/" in the whole P28 (NB: another
solution would be to change the specification of p28_binding in annex
E)</FONT></DIV>
<DIV><FONT size=2> - occurrences of urn:iso10303-28:osb:osb
are wrong</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>14 - OSEB (§9.9.9): the line</FONT></DIV>
<DIV><FONT face=Arial size=2> <FONT face=Courier size=2>#40 =
A(Pipe(P1-1));</FONT></FONT></DIV>
<DIV><FONT size=2>is wrong and should be replaced by</FONT></DIV>
<DIV><FONT size=2><FONT face=Arial> </FONT><FONT face=Courier
size=2>#40 = A(#50);</FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial> </FONT><FONT face=Courier
size=2>#50 = PIPE('P1-1');</FONT></FONT></DIV></DIV>
<DIV> </DIV>
<DIV>15 - annex J.
<DIV><FONT face=Arial size=2>This annex, informative, contains an
instanciation example.</FONT></DIV>
<DIV><FONT face=Arial size=2>But instead of having chosen a simple one, showing
main encoding principles, a big one has been selected. The result is that this
annex contains more than 100 pages of unreadable and
uncommented text.</FONT></DIV>
<DIV><FONT face=Arial size=2>So, this annex presently completely misses its
purpose of facilitating understanding of P28 specifications.</FONT></DIV>
<DIV><FONT face=Arial size=2>Could we get a simpler, sensibly-sized and
commented example?</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Best regards,</DIV>
<DIV> </DIV></DIV></FONT></DIV></DIV>
<DIV><FONT size=2>Pascal Huau<BR>Association GOSET<BR>107,111 avenue Georges
Clemenceau<BR>92000 Nanterre<BR>FRANCE</FONT></DIV></BODY></HTML>