LinkedBrainz/NGS to RDF mappings: Difference between revisions
(→Core) |
No edit summary |
||
Line 1: | Line 1: | ||
This page is for |
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:NGS_to_RDF_mappings|talk page]]. |
||
==NGS at a glance== |
==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. |
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. |
||
Line 72: | Line 73: | ||
|} |
|} |
||
==Advanced |
==Advanced Relationships== |
||
Mapping [[Advanced Relationships]] to RDF could be done using the [http://purl.org/ontology/similarity MuSim] ontology. |
Mapping [[Advanced Relationships]] to RDF could be done using the [http://purl.org/ontology/similarity MuSim] ontology. |
||
Revision as of 21:33, 16 September 2010
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
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
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 - this approach is probably best left for cleaning up "left-overs" that aren't readily covered by other vocabs - --Kurtjx 19:43, 16 August 2010 (UTC)
I have planned a mixed approach - direct property relationships where possible, augmented by event based entities that allow start/end information to be included. As a start I have a mapping for almost all the the link types in NGS to foaf, dc, mo and others. I have supplemented this with some custom properties in a http://musicbrainz.dataincubator.org/schema namespace. I could list them all here, but there are quite a lot! Iand 09:28, 3 August 2010 (UTC)
What about the Relationship Vocabulary? (by zazi)