LinkedBrainz/NGS to RDF mappings
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:
The current mapping decisions for mapping NGS to RDF are summarized here. The mappings make use of the Music Ontology and other ontologies. Previous mapping proposals have been moved to the discussion page.
|'artist'||'mo:MusicArtist' (type=1 => 'mo:SoloMusicArtist', type=2 => 'mo:MusicGroup')|
|'release'||'mo:Release' and 'mo:ReleaseEvent' (currently 1:1 relations)|
with a URI
|'url'||'rdfs:seeAlso' or 'owl:sameAs' links to DBpedia etc.|
|'track'||'mo:Track' with a URI that includes the track.id|
|'medium'||'mo:Record' with a URI that includes the medium.id and various 'mt' instances (related via the mo:media_type property)|
|'tracklist'||'mo:Record' (tracklist currently are not treated separately, parts of this table are mapped to property values of the related mo:Record instances)|
|'artist_credit'||collapse into foaf:maker relations|
Currently, only the some of the most basic Advanced Relationships are modeled.
- 'has a Wikipedia page at' creates 'owl:sameAs' link to corresponding DBpedia resource
- 'has BBC Music Page at' creates 'owl:sameAs' to BBC Music
- currently (2011/07/29) all link types that relate to common web information services are at least implemented and the URLs are associated with its specific information service instance (see also here)
URIs - Thing v Page
In the Linked Data paradigm, it is important to make a distinction between the thing and the page describing that thing. Both the thing and the page should have their own URI. Think of this simple example to understand why - you might want to say "The page about James Brown was created on this date in 1998" - if James Brown and the page about James Brown shared the same URI, we would think James Brown was created in 1998 (which is false).
To mitigate this problem we used the hash URI approach. For example the URI for the page about James Brown would be:
While the URI for James Brown himself includes a hash suffix simply with an underscore character:
Now we can unambiguously make statements about James Brown and statements about the the page about James Brown. Other core entities follow this same pattern.