Re: issues with RDB engines/dialects IRIs for EARL results

> there was a resolution about this yesterday?

We agreed to use http://www.w3.org/2001/sw/wiki/RDB2RDF/SQL_Version_IRIs - maybe Eric and Richard can quickly confirm that we're good to go?

Cheers,
	   Michael

--
Dr. Michael Hausenblas, Research Fellow
DERI - Digital Enterprise Research Institute
NUIG - National University of Ireland, Galway
Ireland, Europe
Tel.: +353 91 495730
WebID: http://sw-app.org/mic.xhtml#i

On 20 Jun 2012, at 09:22, Boris Villazon-Terrazas wrote:

> Hi all
> 
> there was a resolution about this yesterday?
> 
> Boris
> 
> 
> Begin forwarded message:
> 
>> Resent-From: public-rdb2rdf-wg@w3.org
>> From: Kingsley Idehen <kidehen@openlinksw.com>
>> Subject: Re: issues with RDB engines/dialects IRIs for EARL results
>> Date: June 19, 2012 8:28:56 PM GMT+02:00
>> To: public-rdb2rdf-wg@w3.org
>> 
>> On 6/19/12 1:01 PM, Ted Thibodeau Jr wrote:
>>> All --
>>> 
>>> See <http://www.w3.org/2001/sw/wiki/RDB2RDF/SQL_Version_IRIs>.
>>> 
>>> The current table lists --
>>> 
>>> Language Version       IRI
>>> ================       ======================================
>>> Core SQL:2008          http://www.w3.org/ns/r2rml#SQL2008
>>> Oracle Database        http://www.w3.org/ns/r2rml#Oracle
>>> MySQL                  http://www.w3.org/ns/r2rml#MySQL
>>> Microsoft SQL Server   http://www.w3.org/ns/r2rml#MSSQLServer
>>> HSQLDB                 http://www.w3.org/ns/r2rml#HSQLDB
>>> PostgreSQL             http://www.w3.org/ns/r2rml#PostgreSQL
>>> 
>>> 
>>> I see a few moderately significant issues --
>>> 
>>> 1. Engines not listed above which should be added to cover all
>>>    current WG member implementations/testing include Ingres,
>>>    Progress OpenEdge, DB2, Informix, Sybase ASE, Sybase SQL
>>>    Anywhere, OpenLink Virtuoso.  (We are testing against all
>>>    of these.)  There may well be more.
>> 
>> Firebird should also be added.
>> 
>> ODBC and JDBC are actually safer reference points than "Core SQL:2008" . We have to find a way to incorporate ODBC and JDBC bridges.
>> 
>> Note: in our R2RML tests, all of the above work fine. Thus, nothing here is speculative.
>> 
>>> 
>>> 2. There is a need to distinguish between versions of the above
>>>    engines (e.g., Oracle 8i, 9i, 10g, 11i; Microsoft SQL Server
>>>    6, 7, 2000, 2005, 2008, 2012; MySQL 3, 4, 5; etc.), because
>>>    SQL:2008 is not supported by all current versions, never mind
>>>    all past versions, and R2RML/DM implementation support of
>>>    these engines/versions will therefore vary.
>>> 
>>>    I don't *think* we need to go down to build/binary version
>>>    level, but I do think we need to go down as far as major
>>>    release version of each dialect/engine.
>>> 
>>>    This *could* be done by removing "Version" entirely from the
>>>    above ("Core SQL:2008" is arguably not a version but a dialect
>>>    of its own) and requiring a version disclosure along with the
>>>    "Dialect" (which label I'd put in place of "Language Version"
>>>    above)... but that is potentially clumsy, and makes the simple
>>>    IRIs we've minted insufficient as identifiers.
>> 
>> +1
>> 
>>> 
>>> 3. If we're going to keep a live results report page, then it
>>>    seems we'll need to keep a live identifiers page, such that
>>>    new engines can be added over time.
>> 
>> +1
>> 
>> For those of us to live and breathe RDBMS connectivity middleware, contributing to such a Wiki isn't going to be burdensome.
>> 
>> Kingsley
>>> 
>>> Thoughts?
>>> 
>>> Ted
>>> 
>>> 
>>> --
>>> A: Yes.                      http://www.guckes.net/faq/attribution.html
>>> | Q: Are you sure?
>>> | | A: Because it reverses the logical flow of conversation.
>>> | | | Q: Why is top posting frowned upon?
>>> 
>>> Ted Thibodeau, Jr.           //               voice +1-781-273-0900 x32
>>> Senior Support & Evangelism  //        mailto:tthibodeau@openlinksw.com
>>>                              //              http://twitter.com/TallTed
>>> OpenLink Software, Inc.      //              http://www.openlinksw.com/
>>>          10 Burlington Mall Road, Suite 265, Burlington MA 01803
>>>      Weblog   -- http://www.openlinksw.com/blogs/
>>>      LinkedIn -- http://www.linkedin.com/company/openlink-software/
>>>      Twitter  -- http://twitter.com/OpenLink
>>>      Google+  -- http://plus.google.com/100570109519069333827/
>>>      Facebook -- http://www.facebook.com/OpenLinkSoftware
>>> Universal Data Access, Integration, and Management Technology Providers
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Regards,
>> 
>> Kingsley Idehen	
>> Founder & CEO
>> OpenLink Software
>> Company Web: http://www.openlinksw.com
>> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>> Twitter/Identi.ca handle: @kidehen
>> Google+ Profile: https://plus.google.com/112399767740508618350/about
>> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>> 
>> 
>> 
>> 
>> 
>

Received on Wednesday, 20 June 2012 08:27:45 UTC