LinkedBrainz/NGS to RDF mappings: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
Line 46: Line 46:
|'mo:MusicalWork'
|'mo:MusicalWork'
|-
|-
|rowspan="2"|entities
|rowspan="4"|entities
|-
|-
|'url'
|'url'
|'foaf:Document'
|'foaf:Document'
|-
|'track'
|'mo:Track'?
|-
|-
|'medium'
|'medium'
|'mo:Record'
|'mo:Record'
|-
|rowspan="3"|objects
|-
|-
|'tracklist'
|'tracklist'

Revision as of 14:07, 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
'artist' 'mo:MusicArtist'
'release' 'mo:Release'
'release_group' 'mo:SignalGroup'
'recording' 'mo:Signal'
'label' 'mo:Label'
'work' 'mo:MusicalWork'
entities
'url' 'foaf:Document'
'track' 'mo:Track'?
'medium' 'mo:Record'
objects
'tracklist' absorbed into mo:SignalGroup
'artist_credit' collapse into foaf:maker relations?