<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Consolas, monospace" size="2">
<div>In the interest of making progress on the other DRs, let's make the following change to 22.9.2.13:</div>
<div> </div>
<div style="padding-left: 36pt; "><font face="Cambria, serif" size="3">22.9.2.13 ST_String (String)</font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2">This simple type specifies that its contents contains a string. The contents of this string are interpreted based on</font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2">the context of the parent XML element.</font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2"> </font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"><strike>[</strike><font face="Calibri,Italic, sans-serif"><strike><i>Example</i></strike></font><strike>: Consider the following WordprocessingML fragment:</strike></font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> </font></div>
<div style="padding-left: 72pt; "><font size="2" color="#FF0000"><strike><w:pPr></strike></font></div>
<div style="padding-left: 72pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> <font face="Consolas, monospace"><strike><w:pStyle w:val="heading1" /></strike></font></font></div>
<div style="padding-left: 72pt; "><font size="2" color="#FF0000"><strike></w:pPr></strike></font></div>
<div style="padding-left: 72pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> </font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"><strike>The value of the </strike><font face="Cambria, serif"><strike>val </strike></font><strike>attribute is the ID of the associated paragraph style's </strike><font face="Consolas, monospace"><strike>styleId</strike></font><strike>.
However, consider the</strike></font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"><strike>following fragment:</strike></font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> </font></div>
<div style="padding-left: 72pt; "><font size="2" color="#FF0000"><strike><w:sdtPr></strike></font></div>
<div style="padding-left: 72pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> <font face="Consolas, monospace"><strike><w:alias w:val="SDT Title Example" /></strike></font></font></div>
<div style="padding-left: 72pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> <font face="Consolas, monospace"><strike>…</strike></font></font></div>
<div style="padding-left: 72pt; "><font size="2" color="#FF0000"><strike></w:sdtPr></strike></font></div>
<div style="padding-left: 72pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"> </font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"><strike>In this case, the decimal number in the </strike><font face="Cambria, serif"><strike>val </strike></font><strike>attribute is the caption of the parent structured
document tag. In</strike></font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"><strike>each case, the value is of type </strike><font face="Cambria, serif"><strike>ST_String</strike></font><strike>, and therefore must be interpreted in the context
of the parent</strike></font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2" color="#FF0000"><strike>element. </strike><font face="Calibri,Italic, sans-serif"><strike><i>end example</i></strike></font><strike>]</strike></font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif" size="2"> </font></div>
<div style="padding-left: 36pt; "><font face="Calibri, sans-serif">This simple type's contents are a restriction of the W3C XML Schema <font face="Cambria, serif">string </font>datatype.</font></div>
<div> </div>
<div>I believe that these changes will resolve all of the discussions we’ve had thus far on the reflector. Perhaps we can move this defect report to last call?</div>
<div> </div>
<div>Thanks,</div>
<div> </div>
<div>shawn</div>
<div> </div>
<div>-----Original Message-----<br>
From: MURATA Makoto (FAMILY Given) [<a href="mailto:eb2m-mrt@asahi-net.or..jp">mailto:eb2m-mrt@asahi-net.or.jp</a>]
<br>
Sent: Thursday, April 23, 2009 4:46 AM<br>
To: e-SC34-WG4@ecma-international.org<br>
Subject: Re: DR-08-0014: Shared MLs, Shared Simple Types: ST_String example description error</div>
<div> </div>
<div>> I do believe that the current text of 22.9.2.13 serves a purpose: that </div>
<div>> attributes of the same name, used in different contexts, have</div>
<div>> potentially different meanings. </div>
<div> </div>
<div>Context dependencies do not belong to ST_String but belong to </div>
<div>attributes or elements, and thus should not be described here. </div>
<div> </div>
<div>There are other semantic issues about strings, such as case-(in)sensitivity. </div>
<div>When no other such semantic issues are mentioned here, why should </div>
<div>we care context dependencies?</div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>-- </div>
<div>Makoto <EB2M-MRT@asahi-net.or.jp></div>
<div> </div>
<div> </div>
<div> </div>
</font>
</body>
</html>