ISSUE-71: Column name collisions between child and parent queries in RefObjectMaps

child-parent-collision

Column name collisions between child and parent queries in RefObjectMaps

State:
CLOSED
Product:
R2RML
Raised by:
Richard Cyganiak
Opened on:
2011-11-07
Description:
This is part of David's Last Call comments:
http://lists.w3.org/Archives/Public/public-rdb2rdf-comments/2011Oct/0022.html

R2RML Section 8 states:

[[
SELECT * FROM ({child-query}) AS child, ({parent-query}) AS parent
]]

From a SQL perspective, this feels wrong because it doesn't address the issue of column name collisions between the child and parent query.

Is the thought that we can just ignore this because we describe in section 11 that the projected columns are split between child and parent?

This seems to be not fully thought through. I think either the spec needs something that states that the sets of columns are disjoint (but that would limit the usefulness), or the mechanics in sections 8 and 11 need to be changed.
Related Actions Items:
Related emails:
  1. Status update on LC comments and post-LC changes to R2RML (from richard@cyganiak.de on 2011-11-07)
  2. ISSUE-71 (child-parent-collision): Column name collisions between child and parent queries in RefObjectMaps [R2RML] (from sysbot+tracker@w3.org on 2011-11-07)

Related notes:

(There was no WG discussion or WG resolution on the issue.)

R2RML editor implemented a change that addresses it, as announced here (on comments list, not WG list):
http://lists.w3.org/Archives/Public/public-rdb2rdf-comments/2011Nov/0023.html

Richard Cyganiak, 20 Dec 2011, 17:52:45

Display change log ATOM feed


Ashok Malhotra <ashok.malhotra@oracle.com>, Michael Hausenblas <michael.hausenblas@deri.org>, Chairs, Eric Prud'hommeaux <eric@w3.org>, Ivan Herman <ivan@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 71.html,v 1.1 2012/10/16 16:28:41 vivien Exp $