- From: Nuno Lopes <nuno.lopes@deri.org>
- Date: Tue, 2 Aug 2011 17:39:01 +0100
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: Nuno Lopes <nuno.lopes@deri.org>, W3C RDB2RDF <public-rdb2rdf-wg@w3.org>
Hi all, Sorry but I somehow missed this email! On 27 Jul 2011, at 15:57, Richard Cyganiak wrote: > Nuno, > > Thanks for that. > > Is xsd:date for TIME a typo? Yes, fixed. > > How exactly should I read the “or”/“and” in the XSD column? The spec further defines an algorithm for this mapping, for instance, the "or" for FLOAT is dependent on the precision of the datatype in the implementation: under 24 bits is an xs:float otherwise is an xs:double. Not sure if all cases are this simple, I will check. > > For things like boolean and dates and times and durations, how exactly is the syntactic correspondence for the values? I mean, a normal SQL datetime literal isn't in the right lexical form for an XSD datetime literal. (I think there's a section in Part 14 about that, something about "data values"?) Regarding the lexical form of dates, times, and durations the facet is used to restrict the lexical value of the XSD datatype and the algorithm (which I did not look into in detail yet) seems to define a regular expression for the conversion from the SQL datatype to a valid form of the XSD datatype. -- Nuno Lopes > > On 27 Jul 2011, at 13:43, Nuno Lopes wrote: > >> Dear all, >> >> Regarding ACTION-141: Create a SQL/XSD data dataype mapping I've created a page in the Wiki [1] with the mappings defined in the SQL spec. This is mostly for built-in datatypes and does not consider "constructed" and "user-defined" types. Should the WG also provide a mapping for these types (I'm thinking mostly of constructed types) or only for built-in datatypes? >> >> Best regards, >> -- >> Nuno Lopes >> >> [1] http://www.w3.org/2001/sw/rdb2rdf/wiki/Mapping_SQL_datatypes_to_XML_Schema_datatypes >> >> >> >
Received on Tuesday, 2 August 2011 16:39:30 UTC