Class Schemas
From Music Ontology Wiki
Introduction to Class Schemas
Basic Ontologies
event:Event overview
A basic event:Event can make use of up to six basic properties:
- event:place,
- weight loss pills for women
- event:time,
- event:agent,
- event:factor,
- event:product and
- event:sub_event.
- spy equipment
Note: Please also have look into the definition of the Event Ontology for this concept.
timeline:TimeLine overview
Note: Please also have look into the definition of the Timeline Ontology for this concept.
The 4 levels of the FRBR Ontology
To understand fireworks the Music Ontology it is somehow essential to marc manoff understand the portable stage architecture of vending machines 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.
The 4 levels of the Music Ontology
Especially on how to associate a mo:Signal instance to its mo:Track instance (mo:MusicalManifestation) - with mo:published_as and mo:encodes (over its related mo:Medium instances) - and mo:Medium (mo:MusicalItem) instances - with mo:available_as (for release related issues) or mo:item (for user related issues). To associate mo:Signal (mo:SignalGroup) instances to its related mo:Release (mo:MusicalManifestation) instances, please make use of the extended release concept.
mo:MusicalWork schema
mo:MusicalWork has its buy pistachios origin in frbr:Work and as a sub eye secrets class it has currently only mo:Movement.
mo:MusicalWork schema extended
- mo:MusicalWork,
- its subclass(es) (
- and its related events (
mo:Arrangement schema
mo:Arrangement and its sub classes
mo:MusicalExpression schema
mo:MusicalExpression and event:Event schemas
(based on MO version 1.X)
- mo:Expression,
- its subclasses (
- mo:Score,
- mo:Signal with
- mo:Lyrics,
- mo:Libretto) and windows 8
- event:Event and its related musical event sub classes
adipex diet pills buy adipex best diet pills buy phentermine online phentermine without prescription
mo:MusicalExpression schema and event relations (extended)
(based on MO 2.0)
- mo:Expression,
- its subclasses (
- and its related events (
buy backlinks
backlink services
The red arrow is from the owl:disjointWith property that means both signal types are disjoint to each other.
mo:MusicalManifestation schema
mo:MusicalManifestation schema (simple)
mo:MusicalManifestation has its origin in frbr:Manifestation and it has the following sub classes currently
mo:MusicalManifestation schema (extended)
- mo:MusicalManifestation has the following sub classes currently
- mo:PublishedLyrics,
- mo:PublishedLibretto,
- mo:PublishedScore,
- mo:Release (with its mo:record property),
- mo:Record (with its mo:track property) and
- mo:Track.
- One could especially make use of its related release properties
- mo:release_status,
- mo:release_type and
- mo:other_release_of (a mo:MusicalManifestation to mo:MusicalManifestation relation).
- The related event:Event for mo:MusicalManifestation is
- mo:ReleaseEvent (with its mo:release property to create release events from a mo:SignalGroup instance (see also the extended release concept)).
mo:MusicalItem schema
mo:MusicalItem schema (simple)
(based on Music Ontology version 1.X)
mo:MusicalItem had its origin in frbr:Item and only one direct sub class
- mo:Medium with its concrete sub classes
- mo:DAT,
- mo:DCC,
- mo:CD,
- mo:MD,
- mo:SACD,
- mo:Torrent,
- mo:ED2K,
- mo:Datapikay,
- mo:Vinyl,
- mo:MagneticTape,
- mo:Stream,
- mo:DVDA,
- mo:AudioFile.
mo:MusicalItem schema (extended)
(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:Medium with its concrete sub classes
beauty tips SeatonCorp beauty make-up windows 8 buy backlinks thomas meano backlink service best diet pills
mo:MusicalManifestation and mo:MusicalItem schema (partial)
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:MusicArtist, mo:MusicGroup, and mo:Organization schemas
mo:MusicArtist, mo:MusicGroup, and mo:Label schemas (simple)
(based on Music Ontology version 1.X)
This graphic illustrates the construction (origins) of the important musical concepts
- mo:MusicArtist and its sub class mo:SoloMusicArtist,
- mo:MusicGroup and
- mo:Label.
The overall concept is foaf:Agent with its sub classes
mo:CorporateBody is a more general concept to model instant performer musical corporated bodies, such as labels or concert agencies.
mo:MusicArtist, mo:MusicGroup, mo:Label and mo:Membership schemas (extended)
(based on Music Ontology version 2.0)
This graphic shows not only the construction (origins) of the important musical concepts
- mo:MusicArtist and its sub class mo:SoloMusicArtist,
- mo:MusicGroup with its releated mo:Membership event to model music group memberships (by using mo:membership and mo:group, or for simple (permanent) relations mo:member) and
- mo:Label,
it illustrates furthermore, the broad range of related roles during the music production and consumption process:
- mo:SoundEngineer,
- mo:Arranger (currently no link to the documentation available),
- mo:Composer,
- mo:Listener,
- mo:Conductor and
- mo:Performer (Note: currently these concepts are all linked to its seo India related property in the documentation, which can also be used with a more abstract foaf:Agent as range).
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 slimming pills corporated bodies, such as labels or concert agencies.
mo:ReleaseStatus schema
The mo:ReleaseStatus concept is for describing the current release status of a related mo:MusicalManifestation instance. Currently, in the Music Ontology the sexual enhancers following individuals are defined:
This list of mo:ReleaseStatus individuals might be extended in future penis enlargement pills Music Ontology releases or could also be extended by Key Environmental Inc self defined sub ontology definitions.
mo:ReleaseType schema
The mo:ReleaseType concept is for describing the release type of a related mo:MusicalManifestation instance. Currently, in the Music Ontology breast enlargements the following individuals are defined:
- mo:interview,
- mo:live,
- mo:spokenword,
- mo:ep,
- mo:remix,
- mo:compilation,
- mo:soundtrack,
- mo:album and
- mo:audiobook.
This list of mo:ReleaseType individuals might be extended in future Music volume pills Ontology releases or could also be extended by Travel Itineraries self defined sub ontology definitions.
Unstable class schemas
These schemas are unstable at the moment considering the work intivar we are currently doing for these two portions of the ontology.
Extended release concept with mo:ReleaseEvent
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 into the notes of Proposal Revision 1.14 for this concept. Search Engine Optimization Consultant Link Building Service Cheap Web Hosting Link Building Service Kinect game
Recording Session concept to capture Recordings
Each mo:Recording century 21 broker properti jual beli sewa rumah Indonesia 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 into
snoring relief
best snoring solution
the notes of Proposal Revision 1.14 for this concept.
