@prefix dc: .
@prefix rdf: .
@prefix rdfs: .
@prefix mo: .
@prefix foaf: .
@prefix bach: .
@prefix mu: .
@prefix time: .
@prefix event: .
# Compatibility Layer between:
# http://purl.org/ontology/mo/
# and
# http://purl.org/NET/c4dm/music.owl#
#
# NOTE:
# Things to remove/discuss:
# * mo:composer --> dc:creator
# * mo:MusicalGroup --> foaf:Group (a Group is implicitly a MusicalGroup if it is involved in something related to music)
# * mo:title --> dc:title
# * all the stuff that are related to the *process* leading to a MusicalExpression
# --> engineer, recording studio, produced, producer, publisher (btw, there is already a dc:publisher)
# MusicalExpression - only the actual expression!
mu:Score rdfs:subClassOf mo:MusicalExpression. #Here I talk about the product of an arrangement, not the actual "published" score
mu:Sound rdfs:subClassOf mo:MusicalExpression.
mu:Signal rdfs:subClassOf mo:MusicalExpression.
# MusicalManifestation
mo:Album a mo:MusicalManifestation.
mo:Track a mo:MusicalManifestation.
mo:PublishedScore a mo:MusicalManifestation.
mo:has_track a rdf:Property;
rdfs:domain mo:Album;
rdfs:range mo:Track;
.
# Link between MusicalWork/Expression and Manifestation:
#
# I am not sure about including MusicalWork in the domain here
# but I think that it might be useful, as some times, a work can't
# really be decorrelated from its expression (see the Bach example)
# basically replaces the "records" property
mo:hasMusicalManifestation a rdf:Property;
rdfs:domain mo:MusicalWork;
rdfs:domain mo:MusicalExpression;
rdfs:range mo:MusicalManifestation.