- From: Juan Sequeda <juanfederico@gmail.com>
- Date: Wed, 14 Dec 2011 15:01:57 -0500
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: Souripriya Das <souripriya.das@oracle.com>, public-rdb2rdf-wg@w3.org
- Message-ID: <CAMVTWDwmOTZRb8Z7w+Lt7dSpjmN_XUWquSbGeqt98bqB7AR18Q@mail.gmail.com>
On Wed, Dec 14, 2011 at 1:47 PM, Richard Cyganiak <richard@cyganiak.de>wrote: > Hi Souri, > > On 14 Dec 2011, at 16:05, Souripriya Das wrote: > > We have made the examples in this page more complete. > > > > > http://www.w3.org/2001/sw/rdb2rdf/wiki/Translating_Database_Values_to_RDF_Terms > > > > Please read it if you get a chance. > > I did, but I'm not sure that I grasp the point. Are you saying that > translation tables can be written as R2RML views without too much effort > and hence are not needed in R2RML 1.0? > Maybe :) But it would be an "ugly" sql query. However, if you are a db guy, you may be more comfortable writing SQL than learning R2RML. If you are a semweb guy, then you would be comfortable with the translation tables in R2RML. Therefore, I believe that we need to have translation tables. Comparing both proposals: Souri: x:myTranslationScheme rr:translationMap [ rr:toTerm <http://www.nyc.gov> ; rr:fromTerm < http://www.city.New%20York.NY.us> ] ; [ rr:toTerm <http://www.cityofboston.gov> ; rr:fromTerm < http://www.city.Boston.MA.us> ] ; [ rr:toTerm <http://www.atlantaga.gov> ; rr:fromTerm < http://www.city.Atlanta.GA.us> ] ; [ rr:toTerm <http://www.miamigov.com> ; rr:fromTerm < http://www.city.Miami.FL.us> ] ; [ rr:toTerm <http://www.dallascityhall.com> ; rr:fromTerm < http://www.city.Dallas.TX.us> ] ; [ rr:toTerm <http://www.lacity.org> ; rr:fromTerm < http://www.city.Los%20Angeles.CA.us> ] ; [ rr:toTerm <http://www.sfgov.org> ; rr:fromTerm < http://www.city.San%20Francisco.CA.us> ] ; [ rr:toTerm <http://www.seattle.gov> ; rr:fromTerm < http://www.city.Seattle.WA.us> ] ; [ rr:toTerm <http://www.cityofchicago.org> ; rr:fromTerm < http://www.city.Chicago.IL.us> ] . Richard: [] skos:inScheme x:myTranslationScheme; skos:notation <http://www.city.New%20York.NY.us>; skos:exactMatch <http://www.nyc.gov>. [] skos:inScheme x:myTranslationScheme; skos:notation <http://www.city.Boston.MA.us>; skos:exactMatch <http://www.cityofboston.gov>. ..... So basically rr:translationMap ~= skos:inScheme rr:fromTerm = skos:notation rr:toTerm = skos:exactMatch Souri's proposal would avoid the following repetitive triple [] skos:inScheme x:myTranslationScheme; Am I missing something else? > Best, > Richard >
Received on Wednesday, 14 December 2011 20:02:46 UTC