Re: ISSUE-9 Another question about Generate Blank Nodes

Let me see if I understand the problem.

Suppose we have a table with no primary key and many columns.
A triple would be generated for each column in the table and all the triples
for a row would be anchored by a blank node.  Is this correct?

So, the problem is that we have a blank node anchoring the triples for each
row but, really, the blank nodes for each row represent different entities.  Is this correct?

If so, then I'm with Soeren.  We can improve the details of his solution but his
direction seems right.

All the best, Ashok

On 2/1/2011 2:11 PM, Sören Auer wrote:
> Hi all,
>
> In todays telco several people (including Souri and me) supported the idea to abandon the use of blank notes. Is there any fundamental reason (beside philosopical views) to use blank nodes?
> If not I suggest we just generate IRIs for all resources. Of course this does not yet solve the problem of how they should be created, but we could follow the following strategy:
>
> * if there is a candidate key use the candidate key,
> * if there is no candidate key, but an internal row identifier (e.g. Virtuoso has such one always) use this row identifier,
> * if nether one exists, generate an identifier using a hash function over all values of the row + an incremented counter in case duplicate rows exist
>
> Wouldn't this be a simple and effective solution to the problem?
>
> Best,
>
> Sören
>