[Mulgara-dev] creating container nodes
William Mills
wmills_92105 at yahoo.com
Mon Feb 15 19:04:28 UTC 2010
Makes sense. Blank nodes is what I'm looking for. Is there a loader for N3, I've been looking at the docs a bit but don't find it yet.
Thanks,
-bill
________________________________
From: Paul Gearon <gearon at ieee.org>
To: Mulgara Developers <mulgara-dev at mulgara.org>
Sent: Mon, February 15, 2010 8:26:55 AM
Subject: Re: [Mulgara-dev] creating container nodes
On Sun, Feb 14, 2010 at 9:57 PM, William Mills <wmills_92105 at yahoo.com> wrote:
> I've got a data set which is (time, result, error code, login, ip,
> comment). To get this into Mulgara do I have to assign an arbitrary unique
> ID for each row so that I have a SQL report like:
>
> entity:$row_id rel:time $time .
> entity:$row_id rel:user $login .
> entity:$row_id rel:ip $ip .
>
> and so forth? So each of my tuples becomes an RDF for each column?
You don't HAVE to do it this way, but you can. This would usually be a
good candidate for a blank node, but by using IDs like this you can
map back and forth between the original SQL entry and the RDF data.
Alternatively, you could use a blank node, and associate the SQL ID
with a predicate. So the N3 might look like:
[ rel:time '...time...' ;
rel:user '...login...' ;
rel:ip '...ip...' ;
rel:id '...row_id...' ]
I believe that this is a more common mapping, but it's up to you.
Regards,
Paul Gearon
_______________________________________________
Mulgara-dev mailing list
Mulgara-dev at mulgara.org
http://mulgara.org/mailman/listinfo/mulgara-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20100215/cc08e096/attachment.htm>
More information about the Mulgara-dev
mailing list