Hi Mirko,
Am 14.10.2010 15:08, schrieb Mirko:
Thank you all for your helpful comments. First, let me clarify my
intention. My question aimed not so much at the (internal) storage of
the data, but really on how to publish them as Linked Data, so that they
are useful for third parties (= easy to q
Thank you all for your helpful comments. First, let me clarify my intention.
My question aimed not so much at the (internal) storage of the data, but
really on how to publish them as Linked Data, so that they are useful for
third parties (= easy to query and consume).
I use Virtuoso and want to pu
Aldo,
On Wed, 2010-10-13 at 16:02 -0300, Aldo Bucchi wrote:
> From the docs:
>
> "output:route: works only for SPARUL operators and tells the SPARQL
> compiler to generate procedure names that differ from default. As a
> result, the effect of operator will depend on application. That is for
> tri
Hi Ivan,
Hehe, I knew you were going to jump in, that's why I CC'd this to
virtuoso-users ;)
Before getting into the content of your response, let me just say this:
I think Mirko's example is actually really common. Every application
that I have built needs to keep track of ( at least ) two othe
Hello Aldo,
I'd recommend to keep RDF_QUAD unchanged and use RDF Views to keep n-ary
things in separate tables. The reason is that the access to RDF_QUAD is
heavily optimized, we've never "polished" any other table to such a
degree (and I hope we will not :), and any changes may result in severe
p
Hi Mirko,
Here's a tip that is a bit software bound but it may prove useful to
keep it in mind.
Virtuoso's Quad Store is implemented atop an RDF_QUAD table with 4
columns (g, s, p o). This is very straightforward. It may even seem
naive at first glance. ( a table!!? ).
Now, the great part is tha
