LinkedBrainz/NGS to RDF mappings

From MusicBrainz Wiki
Jump to navigationJump to search

This page is for defining the mapping of Next Generation Schema and Advanced Relationships to RDF. Much of the old content has been moved to the talk page.

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:

Mappings

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.

Core

core NGS mappings to RDF
type NGS RDF
core entities

with mbids

'artist' 'mo:MusicArtist' (type=1 => 'mo:SoloMusicArtist', type=2 => 'mo:MusicGroup')
'release' 'mo:Release'
'release_group' 'mo:SignalGroup'
'recording' 'mo:Signal'
'label' 'mo:Label'
'work' 'mo:MusicalWork'
entities

with a URI

(potentially)

'url' 'foaf:Document' or 'owl:sameAs' links to DBpedia etc.
'track' 'mo:Track' as a blank node
'medium' 'mo:Medium' and various 'mfo' concepts
objects

(no URI?)

'tracklist' both a 'mo:Medium' (or mfo subclass) and 'mo:Record'?
'artist_credit' collapse into foaf:maker relations

Advanced Relationships

Currently, only the some of the most basic Advanced Relationships are modeled.