<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#085296;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#993366;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#085296" vlink="#993366">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I took the liberty of making these changes in the usual faux tracked changes document attached, for the usual review.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I think an additional normative reference is needed, since Part 1 currently only refers to 9075-1. I pre-emptively added this to the attached.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Jim Thatcher [mailto:Jim.Thatcher@microsoft.com]
<br>
<b>Sent:</b> Thursday, March 29, 2012 10:52 AM<br>
<b>To:</b> MURATA Makoto; SC34/WG4<br>
<b>Subject:</b> RE: DR 10-0018: General: missing normative reference<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText">Following is the full text that I committed in the conference call last week to provide as the resolution for DR 09-0018.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Part 1, §4 - Add the following definition:<o:p></o:p></p>
<p class="MsoPlainText"><b>ODBC</b> – An implementation of ISO/IEC 9075-3:2008 “Information technology -- Database languages -- SQL -- Part 3: Call-Level Interface (SQL/CLI)” or SQL/CLI-based database connectivity API. An example of a broadly used SQL\CLI-based
database connectivity API is the Open Database Connectivity (ODBC) API.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Part 1, §17.14.10 – Modify the Example to replace the words “the Open Database Connectivity interface” with “ODBC”.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Part 1, §17.18.52 – Replace the current entry for “odbc” in the table with the following:<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:.4pt;border-collapse:collapse">
<tbody>
<tr>
<td width="191" valign="top" style="width:143.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText">odbc (ODBC Data Source)<o:p></o:p></p>
</td>
<td width="447" valign="top" style="width:335.2pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText">Specifies that a given merged WordprocessingML document has been connected to an external data source via ODBC.<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText">and modify the Example to replace the words “the Open Database Connectivity interface” with “ODBC”.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Part 1, §18.10.1.3 – Replace the current entry for “sqlType” in the Attributes table with the following:<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:.4pt;border-collapse:collapse">
<tbody>
<tr>
<td width="191" valign="top" style="width:143.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText">sqlType (SQL Data Type)<o:p></o:p></p>
</td>
<td width="447" valign="top" style="width:335.2pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText">Specifies the SQL data type of the field. This attribute applies to ODBC data sources only. A value is supplied for this attribute only if it is provided to the application.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">For more information, including supported data types, see ISO 9075-3:2008, Table 33 - Codes used for concise data types.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The possible values for this attribute are defined by the W3C XML Schema int datatype.<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Part 1, §18.13.6 – Replace the current entry for “sqlType” in the Attributes table with the following:<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:.4pt;border-collapse:collapse">
<tbody>
<tr>
<td width="191" valign="top" style="width:143.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText">sqlType (SQL Data Type)<o:p></o:p></p>
</td>
<td width="447" valign="top" style="width:335.2pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoPlainText">Specifies the SQL data type of the parameter. This attribute is only supported for ODBC data sources.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">For more information, including supported data types, see ISO 9075-3:2008, Table 33 - Codes used for concise data types.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The possible values for this attribute are defined by the W3C XML Schema int datatype.<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Based on a search for “odbc” in Part 1 and Part 4 this appears to be the extent of the changes needed to address the DR. Many other occurrences of ODBC or odbc exist, but those other instances are consistent with the definition included
above.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Jim<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class="MsoPlainText">From: Jim Thatcher <o:p></o:p></p>
<p class="MsoPlainText">Sent: Wednesday, March 21, 2012 2:48 PM<o:p></o:p></p>
<p class="MsoPlainText">To: MURATA Makoto; SC34/WG4<o:p></o:p></p>
<p class="MsoPlainText">Subject: RE: DR 10-0018: General: missing normative reference<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Yes, I think we can close on this in the call tomorrow. The proposed resolution in the DR log should address the concerns in the DR. I'd like to add one update to that proposal, which is to identify the specific part of the SQ/CLI standard
that should be referenced to describe the sqlType attribute in the tables in sections 18.10.1.3 and 18.13.6, which is ISO 9075-3:2008, Table 33 - Codes used for concise data types. If we decide to keep the existing partial lists of supported value/type pairs
we should remove the negative values from those lists (SQL/CLI standard defines values < 0 as implementation defined) and order both lists in the same order.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Jim<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">________________________________________<o:p></o:p></p>
<p class="MsoPlainText">From: <a href="mailto:eb2mmrt@gmail.com">eb2mmrt@gmail.com</a> [eb2mmrt@gmail.com] on behalf of MURATA Makoto [eb2m-mrt@asahi-net.or.jp]<o:p></o:p></p>
<p class="MsoPlainText">Sent: Wednesday, March 21, 2012 7:23 AM<o:p></o:p></p>
<p class="MsoPlainText">To: SC34/WG4<o:p></o:p></p>
<p class="MsoPlainText">Subject: DR 10-0018: General: missing normative reference<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This is about ODBC. We made progress in Prague, but are we ready to close this tomorrow?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Praying for the victims of the Japan Tohoku earthquake<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Makoto<o:p></o:p></p>
</div>
</body>
</html>