<!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.4134.600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=710285211-19102001>All,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=710285211-19102001></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=710285211-19102001>A
quick response to a few of Pascal's issues:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=710285211-19102001></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=710285211-19102001>1, 2,
11 and 12 - The audience of Part 28 is an implementor who is
fluent in EXPRESS and the XML 1.0 Recommendation. Therefore, repeating the
definitions found in the XML spec for ?, *, +, %, ENTITY, NOTATION, etc. in
the XML syntax is not appropriate info to be included in Part 28. The XML
Spec is freely available on the Web and, to be frank, if P28 becomes popular
it's more likely the readers won't know EXPRESS than that they won't know
XML.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=710285211-19102001></SPAN></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN class=710285211-19102001><FONT
face=Arial color=#0000ff>Thanks,</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=710285211-19102001>David</SPAN></FONT></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=710285211-19102001></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=710285211-19102001> </SPAN>-----Original Message-----<BR><B>From:</B>
owner-wg11@steptools.com [mailto:owner-wg11@steptools.com]<B>On Behalf Of
</B>Pascal Huau<BR><B>Sent:</B> 2001 October 19 07:49<BR><B>To:</B>
WG11<BR><B>Subject:</B> Various issues on WG11N173<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV><FONT size=2>Dear all,</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>please find hereafter issues against the current draft
(WG11N173) of Part28:</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<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)</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.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial></FONT> </DIV>Regards,</FONT></DIV>
<DIV><FONT size=2>Pascal Huau<BR>Association GOSET<BR>107,111 avenue Georges
Clemenceau<BR>92000 Nanterre<BR>FRANCE</FONT></DIV></BLOCKQUOTE></BODY></HTML>