- From: ashok malhotra <ashok.malhotra@oracle.com>
- Date: Tue, 11 Oct 2011 08:31:24 -0700
- To: public-rdb2rdf-wg@w3.org
I changed the subject. How about: [[ Extensions to the Direct Mapping should note the spirit of this mapping, i.e. to use a valid representation of an XML Schema Datatype corresponding to the SQL datatype. For numerics, booleans and dates, the canonical XML Schema lexical representation is used. Vendor extensions may represent data outside of the minimal SQL conformance. Such data will map to data types with higher precision than those specified by the literal map. The exact mapping of data outside of the SQL specification is not specified in this document. ]] You said: I'd like editorial suggestions, as well as advice from the WG about whether we should materialize the ellusive minimal intersection between SQL and XSD so that others don't have to do it: decimal 18 digits per XSD integer 18 digits per XSD double '±' + 16ch mantissa + 4ch exp per IEEE754 // what to do with NAN, +∞, −∞? date 4 digits per SQL time hh:mm:ss.mmmmmm per SQL I think this information is valuable and should be included in both specs. All the best, Ashok On 10/11/2011 8:00 AM, Eric Prud'hommeaux wrote: > [[ > Extensions to the Direct Mapping should note the spirit of this mapping, i.e. to use a valid representation of an XML Schema Datatype corresponding to the SQL datatype. For numerics, booleans and dates, the canonical XML Schema lexical representation is used. Extensions are likely to map data outside of the minimal SQL conformance into data types with higher precision than those specified by the literal map. > ]] >
Received on Tuesday, 11 October 2011 15:32:01 UTC