Kingsley, On Thu, Feb 12, 2009 at 6:10 PM, Kingsley Idehen <kide...@openlinksw.com> wrote: > 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
Got it. Thanks! Just to put this on the list for others to debate/see/etc. This is the initial plan ( subject to change ). = TBox (once) = * Make SQL dump of MySQL/PG schema(s) * Load schema(s) into virtuoso ( Create Tables ) ** Minor manual syntax changes might be needed. Manual intervention is actually *good* as it forces us to understand the schema in depth ( and it is a reasonable amount of work ). * Create RDF Views = ABox (daily) = To load data from production DB ( batch ). * Dump data as CSV * Compress and upload to WebDAV folder on EC2 instance * Virtuoso will automatically load/update/etc This way we 1)pay careful attention to the mappings and 2)keep the contract with the provider of the data simple: Upload an agreed CSV formatted file via WebDAV to update instance data. Comments appreciated Thanks yet again, 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.
