DR 10-0018: General: missing normative reference

[John Haug]

OK, fixed locally.  It will appear in the final version of the changes (unless altered by future comments).

From: Jim Thatcher
Sent: Thursday, March 29, 2012 1:22 PM
To: John Haug; SC34/WG4
Subject: RE: DR 10-0018: General: missing normative reference

Thanks John. Can you update the changes in Section 17.14.10 to delete the words "the" and "interface" that currently surround "ODBC"? Given the new definition of ODBC I don't think those words are necessary now.

Jim

From: John Haug [mailto:johnhaug at exchange.microsoft.com]
Sent: Thursday, March 29, 2012 1:16 PM
To: SC34/WG4
Subject: RE: DR 10-0018: General: missing normative reference

I took the liberty of making these changes in the usual faux tracked changes document attached, for the usual review.

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.

John

From: Jim Thatcher [mailto:Jim.Thatcher at microsoft.com]
Sent: Thursday, March 29, 2012 10:52 AM
To: MURATA Makoto; SC34/WG4
Subject: RE: DR 10-0018: General: missing normative reference


Following is the full text that I committed in the conference call last week to provide as the resolution for DR 09-0018.



Part 1, §4 - Add the following definition:

ODBC - 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.



Part 1, §17.14.10 - Modify the Example to replace the words "the Open Database Connectivity interface" with "ODBC".



Part 1, §17.18.52 - Replace the current entry for "odbc" in the table with the following:

odbc (ODBC Data Source)


Specifies that a given merged WordprocessingML document has been connected to an external data source via ODBC.


and modify the Example to replace the words "the Open Database Connectivity interface" with "ODBC".



Part 1, §18.10.1.3 - Replace the current entry for "sqlType" in the Attributes table with the following:

sqlType (SQL Data Type)


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.



For more information, including supported data types, see ISO 9075-3:2008, Table 33 - Codes used for concise data types.



The possible values for this attribute are defined by the W3C XML Schema int datatype.




Part 1, §18.13.6 - Replace the current entry for "sqlType" in the Attributes table with the following:

sqlType (SQL Data Type)


Specifies the SQL data type of the parameter.  This attribute is only supported for ODBC data sources.



For more information, including supported data types, see ISO 9075-3:2008, Table 33 - Codes used for concise data types.



The possible values for this attribute are defined by the W3C XML Schema int datatype.






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.



Jim



-----Original Message-----

From: Jim Thatcher

Sent: Wednesday, March 21, 2012 2:48 PM

To: MURATA Makoto; SC34/WG4

Subject: RE: DR 10-0018: General: missing normative reference



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.



Jim



________________________________________

From: eb2mmrt at gmail.com<mailto:eb2mmrt at gmail.com> [eb2mmrt at gmail.com] on behalf of MURATA Makoto [eb2m-mrt at asahi-net.or.jp]

Sent: Wednesday, March 21, 2012 7:23 AM

To: SC34/WG4

Subject: DR 10-0018: General: missing normative reference



This is about ODBC.  We made progress in Prague, but are we ready to close this tomorrow?



--



Praying for the victims of the Japan Tohoku earthquake



Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20120329/4adcac8c/attachment-0001.htm>