Kingsley,

[...]

> Coming, but current cut is based on Physical Quad Store Triples.
>
> The Virtual (RDF Views) variant is certainly coming too, but maybe not in
> the first release of v6.0.

Roger that. So then the general strategy could be:

MySQL Production DB --> (?A) --> Ph. Quad Store --> FCT --> UI

For (?A) we have several options.

The critical step in the data route is RDF mapping ( and rule
materialization for labels, etc ). I want to do this using RDF Views
over internal physical tables to do it the Virtuoso way. So, one
possible ?A:

MySQL --> ( (?B) --> Virtuoso Physical Tables --> RDFViews -->
select/insert into Quad ) --> FCT --> UI

For ?B we can use an ETL tool, but if there's a way to do this a la
Vituoso I would prefer that.
( the driver is not justified for now if this is going to be batch.
Later on when we link FCT to production DB it will ).

Any recommendations?
This is for a real estate portal that will serve as customer showcase.
( We are working on ODS too. It's the same codebase. We're just
bumping into details while we get used to Virt and Flex4. Big learning
curve * 2 ).

>>
>> And then, are there any structural/indexation requirements to keep in
>> mind?
>>
>
> Virtuoso is a Virtual DBMS as well as Native. ODBC and JDBC metadata calls
> are a VDBMS engines best friend. We already have "Locality based Cost
> Optimization" in the VDB layer (several years old, actually).

Yes of course.
I was just asking because it simply seems too much of a good thing ;)
( facets over RDF views over linked tables... and sponger, etc. Phew!
Panacea ahead )

>
> Kingsley
>>
>> Thanks,
>> A
>>
>>
>
>
> --
>
>
> Regards,
>
> Kingsley Idehen       Weblog: http://www.openlinksw.com/blog/~kidehen
> President & CEO OpenLink Software     Web: http://www.openlinksw.com
>
>
>
>
>


Thanks!
A


-- 
Aldo Bucchi
U N I V R Z
Office: +56 2 795 4532
Mobile:+56 9 7623 8653
skype:aldo.bucchi
http://www.univrz.com/
http://aldobucchi.com/

PRIVILEGED AND CONFIDENTIAL INFORMATION
This message is only for the use of the individual or entity to which it is
addressed and may contain information that is privileged and confidential. If
you are not the intended recipient, please do not distribute or copy this
communication, by e-mail or otherwise. Instead, please notify us immediately by
return e-mail.
INFORMACIÓN PRIVILEGIADA Y CONFIDENCIAL
Este mensaje está destinado sólo a la persona u organización al cual está
dirigido y podría contener información privilegiada y confidencial. Si usted no
es el destinatario, por favor no distribuya ni copie esta comunicación, por
email o por otra vía. Por el contrario, por favor notifíquenos inmediatamente
vía e-mail.

Reply via email to