- From: Thomas B. Passin <tpassin@home.com>
- Date: Tue, 21 Aug 2001 09:21:42 -0400
- To: <www-rdf-interest@w3.org>
[David Allsopp ] > > "Thomas B. Passin" wrote: > > > > Now if John did indeed have two fathers after all, the situation would be > > more complex, because on merging the two data sources, our processor would > > have to convert the hasFather statements into some kind of a container, > > Why? Why not just have two hasFather properties? > Only because I was thinking about triples in a relational database table right after my post about that, and you couldn't have two different rows with the same primary key. It's not the only way to do it, of course. I suppose, sticking with a relational table for a minute, that you could make the entire row the primary key. Then you could get multiple property values for the same subject. Cheers, Tom P
Received on Tuesday, 21 August 2001 09:18:32 UTC