Aldo Bucchi wrote:
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.
For now you Map, and then use the Mappings to triggered a physical quad
store bulk load. Basically, we used this approach to produce the
MusicBrainz dump that's making its way to EC2.
Virtuoso does offer ETL via replication options. And we plan to offer
some other option inline with SQL Servers offerings (re. SQL-SQL data
transfers). These are planned for the post V6.0 release dev. cycle
though. Short-term, you can leverage Virtuoso's in-built replication
functionality (but this is in the commercial edition) and implement for
you specific use case scenarios.
I think RDF Views to Quad Store is what you are looking for. Once the
data is in the Quad Store you can also leverage the reasoning
capabilities via inference rules and SPARQL pragmas (which is what is
happening withing "description.vsp" template).
Kingsley
( 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
--
Regards,
Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO
OpenLink Software Web: http://www.openlinksw.com
