Class Schemas

zazi edited this page Feb 7, 2012 · 12 revisions

1. Introduction to Class Schemas
1.1. Dereferencing
2. Stable class schemas
2.1. Basic Ontologies
2.1.1. event:Event overview
2.1.2. timeline:TimeLine overview
2.1.3. The 4 levels of the FRBR Ontology
2.2. The 4 levels of the Music Ontology
2.2.1. mo:MusicalWork schema
2.2.1.1. mo:MusicalWork schema extended
2.2.1.2. mo:Arrangement schema
2.2.2. mo:MusicalExpression schema
2.2.2.1. mo:MusicalExpression and event:Event schemas
2.2.2.2. mo:MusicalExpression schema and event relations (extended)
2.2.3. mo:MusicalManifestation schema
2.2.3.1. mo:MusicalManifestation schema (simple)
2.2.3.2. mo:MusicalManifestation schema (extended)
2.2.4. mo:MusicalItem schema
2.2.4.1. mo:MusicalItem schema (simple)
2.2.4.2. mo:MusicalItem schema (extended)
2.2.5. mo:MusicalManifestation and mo:MusicalItem schema (partial)
2.3. mo:MusicArtist, mo:MusicGroup, and mo:Organization schemas
2.3.1. mo:MusicArtist, mo:MusicGroup, and mo:Label schemas (simple)
2.3.2. mo:MusicArtist, mo:MusicGroup, mo:Label and mo:Membership schemas (extended)
2.4. mo:ReleaseStatus schema
2.5. mo:ReleaseType schema
3. Unstable class schemas
3.1. Extended release concept with mo:ReleaseEvent
3.2. Recording Session concept to capture Recordings

1. Introduction to Class Schemas

[top]

1.1. Dereferencing

[top]

All Classes and Properties are dereferenceable via their URI (in fact, more would have do be done with content-negotiation, etc.)

2. Stable class schemas

[top]

2.1. Basic Ontologies

[top]

2.1.1. event:Event overview

[top]

A basic event:Event can make use of up to six basic properties:

Note: Please also have look at the definition of the Event Ontology for this concept.

Event concept

2.1.2. timeline:TimeLine overview

[top]

Note: Please also have look at the definition of the Timeline Ontology for this concept.

Timeline concept

2.1.3. The 4 levels of the FRBR Ontology

[top]

To understand the Music Ontology it is somehow essential to understand its underlying ontology - the FRBR Ontology - with its 4 levels: frbr:Work, frbr:Expression, frbr:Manifestation, frbr:Item, where MO derives from on each level.
Note: To bypass the levels from the most abstract level to a lower level, please use the property frbr:subject, which has a range of frbr:Endeavour (the superclass of the 4 levels concept). This enables, for example, a bypass from a mo:MusicalWork instance to a mo:SignalGroup instance.

The red arrows are from the owl:disjointWith property that means each level of the 4 levels concept is disjoint to each other.

FRBR - 4 level concept

2.2. The 4 levels of the Music Ontology

[top]

A mo:Signal instance can be associated with mo:Track instances (mo:MusicalManifestation) by utilising mo:published_as and mo:encodes (over its related mo:Medium instances). A mo:Track instance (mo:MusicalManifestation) can be associated with mo:Medium (mo:MusicalItem) instances by utilising mo:available_as (for release related issues) or mo:item (for user related issues). To associate mo:Signal (mo:SignalGroup) instances with their related mo:Release (mo:MusicalManifestation) instances, please make use of the extended release concept.

MO - 4 level concept

2.2.1. mo:MusicalWork schema

[top]

mo:MusicalWork has its origin in frbr:Work and as a sub class it has currently only mo:Movement.

Musical Work concept

2.2.1.1. mo:MusicalWork schema extended

[top]

