LinkedBrainz/NGS to RDF mappings: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
Line 71: Line 71:


some issues:
some issues:
* a medium is part of a release but does not have its own mbid - what should be the URI for a medium?
* 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
* 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

Revision as of 14:17, 2 August 2010

This page is for discussing mapping of Next Generation Schema and Advanced Relationships to RDF.

NGS Objects

The following objects exist in the Next Generation Schema:

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 :-)

proposed mappings to mo - kurtjx
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
'tracklist' absorbed into mo:SignalGroup
'artist_credit' collapse into foaf:maker relations

some issues:

  • 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