primary key that's already a uri?

http://www.w3.org/TR/2010/WD-rdb-direct-mapping-20101118/#row_iri

"The IRI that identifies a row is created by  ..."

Please consider the cases where people do have the freedom to use a 
complete URI as the primary key in their RDB. When I can build my RDB 
with RDF mapping in mind, that is the most natural thing to do. I would 
like to see an alternate row node scheme that simply takes the PK string 
and treats it as the row node.

This use case will come up especially often when people are designing 
hybrid systems that store what they can in RDF, but keep some data as 
RDB rows for reasons of performance, space economy, existing tool 
support, etc.



I also wonder if users will have tables with a boring PK (e.g. an int) 
but with another column that contains URIs. Generating <People/ID=8#_> 
<People#URI> "http://foaf.org/person/Bob" is silly; we should be able to 
indicate that the 'URI' column *is* the row node, even if it's not the 
PK. This would also be a general solution for people who want other URI 
forms for their rows: they could always augment their tables with a 
hand- or auto-generated URI column that's used instead of your built-in 
algorithm.

Received on Friday, 19 November 2010 08:16:11 UTC