LinkedBrainz/Software Approach: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
===Virtuoso=== |
===Virtuoso=== |
||
Virtuoso Open Source was used in the Zitgist mappings. |
[http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/ Virtuoso Open Source] was used in the Zitgist mappings. See this [http://motools.svn.sourceforge.net/viewvc/motools/musicbrainz/mbz-rdf-view.sql?view=log mapping file]. |
||
===D2RQ=== |
===D2RQ=== |
||
[http://www4.wiwiss.fu-berlin.de/bizer/d2rq/ D2RQ] and the [http://www4.wiwiss.fu-berlin.de/bizer/d2r-server/ D2R server] were used in the DBTune mappings. |
[http://www4.wiwiss.fu-berlin.de/bizer/d2rq/ D2RQ] and the [http://www4.wiwiss.fu-berlin.de/bizer/d2r-server/ D2R server] were used in the DBTune mappings. See this [http://motools.svn.sourceforge.net/viewvc/motools/musicbrainz/musicbrainz_mo.n3?view=log mapping file]. |
||
Revision as of 22:18, 7 August 2010
There are several approaches to implementing LinkedBrainz in software. Broadly, these fall into two categories - modifying the MusicBrainz server code directly or using/modifying off-the-shelf software that translates the Postgres DB into RDF using RDF Views.
Modify MusicBrainz
We would modify the controllers in the codebase and create some additional views to serve RDF. This would allow/force us to adopt the same pagination scheme used for the HTML and ensure no heavy load on the DB server.
RDF Views
RDF Views allow the translation of an RDBMS into RDF. The main advantage is that this approach could side-step all pagination. However, this is also the major disadvantage as we must find some alternative method to limit the load on the DB server.
Virtuoso
Virtuoso Open Source was used in the Zitgist mappings. See this mapping file.
D2RQ
D2RQ and the D2R server were used in the DBTune mappings. See this mapping file.
