Re: ISSUE-37, ACTION-138: DBMS connection details in R2RML mappings

On 7/13/11 12:29 AM, ashok malhotra wrote:
> Kingsley, why do we need to say anything about DB Connection in the 
> R2RML Standard?
> The standard is about mapping.

Only if we already say something about JDBC.
> You connect in any way that works for you and, as you know,
> there is a lot of variation in how you connect from vendor to vendor.
Sure, and that's fine if JDBC isn't part of the spec in any form. BTW -- 
I haven't read the very latest, I am sorta responding to specific points 
as they pass by. Thus, no JDBC means, yes no need to add connection 
details to spec etc..

> Why do we want to go there?

See comment above :-)

>
> My unstated goal in putting this issue on the agenda was the hope that
> we could close it quickly without action :-)

Hmm.. well you can see it has legs ...

Kingsley
> All the best, Ashok
>
> On 7/12/2011 3:55 PM, Kingsley Idehen wrote:
>> On 7/12/11 10:07 PM, Richard Cyganiak wrote:
>>> On 12 Jul 2011, at 21:12, Kingsley Idehen wrote:
>>>> On 7/12/11 8:25 PM, Richard Cyganiak wrote:
>>>>> I'd add:
>>>>>
>>>>> - authenticating user password
>>>>> - JDBC driver class name
>>>>> - JDBC connection properties
>>>>> - the base IRI
>>>>>
>>>>> This would complete the list of things one can specify in D2RQ 
>>>>> (all optional). A couple of them are wrapped into a JDBC URL.
>>>> What about ODBC ?
>>> We didn't support it in D2RQ (except for what you can do with 
>>> JDBC-ODBC bridges) since we were in a Java environment.
>>>
>>> For R2RML neither JDBC nor ODBC are really all that great because 
>>> both of them are tied so strongly to a particular implementation 
>>> environment.
>>>
>>> But defining a new, third option is of course also bad.
>>
>> What I am trying to highlight is the fact that SQL connections can be 
>> abstracted by merging JDBC and ODBC connections strings. They are 
>> both from the SAG CLI genealogy. There's little between them.
>>
>> Every RDBMS is ODBC and JDBC accessible, so we can list all the 
>> Attribute=Value pairs that constitute a connection URL.
>>> Hence my proposal to POSTPONE.
>>
>> If need be, Ted can pick up and deliver it quickly.
>>
>> Kingsley
>>> Best,
>>> Richard
>>>
>>>
>>>> Links:
>>>>
>>>> 1. http://www.connectionstrings.com/
>>>> 2. 
>>>> http://wiki.lazarus.freepascal.org/ODBCConn#The_ODBC_connection_string 
>>>> .
>>>>
>>>> -- 
>>>>
>>>> Regards,
>>>>
>>>> Kingsley Idehen
>>>> President&   CEO
>>>> OpenLink Software
>>>> Web: http://www.openlinksw.com
>>>> Weblog: http://www.openlinksw.com/blog/~kidehen
>>>> Twitter/Identi.ca: kidehen
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
>


-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen

Received on Wednesday, 13 July 2011 13:46:01 UTC