How to model a music file with the music ontology
daniel.gerber
let me first explain what I want to do:
I'm currently building a small php framework which basically works
like this...
put a file in (any kind of multimedia) and get a rdf description of
the file out
right now I'm implementing the functionality for music files (m4a,mp3
etc...)
so, what I don't get from looking at the music ontology is, how should
I model a file which represents a track:
let's say for example I do have the file "The Beatles - Yellow
Submarine.m4a"
Would it then be correct to type this file as a mo:Track? Or should
this be a mo:AudioFile instead?
And if so, how is the connection to the mo:Track actually made?
What I was thinking is, that the file and the abstract concept of this
song (you can't actually see it) is the same.
It's just a different representation!?
What do you think?
Cheers,
Daniel
Bob Ferris
> Hi,
> let me first explain what I want to do:
>
> I'm currently building a small php framework which basically works
> like this...
>
> put a file in (any kind of multimedia) and get a rdf description of
> the file out
>
> right now I'm implementing the functionality for music files (m4a,mp3
> etc...)
>
> so, what I don't get from looking at the music ontology is, how should
> I model a file which represents a track:
>
> let's say for example I do have the file "The Beatles - Yellow
> Submarine.m4a"
>
> Would it then be correct to type this file as a mo:Track? Or should
> this be a mo:AudioFile instead?
> And if so, how is the connection to the mo:Track actually made?
>
Hi Daniel,
re. representing a concrete exemplar, then you are on the item level of
the 4 level of the FRBR Vocabulary, which are also applied in the Music
Ontology. You can model a song over these 4 levels. See also [1] for an
illustration of these relations in the Music Ontology, or [2] for an
example, which models a personal exemplar of a CD.
As you can see there, you can use mo:available_as and mo:item to create
a relation from the manifestation level (here mo:MusicalManifestation)
to the item level (here mo:MusicalItem). Furthermore, you can also
directly associate a mo:Signal instance - that means on the expression
level - from the item level by using the property mo:encodes.
> What I was thinking is, that the file and the abstract concept of this
> song (you can't actually see it) is the same.
Well, you see each level of abstraction as a part of the whole
description. However, it is not really the same. A mo:Track instance can
be related with several mo:MusicalItem instances. A mo:Signal instance
can be related with several mo:Track instances. A mo:MusicalWork
instance can be related with several mo:Signal instances.
It's more or less all about sharing some information on each level. If
one model this from the bottom, it seems at the beginning a bit
complicated and complex. However, in a distributed, shared Knowledge
Base, one will notice the advantages.
[1]
http://wiki.musicontology.com/index.php/Classes_Schemas#The_4_levels_of_the_Music_Ontology
[2] http://wiki.musicontology.com/index.php/Yet_another_basic_example
daniel.gerber
would this then be correct?
http://www.discogs.com/artist/Kate+Nash a mo:MusicArtist
foaf:name "Kate Nash"^^xsd:string
owl:sameAs http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314
http://www.discogs.com/Kate-Nash-Made-Of-Bricks/release/1104100 a
mo:Record
dc:title "Kate Nash"^^xsd:string
dc:creator http://www.discogs.com/artist/Kate+Nash
mo:releaseType mo:album; (Why is "album" in lower case?)
mo:has_track http://test.de/madeofbricks/foundations
http://test.de/madeofbricks/foundations a mo:track
dc:title "Foundations";
mo:trackNum "2";
mo:item "http://test.de/foundation.m4a"
http://test.de/foundation.m4a a mo:AudioFile
> [2]http://wiki.musicontology.com/index.php/Yet_another_basic_example
Bob Ferris
your example is almost correct. However, there are small changes since
the bit-out-of-date example and the currently Music Ontology revision.
Am 14.09.2010 10:48, schrieb daniel.gerber:
> thank you for the help.. so let me get this straight:
>
> would this then be correct?
>
> http://www.discogs.com/artist/Kate+Nash a mo:MusicArtist
> foaf:name "Kate Nash"^^xsd:string
> owl:sameAs http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314
>
> http://www.discogs.com/Kate-Nash-Made-Of-Bricks/release/1104100 a
> mo:Record
> dc:title "Kate Nash"^^xsd:string
> dc:creator http://www.discogs.com/artist/Kate+Nash
> mo:releaseType mo:album; (Why is "album" in lower case?)
-> is now mo:release_type (see [2])
- the lower case is probably because of mo:album is an instance of
mo:ReleaseType (see [3]); furthermore, it is planned to outsource the
release types to a separate namespace in the (near) future
> mo:has_track http://test.de/madeofbricks/foundations
-> is now mo:track (see [4])
>
> http://test.de/madeofbricks/foundations a mo:track
> dc:title "Foundations";
> mo:trackNum "2";
-> is now mo:track_number (see [1])
> mo:item "http://test.de/foundation.m4a"
>
> http://test.de/foundation.m4a a mo:AudioFile
Cheer,
Bob
[1] http://musicontology.com/#term_track_number
[2] http://musicontology.com/#term_release_type
[3] http://musicontology.com/#term_album
[4] http://musicontology.com/#term_track
Yves Raimond
On Tue, Sep 14, 2010 at 9:48 AM, daniel.gerber <ger...@googlemail.com> wrote:
> thank you for the help.. so let me get this straight:
>
> would this then be correct?
>
This looks good! Just a few inline comments:
> http://www.discogs.com/artist/Kate+Nash a mo:MusicArtist
> foaf:name "Kate Nash"^^xsd:string
> owl:sameAs http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314
>
One small comment:
http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314
is the BBC page about this artist, the actual artist URI is
http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314#artist
> http://www.discogs.com/Kate-Nash-Made-Of-Bricks/release/1104100 a
> mo:Record
> dc:title "Kate Nash"^^xsd:string
> dc:creator http://www.discogs.com/artist/Kate+Nash
> mo:releaseType mo:album; (Why is "album" in lower case?)
> mo:has_track http://test.de/madeofbricks/foundations
>
> http://test.de/madeofbricks/foundations a mo:track
> dc:title "Foundations";
> mo:trackNum "2";
> mo:item "http://test.de/foundation.m4a"
There is a slightly more specific property than mo:item in the Music
Ontology: mo:available_as. Also, mo:trackNum should be mo:track_number
(are there still some Wiki examples pointing to mo:trackNum?) and
mo:has_track should be mo:track (same thing, is that still mentioned
in the Wiki somewhere? We should change that if so).
Cheers,
y
> --
> You received this message because you are subscribed to the Google Groups "Music Ontology Specification Group" group.
> To post to this group, send email to music-ontology-sp...@googlegroups.com.
> To unsubscribe from this group, send email to music-ontology-specific...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/music-ontology-specification-group?hl=en.
>
>
daniel.gerber
from [1].
Thanks for the tip with "#artist", I think I heard that before but I
didn't found it in [2]. Maybe you should add this there..
By the way.. did you guys publish something on how you modeled the bbc
music page? (I'm writing my master thesis on multimedia management in
general, with respect to manage multimedia documents in OntoWiki [3])
[1] http://wiki.musicontology.com/index.php/Yet_another_basic_example
[2] http://www.bbc.co.uk/music/developers#api
[3] http://ontowiki.net/Projects/OntoWiki
> > thank you for the help.. so let me get this straight:
>
> > would this then be correct?
>
> This looks good! Just a few inline comments:
>
> > owl:sameAs http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314
>
> One small comment:http://www.bbc.co.uk/music/artists/49018fd2-95ef-4f7e-92bb-813159909314
>
> >http://www.discogs.com/Kate-Nash-Made-Of-Bricks/release/1104100a
> > dc:title "Kate Nash"^^xsd:string
> > dc:creator http://www.discogs.com/artist/Kate+Nash
> > mo:releaseType mo:album; (Why is "album" in lower case?)
> > mo:has_track http://test.de/madeofbricks/foundations
>
> > mo:trackNum "2";
> > mo:item "http://test.de/foundation.m4a"
>
> There is a slightly more specific property than mo:item in the Music
> Ontology: mo:available_as. Also, mo:trackNum should be mo:track_number
> (are there still some Wiki examples pointing to mo:trackNum?) and
> mo:has_track should be mo:track (same thing, is that still mentioned
> in the Wiki somewhere? We should change that if so).
>
> Cheers,
> y
>
>
>
>
>
Nicholas J Humfrey
There are a few blog posts on the BBC Radio Labs blog:
http://www.bbc.co.uk/blogs/radiolabs/2007/11/urls.shtml
http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml
They are more about the programmes website, but the same principles apply
to music.
I agree that a music specific blog post and one that describes how to make
use of the music RDF would be good...
nick.