Revised SKOS-based translation table proposal

Regarding ISSUE-72 “Bring back R2RML lookup tables” [1], here's a new proposal:

   http://www.w3.org/2001/sw/rdb2rdf/drafts/translation-tables-DERI2.html

It is still SKOS-based like the first proposal [2], but drops the possibility of using skos:xxxMatch properties, and retains only the ability to use skos:notation, as suggested by David [3].

This makes it simpler than the Oracle proposal [4] in terms of new properties introduced and total triples needed to express a translation table. Since Souri's and Seema's objection to the original proposal [2] was about its complexity [5], I'm confident that the revised proposal is acceptable to them.

(The new proposal retains the ability to express non-bijective mappings, and is limited to mapping to IRIs. This differs from the Oracle proposal, which can only express bijective mappings, but can also map to literals.)

Ivan noted [6] that re-adding this feature would require a second last call.

Best,
Richard


[1] http://www.w3.org/2001/sw/rdb2rdf/track/issues/72
[2] http://www.w3.org/2001/sw/rdb2rdf/drafts/translation-tables-DERI.html
[3] http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2011Aug/0186.html
[4] http://www.w3.org/2001/sw/rdb2rdf/drafts/translation-tables-Oracle.html
[5] http://www.w3.org/2001/sw/rdb2rdf/track/issues/66
[6] http://lists.w3.org/Archives/Public/public-rdb2rdf-wg/2011Nov/0013.html

Received on Tuesday, 15 November 2011 12:03:22 UTC