I started a D2R [1] mapping for Musicbrainz, allowing to create a SPARQL end-point+linked data access out of Musicbrainz fairly easily - a D2R instance loaded with the mapping as it is now is available at: http://dbtune.org/musicbrainz/
Added to the things that are available within the Zitgist mapping: * SPARQL end point * Support for tags, * Supports a couple of advanced relationships (still working my way through it, though) * Instrument taxonomy directly generated from the db, and related to performance events * Support for orchestras
There is still a *lot* to do, though - it is really a start. The mapping is available under the musicbrainz/ directory on the motools sourceforge project: http://sourceforge.net/projects/motools
This made me spot an unclear point in MO level 1, also. In case of multiple releases of a single record, should there be several mo:Record? According to the fact that mo:Record rdfs:subClassOf mo:MusicalManifestation. there should indeed be several mo:Record - in this case, would mo:Release be a better name?
I think it makes thing more understandable: :a a mo:Signal; dc:title "example record, master"; mo:available_as :r1,:r2. :r1 a mo:Release; dc:title "example record, original release". :r2 a mo:Release; dc:title "example record, 1962 reedition".
On Mon, Apr 7, 2008 at 12:10 PM, Yves Raimond <yves.raim...@gmail.com> wrote: > Hello!
> I started a D2R [1] mapping for Musicbrainz, allowing to create a > SPARQL end-point+linked data access out of Musicbrainz fairly easily - > a D2R instance loaded with the mapping as it is now is available at: > http://dbtune.org/musicbrainz/
> Added to the things that are available within the Zitgist mapping: > * SPARQL end point > * Support for tags, > * Supports a couple of advanced relationships (still working my way > through it, though) > * Instrument taxonomy directly generated from the db, and related to > performance events > * Support for orchestras
> There is still a *lot* to do, though - it is really a start. The > mapping is available under the musicbrainz/ directory on the motools > sourceforge project: > http://sourceforge.net/projects/motools
> This made me spot an unclear point in MO level 1, also. > In case of multiple releases of a single record, should there be > several mo:Record? According to the fact that > mo:Record rdfs:subClassOf mo:MusicalManifestation. > there should indeed be several mo:Record - in this case, would > mo:Release be a better name?
> I think it makes thing more understandable: > :a a mo:Signal; dc:title "example record, master"; mo:available_as :r1,:r2. > :r1 a mo:Release; dc:title "example record, original release". > :r2 a mo:Release; dc:title "example record, 1962 reedition".
I seem to be getting the following error when doing SPARQL queries
through the SNORQL interface, or clicking the "artist" link:
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /musicbrainz/
directory/artist.
Reason: Error reading from remote server
On Apr 7, 4:10 am, "Yves Raimond" <yves.raim...@gmail.com> wrote:
> I started a D2R [1] mapping for Musicbrainz, allowing to create a
> SPARQL end-point+linked data access out of Musicbrainz fairly easily -
> a D2R instance loaded with the mapping as it is now is available at:http://dbtune.org/musicbrainz/
> Added to the things that are available within the Zitgist mapping:
> * SPARQL end point
> * Support for tags,
> * Supports a couple of advanced relationships (still working my way
> through it, though)
> * Instrument taxonomy directly generated from the db, and related to
> performance events
> * Support for orchestras
> There is still a *lot* to do, though - it is really a start. The
> mapping is available under the musicbrainz/ directory on the motools
> sourceforge project:http://sourceforge.net/projects/motools
> This made me spot an unclear point in MO level 1, also.
> In case of multiple releases of a single record, should there be
> several mo:Record? According to the fact that
> mo:Record rdfs:subClassOf mo:MusicalManifestation.
> there should indeed be several mo:Record - in this case, would
> mo:Release be a better name?
> I think it makes thing more understandable:
> :a a mo:Signal; dc:title "example record, master"; mo:available_as :r1,:r2.
> :r1 a mo:Release; dc:title "example record, original release".
> :r2 a mo:Release; dc:title "example record, 1962 reedition".
On Mon, Apr 7, 2008 at 11:39 PM, <kriso...@gmail.com> wrote:
> I seem to be getting the following error when doing SPARQL queries > through the SNORQL interface, or clicking the "artist" link:
> The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request GET /musicbrainz/ > directory/artist.
> On Mon, Apr 7, 2008 at 11:39 PM, <kriso...@gmail.com> wrote:
> > I seem to be getting the following error when doing SPARQL queries
> > through the SNORQL interface, or clicking the "artist" link:
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request GET /musicbrainz/
> > directory/artist.
> On Mon, Apr 7, 2008 at 11:39 PM, <kriso...@gmail.com> wrote:
> > I seem to be getting the following error when doing SPARQL queries
> > through the SNORQL interface, or clicking the "artist" link:
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request GET /musicbrainz/
> > directory/artist.
