LinkedBrainz/NGS to RDF mappings: Difference between revisions
Line 78: | Line 78: | ||
* '''tracklist''' and '''artist_credit''' objects are described (completely?) by properties attached to various concepts (e.g. '''mo:SignalGroup''' and '''mo:Signal''') and require no URIs for themselves |
* '''tracklist''' and '''artist_credit''' objects are described (completely?) by properties attached to various concepts (e.g. '''mo:SignalGroup''' and '''mo:Signal''') and require no URIs for themselves |
||
* what property associates a '''mo:SignalGroup''' ('''release_group''') to a '''mo:Release''' ('''release''')??? |
* what property associates a '''mo:SignalGroup''' ('''release_group''') to a '''mo:Release''' ('''release''')??? |
||
===proposal 1 (dataincubator) === |
|||
These are the mapping I have worked on as part of my http://musicbrainz.dataincubator.org// conversion |
|||
{| |
|||
|+ align="bottom" |''proposed mappings to mo - kurtjx'' |
|||
! type |
|||
! NGS |
|||
! RDF |
|||
|- |
|||
|rowspan="7"|core entities |
|||
with mbids |
|||
|- |
|||
|'artist' |
|||
| 'mo:MusicArtist' (type=1' => mo:SoloMusicArtist, type=2 => mo:MusicGroup) |
|||
|- |
|||
|'release' |
|||
|'mo:Release' and 'mo:ReleaseEvent' (1:1 mapping) |
|||
|- |
|||
|'release_group' |
|||
|'mo:SignalGroup' |
|||
|- |
|||
|'recording' |
|||
|'mo:Signal' |
|||
|- |
|||
|'label' |
|||
|'mo:Label' |
|||
|- |
|||
|'work' |
|||
|'mo:MusicalWork' |
|||
|- |
|||
|rowspan="4"|entities |
|||
with a URI |
|||
(potentially) |
|||
|- |
|||
|'url' |
|||
| untyped, I parse wikipedia links to create owl:sameAs to dbpedia, and discogs links for owl:sameAs to discogs.dataincubator.org |
|||
|- |
|||
|'track' |
|||
|'mo:Track' |
|||
|- |
|||
|'medium' |
|||
|'mo:Medium' (and mo:CD, mo:SACD etc depending on format column) |
|||
|- |
|||
|rowspan="3"|objects |
|||
(no URI?) |
|||
|- |
|||
|'tracklist' |
|||
|absorbed into mo:SignalGroup |
|||
|- |
|||
|'artist_alias' |
|||
| 'http://ontologi.es/persona#Persona' |
|||
|- |
|||
|'artist_credit' |
|||
|collapse into foaf:maker relations. Also want to point to a sequence of artists, similar to http://purl.org/ontology/bibo/authorList |
|||
|} |
|||
==Advanced Relationship mappings== |
==Advanced Relationship mappings== |
Revision as of 09:17, 3 August 2010
This page is for discussing mapping of Next Generation Schema and Advanced Relationships to RDF.
NGS at a glance
The following objects exist in the Next Generation Schema. Here we make a clear distinction between core entities which have a unique MBID, entities which share an MBID with some core entity and perhaps other entities, and objects which are not associated with an MBID directly.
core entities that have mbids:
entities that share/borrow mbids:
just objects:
MO Mappings
mappings to the Music Ontology can be collected here. jump in and have your say :-)
proposal 0
type | NGS | RDF |
---|---|---|
core entities
with mbids | ||
'artist' | 'mo:MusicArtist' | |
'release' | 'mo:Release' | |
'release_group' | 'mo:SignalGroup' | |
'recording' | 'mo:Signal' | |
'label' | 'mo:Label' | |
'work' | 'mo:MusicalWork' | |
entities
with a URI (potentially) | ||
'url' | 'foaf:Document' | |
'track' | 'mo:Track' or 'mo:Signal' | |
'medium' | 'mo:Record' | |
objects
(no URI?) | ||
'tracklist' | absorbed into mo:SignalGroup | |
'artist_credit' | collapse into foaf:maker relations |
some notes:
- a medium is part of a release but does not have its own mbid - what should be the URI for a medium? perhaps some hash on the end of the release URI?
- in NGS a track simply redirects to a recording and associates a recording to a release - do we use mo:Track or mo:Signal for a track
- tracklist and artist_credit objects are described (completely?) by properties attached to various concepts (e.g. mo:SignalGroup and mo:Signal) and require no URIs for themselves
- what property associates a mo:SignalGroup (release_group) to a mo:Release (release)???
proposal 1 (dataincubator)
These are the mapping I have worked on as part of my http://musicbrainz.dataincubator.org// conversion
type | NGS | RDF |
---|---|---|
core entities
with mbids | ||
'artist' | 'mo:MusicArtist' (type=1' => mo:SoloMusicArtist, type=2 => mo:MusicGroup) | |
'release' | 'mo:Release' and 'mo:ReleaseEvent' (1:1 mapping) | |
'release_group' | 'mo:SignalGroup' | |
'recording' | 'mo:Signal' | |
'label' | 'mo:Label' | |
'work' | 'mo:MusicalWork' | |
entities
with a URI (potentially) | ||
'url' | untyped, I parse wikipedia links to create owl:sameAs to dbpedia, and discogs links for owl:sameAs to discogs.dataincubator.org | |
'track' | 'mo:Track' | |
'medium' | 'mo:Medium' (and mo:CD, mo:SACD etc depending on format column) | |
objects
(no URI?) | ||
'tracklist' | absorbed into mo:SignalGroup | |
'artist_alias' | 'http://ontologi.es/persona#Persona' | |
'artist_credit' | collapse into foaf:maker relations. Also want to point to a sequence of artists, similar to http://purl.org/ontology/bibo/authorList |
Advanced Relationship mappings
Mapping Advanced Relationships to RDF could be done using the MuSim ontology.
A link_type becomes and sim:AssociationMethod and each link becomes a sim:Association...