[![MO - Musical Work concept](https://github.com/motools/musicontology/raw/master/doc/wiki/images/Mo_-_musical_work.gif)](https://github.com/motools/musicontology/raw/master/doc/wiki/images/Mo_-_musical_work.gif)

2.2.1.2. mo:Arrangement schema

[top]

mo:Arrangement and its sub classes

Arrangement concept

2.2.2. mo:MusicalExpression schema

[top]

2.2.2.1. mo:MusicalExpression and event:Event schemas

[top]

(based on MO version 1.X)

MO - event concepts

2.2.2.2. mo:MusicalExpression schema and event relations (extended)

[top]

(based on MO 2.0)

*The red arrow is from the* [***owl:disjointWith***](http://www.w3.org/TR/2004/REC-owl-guide-20040210/#DisjointClasses) *property that means both signal types are disjoint to each other.*

MO - Musical Expression concept

2.2.3. mo:MusicalManifestation schema

[top]

2.2.3.1. mo:MusicalManifestation schema (simple)

[top]

mo:MusicalManifestation has its origin in frbr:Manifestation and it has the following sub classes currently

MO - Musical Manifestation concept

2.2.3.2. mo:MusicalManifestation schema (extended)

[top]

MO - Musical Manifestation concept extended

2.2.4. mo:MusicalItem schema

[top]

2.2.4.1. mo:MusicalItem schema (simple)

[top]

(based on Music Ontology version 1.X)

mo:MusicalItem had its origin in frbr:Item and only one direct sub class

MO - Musical Item concept

2.2.4.2. mo:MusicalItem schema (extended)

[top]

(based on Music Ontology version 2.0)

mo:MusicalItem isn't a sub class of frbr:Item anymore (see its description for details) and only one direct sub class

MO - Musical Item concept extended

2.2.5. mo:MusicalManifestation and mo:MusicalItem schema (partial)

[top]

This graphic is to illustrate a relation (mo:available_as as sub property of frbr:exemplar) between a mo:MusicalManifestation instance (e.g. mo:Release, mo:Record or mo:Track) and a mo:MusicalItem instance (e.g. mo:CD).

MO - Musical Item to Musical Manifestation concept relations

2.3. mo:MusicArtist, mo:MusicGroup, and mo:Organization schemas

[top]

2.3.1. mo:MusicArtist, mo:MusicGroup, and mo:Label schemas (simple)

[top]

(based on Music Ontology version 1.X)

This graphic illustrates the construction (origins) of the important musical concepts

The overall concept is foaf:Agent with its sub classes

mo:CorporateBody is a more general concept to model musical corporated bodies, such as labels or concert agencies.

MO - Agent concepts

2.3.2. mo:MusicArtist, mo:MusicGroup, mo:Label and mo:Membership schemas (extended)

[top]

(based on Music Ontology version 2.0)

This graphic shows not only the construction (origins) of the important musical concepts

The overall concept is foaf:Agent with its sub classes

foaf:Group and foaf:Organization are both sub classes of frbr:CorporateBody. mo:CorporateBody is a more general concept to model musical corporate bodies, such as labels or concert agencies.

MO - Musical Artist, Musical Group, Label, Membership concepts

2.4. mo:ReleaseStatus schema

[top]

The mo:ReleaseStatus concept is for describing the current release status of a related mo:MusicalManifestation instance. Currently, in the Music Ontology the following individuals are defined:

This list of mo:ReleaseStatus individuals might be extended in future Music Ontology releases or could also be extended by self defined sub ontology definitions.

Release Status concept

2.5. mo:ReleaseType schema

[top]

The mo:ReleaseType concept is for describing the release type of a related mo:MusicalManifestation instance. Currently, in the Music Ontology the following individuals are defined:

This list of mo:ReleaseType individuals might be extended in future Music Ontology releases or could also be extended by self defined sub ontology definitions.

Release Type concept

3. Unstable class schemas

[top]

These schemas are unstable at the moment considering the work we are currently doing for these two portions of the ontology.

3.1. Extended release concept with mo:ReleaseEvent

[top]

A mo:ReleaseEvent consumes often mo:SignalGroup or mo:Signal instances as event:factor. The event:product objects of such events are then often one or more mo:Release instance(s), which are related through the mo:release property (instead of the dropped mo:release_event from version 2.0). In other cases, e.g. releasing a mo:Score instance somewhere as a mo:PublishedScore instance, one has to use just the event:product property for the publishing relations.
Due to the fact that mo:ReleaseEvent is an event:Event, one can associate a place (event:place) and a time (event:time) to it. Furthermore, could a mo:Label be assigned with the property mo:label (this property has as domain mo:Release, since version 2.1).

Note: Please also have look at the notes of Proposal Revision 1.14 for this concept.

MO - Release Event concept

3.2. Recording Session concept to capture Recordings

[top]

Each mo:Recording instance of a mo:RecordingSession instance is connected to it with the property event:sub_event. Hence, the mo:RecordingSession instance is a composite of mo:Recording instances. The product (mo:produced_signal_group) of a mo:RecordingSession event is mo:SignalGroup instance, which can contain all procuded mo:Signal instances of that mo:RecordingSession instance.
Due to the fact that mo:RecordingSession is an event:Event, one can associate a place (event:place) and a time (event:time) to it.

Note: Please also have look at the notes of Proposal Revision 1.14 for this concept.

MO - Recording Session concept