I have just started learning about ontologies and am a bit confused as to how to go about implementing actual applications that utilize the music ontology and the Similarity ontology in order to find musical similarities between users. I'm collecting user's music likes (in the form of the artist's/band's name). Here is where it gets a bit fuzzy. Is the next next to create an RDF file for each artist/band stating their genre and similar artists/bands and then through the Jena API (I would like to code in Java if possible) query the knowledge base, meaning that if I enter a user's music preferences I would be able to output users with similar musical preferences.
to model a user's music preferences you could utilise the Cognitive Characteristics Ontology (CCO) [1] as well. There is also an example that deals with music preferences in the documentation of CCO, see [2].
If have all your required knowledge in your knowledge base you could write SPARQL queries to get what you need (similarities between users). You'll maybe even do not need the Similarity Ontology at the beginning. This might be a further enhanced of your similarity algorithm. You could utilise it for modelling similarities between music artists, or songs, ...
> I have just started learning about ontologies and am a bit confused as
> to how to go about implementing actual applications that utilize the
> music ontology and the Similarity ontology in order to find musical
> similarities between users. I'm collecting user's music likes (in the
> form of the artist's/band's name). Here is where it gets a bit fuzzy.
> Is the next next to create an RDF file for each artist/band stating
> their genre and similar artists/bands and then through the Jena API (I
> would like to code in Java if possible) query the knowledge base,
> meaning that if I enter a user's music preferences I would be able to
> output users with similar musical preferences.
> to model a user's music preferences you could utilise the Cognitive
> Characteristics Ontology (CCO) [1] as well. There is also an example
> that deals with music preferences in the documentation of CCO, see [2].
> If have all your required knowledge in your knowledge base you could
> write SPARQL queries to get what you need (similarities between users).
> You'll maybe even do not need the Similarity Ontology at the beginning.
> This might be a further enhanced of your similarity algorithm. You could
> utilise it for modelling similarities between music artists, or songs, ...
Thank you so much for the quick reply! I'll be sure to check out all the examples and try to implement a basic user similarity knowledge base. Eventually I think I would like to you the Similarity Ontology since I would like to model similarities between artists in order to find deeper more meaningful similarities between users and not just whether they liked the same artist, but I can start with a more simple task.
> On 09/13/2012 09:51 AM, Bob Ferris wrote: > > Hi Naomi,
> > to model a user's music preferences you could utilise the Cognitive > > Characteristics Ontology (CCO) [1] as well. There is also an example > > that deals with music preferences in the documentation of CCO, see [2]. > > If have all your required knowledge in your knowledge base you could > > write SPARQL queries to get what you need (similarities between users). > > You'll maybe even do not need the Similarity Ontology at the beginning. > > This might be a further enhanced of your similarity algorithm. You could > > utilise it for modelling similarities between music artists, or songs, > ...
I have been playing around with the Characteristic Ontology and was able to combine it with the Similarity Ontology and Music Ontology as well. In the Music Ontology they have an example query for getting the name's of the artists similar to the given artist to at least 80%. Finding the names of the Artists similar to another Artist to at least 80%
14 ?similar_artist a mo:MusicArtist; 16 foaf:name ?similar_artist_name. 17 }
First of all, I'm a little confused about the working of this query. Should it return the artists that are at least 80% similar to the given artist? If this is what it should return, I'm confused about how it does so, since when I run the query on my rdf I just get back all the artists, no matter their level of similarity. How can I filter the result so it will only return those artists that have a similarity level of at least 0.8?
On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> Hello Everyone!
> I have just started learning about ontologies and am a bit confused as to > how to go about implementing actual applications that utilize the music > ontology and the Similarity ontology in order to find musical similarities > between users. I'm collecting user's music likes (in the form of the > artist's/band's name). Here is where it gets a bit fuzzy. > Is the next next to create an RDF file for each artist/band stating their > genre and similar artists/bands and then through the Jena API (I would like > to code in Java if possible) query the knowledge base, meaning that if I > enter a user's music preferences I would be able to output users with > similar musical preferences.
this is more a generic SPARQL question rather than a Music Ontology related question. Anyway, I'll give you a hint ;)
You should utilise the FILTER clause [2] of SPARQL to reduce your result set to artists that have a similarity level of 80%+
This looks like that you have to insert a
FILTER (?level > 0.8)
near the end of your query.
Cheers,
Bo
PS: btw, as source for music artist information you could leverage e.g. MusicBrainz (includes RDFa in their sites), DBPedia (a partial enhanced RDF mapping of Wikipedia), or you write an RDF wrapper for the Echo Nest API
> I have been playing around with the Characteristic Ontology and was able
> to combine it with the Similarity Ontology and Music Ontology as well.
> In the Music Ontology they have an example query for getting the name's
> of the artists similar to the given artist to at least 80%.
> Finding the names of the Artists similar to another Artist to at least 80%
> First of all, I'm a little confused about the working of this query.
> Should it return the artists that are at least 80% similar to the given
> artist?
> If this is what it should return, I'm confused about how it does so,
> since when I run the query on my rdf I just get back all the artists, no
> matter their level of similarity.
> How can I filter the result so it will only return those artists that
> have a similarity level of at least 0.8?
> Thanks in advance,
> Naomi
> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> Hello Everyone!
> I have just started learning about ontologies and am a bit confused
> as to how to go about implementing actual applications that utilize
> the music ontology and the Similarity ontology in order to find
> musical similarities between users. I'm collecting user's music
> likes (in the form of the artist's/band's name). Here is where it
> gets a bit fuzzy.
> Is the next next to create an RDF file for each artist/band stating
> their genre and similar artists/bands and then through the Jena API
> (I would like to code in Java if possible) query the knowledge base,
> meaning that if I enter a user's music preferences I would be able
> to output users with similar musical preferences.
On Fri, Sep 14, 2012 at 4:14 AM, Bob Ferris <z...@smiy.org> wrote:
> Hi Naomi,
> this is more a generic SPARQL question rather than a Music Ontology related
> question. Anyway, I'll give you a hint ;)
> You should utilise the FILTER clause [2] of SPARQL to reduce your result set
> to artists that have a similarity level of 80%+
> This looks like that you have to insert a
> FILTER (?level > 0.8)
> near the end of your query.
> Cheers,
> Bo
> PS: btw, as source for music artist information you could leverage e.g.
> MusicBrainz (includes RDFa in their sites), DBPedia (a partial enhanced RDF
> mapping of Wikipedia), or you write an RDF wrapper for the Echo Nest API
>> I have been playing around with the Characteristic Ontology and was able
>> to combine it with the Similarity Ontology and Music Ontology as well.
>> In the Music Ontology they have an example query for getting the name's
>> of the artists similar to the given artist to at least 80%.
>> Finding the names of the Artists similar to another Artist to at least
>> 80%
>> First of all, I'm a little confused about the working of this query.
>> Should it return the artists that are at least 80% similar to the given
>> artist?
>> If this is what it should return, I'm confused about how it does so,
>> since when I run the query on my rdf I just get back all the artists, no
>> matter their level of similarity.
>> How can I filter the result so it will only return those artists that
>> have a similarity level of at least 0.8?
>> Thanks in advance,
>> Naomi
>> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>> Hello Everyone!
>> I have just started learning about ontologies and am a bit confused
>> as to how to go about implementing actual applications that utilize
>> the music ontology and the Similarity ontology in order to find
>> musical similarities between users. I'm collecting user's music
>> likes (in the form of the artist's/band's name). Here is where it
>> gets a bit fuzzy.
>> Is the next next to create an RDF file for each artist/band stating
>> their genre and similar artists/bands and then through the Jena API
>> (I would like to code in Java if possible) query the knowledge base,
>> meaning that if I enter a user's music preferences I would be able
>> to output users with similar musical preferences.
>> Thanks in advance,
>> Naomi
> --
> 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-specification-group@googlegroups.com.
> To unsubscribe from this group, send email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/music-ontology-specification-group?hl=en.
Thank you both for the reply, I think I need to review SPARQL a bit more :) I don't really know how I cam across the similarity ontology that I was using, but http://purl.org/ontology/similarity/ seems well documented so I'll use that one!
On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> Hello Everyone!
> I have just started learning about ontologies and am a bit confused as to > how to go about implementing actual applications that utilize the music > ontology and the Similarity ontology in order to find musical similarities > between users. I'm collecting user's music likes (in the form of the > artist's/band's name). Here is where it gets a bit fuzzy. > Is the next next to create an RDF file for each artist/band stating their > genre and similar artists/bands and then through the Jena API (I would like > to code in Java if possible) query the knowledge base, meaning that if I > enter a user's music preferences I would be able to output users with > similar musical preferences.
On Fri, Sep 14, 2012 at 12:12 PM, nomush <naomiya...@gmail.com> wrote:
> Thank you both for the reply, I think I need to review SPARQL a bit more :)
> I don't really know how I cam across the similarity ontology that I was
> using, but http://purl.org/ontology/similarity/ seems well documented so
> I'll use that one!
> Thanks again,
> Naomi
> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>> Hello Everyone!
>> I have just started learning about ontologies and am a bit confused as to
>> how to go about implementing actual applications that utilize the music
>> ontology and the Similarity ontology in order to find musical similarities
>> between users. I'm collecting user's music likes (in the form of the
>> artist's/band's name). Here is where it gets a bit fuzzy.
>> Is the next next to create an RDF file for each artist/band stating their
>> genre and similar artists/bands and then through the Jena API (I would like
>> to code in Java if possible) query the knowledge base, meaning that if I
>> enter a user's music preferences I would be able to output users with
>> similar musical preferences.
> To post to this group, send email to
> music-ontology-specification-group@googlegroups.com.
> To unsubscribe from this group, send email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/music-ontology-specification-group?hl=en.
> I've not been working much in the world of RDF lately, but would be > happy to help if i can.
> On Fri, Sep 14, 2012 at 12:12 PM, nomush <naomi...@gmail.com <javascript:>> > wrote: > > Thank you both for the reply, I think I need to review SPARQL a bit more > :) > > I don't really know how I cam across the similarity ontology that I was > > using, but http://purl.org/ontology/similarity/ seems well documented > so > > I'll use that one!
> > Thanks again, > > Naomi
> > On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> >> Hello Everyone!
> >> I have just started learning about ontologies and am a bit confused as > to > >> how to go about implementing actual applications that utilize the music > >> ontology and the Similarity ontology in order to find musical > similarities > >> between users. I'm collecting user's music likes (in the form of the > >> artist's/band's name). Here is where it gets a bit fuzzy. > >> Is the next next to create an RDF file for each artist/band stating > their > >> genre and similar artists/bands and then through the Jena API (I would > like > >> to code in Java if possible) query the knowledge base, meaning that if > I > >> enter a user's music preferences I would be able to output users with > >> similar musical preferences.
> >> Thanks in advance, > >> Naomi
> > -- > > You received this message because you are subscribed to the Google > Groups > > "Music Ontology Specification Group" group. > > To view this discussion on the web visit
> > To post to this group, send email to > > music-ontology-specification-group@googlegroups.com <javascript:>. > > To unsubscribe from this group, send email to > > music-ontology-specification-group+unsubscribe@googlegroups.com<javascript: >.
Using the Similarity Ontology sort-of deprecates using mo:similar_to.
You just don't need that property. Your similarity relation becomes a
"thing". So using n3 notation:
In most implementations, you'd want :mysim to actually be a blank node
- triple stores tend to store these most efficiently and you would
have no cause to refer to :mysim by name - you'll only refer to it in
terms of it's elements. And then the real strength of this approach
is you can bind additional metadata to the similarity (e.g. what was
used to infer the similarity).
Hopefully this helps. Now the real trick will be filling in your
similarities and their weights :)
>> I've not been working much in the world of RDF lately, but would be
>> happy to help if i can.
>> On Fri, Sep 14, 2012 at 12:12 PM, nomush <naomi...@gmail.com> wrote:
>> > Thank you both for the reply, I think I need to review SPARQL a bit more
>> > :)
>> > I don't really know how I cam across the similarity ontology that I was
>> > using, but http://purl.org/ontology/similarity/ seems well documented so
>> > I'll use that one!
>> > Thanks again,
>> > Naomi
>> > On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>> >> Hello Everyone!
>> >> I have just started learning about ontologies and am a bit confused as
>> >> to
>> >> how to go about implementing actual applications that utilize the music
>> >> ontology and the Similarity ontology in order to find musical
>> >> similarities
>> >> between users. I'm collecting user's music likes (in the form of the
>> >> artist's/band's name). Here is where it gets a bit fuzzy.
>> >> Is the next next to create an RDF file for each artist/band stating
>> >> their
>> >> genre and similar artists/bands and then through the Jena API (I would
>> >> like
>> >> to code in Java if possible) query the knowledge base, meaning that if
>> >> I
>> >> enter a user's music preferences I would be able to output users with
>> >> similar musical preferences.
>> >> Thanks in advance,
>> >> Naomi
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Music Ontology Specification Group" group.
>> > To view this discussion on the web visit
>> > To post to this group, send email to
>> > music-ontology-specification-group@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > music-ontology-specification-group+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/music-ontology-specification-group?hl=en.
> To post to this group, send email to
> music-ontology-specification-group@googlegroups.com.
> To unsubscribe from this group, send email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/music-ontology-specification-group?hl=en.
On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> Hello Everyone!
> I have just started learning about ontologies and am a bit confused as to > how to go about implementing actual applications that utilize the music > ontology and the Similarity ontology in order to find musical similarities > between users. I'm collecting user's music likes (in the form of the > artist's/band's name). Here is where it gets a bit fuzzy. > Is the next next to create an RDF file for each artist/band stating their > genre and similar artists/bands and then through the Jena API (I would like > to code in Java if possible) query the knowledge base, meaning that if I > enter a user's music preferences I would be able to output users with > similar musical preferences.
I have a few questions. For the similarity, should I have an rdf:about= the similarity link from the last.fm wrapper? Or am I just complicating things too much?
While music brainz looks like a great database, I think I'm getting to caught up in all the data available, since I only have the artists' names and not their mbid.
I tried querying it using n3 format, however I keep getting errors from the jean api, since I don't think it can handle parsing those formats, so I'm stuck using rdf/xml.
On Friday, September 14, 2012 12:27:11 PM UTC-7, nomush wrote:
> Thanks that actually helped a lot!
> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>> Hello Everyone!
>> I have just started learning about ontologies and am a bit confused as to >> how to go about implementing actual applications that utilize the music >> ontology and the Similarity ontology in order to find musical similarities >> between users. I'm collecting user's music likes (in the form of the >> artist's/band's name). Here is where it gets a bit fuzzy. >> Is the next next to create an RDF file for each artist/band stating their >> genre and similar artists/bands and then through the Jena API (I would like >> to code in Java if possible) query the knowledge base, meaning that if I >> enter a user's music preferences I would be able to output users with >> similar musical preferences.
I would really invest the effort to learn and work in N3 - this is
really the "zen" syntax of RDF. If you have valid N3, Jena will
definitely swallow it happily enough. What I posted in my email was
"pseudo n3" and not valid.
> I have a few questions. For the similarity, should I have an rdf:about= the
> similarity link from the last.fm wrapper? Or am I just complicating things
> too much?
> While music brainz looks like a great database, I think I'm getting to
> caught up in all the data available, since I only have the artists' names
> and not their mbid.
> I tried querying it using n3 format, however I keep getting errors from the
> jean api, since I don't think it can handle parsing those formats, so I'm
> stuck using rdf/xml.
> Naomi
> On Friday, September 14, 2012 12:27:11 PM UTC-7, nomush wrote:
>> Thanks that actually helped a lot!
>> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>>> Hello Everyone!
>>> I have just started learning about ontologies and am a bit confused as to
>>> how to go about implementing actual applications that utilize the music
>>> ontology and the Similarity ontology in order to find musical similarities
>>> between users. I'm collecting user's music likes (in the form of the
>>> artist's/band's name). Here is where it gets a bit fuzzy.
>>> Is the next next to create an RDF file for each artist/band stating their
>>> genre and similar artists/bands and then through the Jena API (I would like
>>> to code in Java if possible) query the knowledge base, meaning that if I
>>> enter a user's music preferences I would be able to output users with
>>> similar musical preferences.
> To post to this group, send email to
> music-ontology-specification-group@googlegroups.com.
> To unsubscribe from this group, send email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/music-ontology-specification-group?hl=en.
> I would really invest the effort to learn and work in N3 - this is
> really the "zen" syntax of RDF. If you have valid N3, Jena will
> definitely swallow it happily enough. What I posted in my email was
> "pseudo n3" and not valid.
> Hope this helps!
> -kurt
> On Fri, Sep 14, 2012 at 6:04 PM, nomush <naomiya...@gmail.com> wrote:
>> Hello again,
>> I have tried using the similarity query, however, I never get any
>> information back. I'm assuming this is due to my rdf file.
>> Here it is:
>> I have a few questions. For the similarity, should I have an rdf:about= the
>> similarity link from the last.fm wrapper? Or am I just complicating things
>> too much?
>> While music brainz looks like a great database, I think I'm getting to
>> caught up in all the data available, since I only have the artists' names
>> and not their mbid.
>> I tried querying it using n3 format, however I keep getting errors from the
>> jean api, since I don't think it can handle parsing those formats, so I'm
>> stuck using rdf/xml.
>> Naomi
>> On Friday, September 14, 2012 12:27:11 PM UTC-7, nomush wrote:
>>> Thanks that actually helped a lot!
>>> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>>>> Hello Everyone!
>>>> I have just started learning about ontologies and am a bit confused as to
>>>> how to go about implementing actual applications that utilize the music
>>>> ontology and the Similarity ontology in order to find musical similarities
>>>> between users. I'm collecting user's music likes (in the form of the
>>>> artist's/band's name). Here is where it gets a bit fuzzy.
>>>> Is the next next to create an RDF file for each artist/band stating their
>>>> genre and similar artists/bands and then through the Jena API (I would like
>>>> to code in Java if possible) query the knowledge base, meaning that if I
>>>> enter a user's music preferences I would be able to output users with
>>>> similar musical preferences.
>> To post to this group, send email to
>> music-ontology-specification-group@googlegroups.com.
>> To unsubscribe from this group, send email to
>> music-ontology-specification-group+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/music-ontology-specification-group?hl=en.
That validator is extremely helpful :) thanks! Since the rdf file changed from the previous format, the sparql query above will need to change to the following: PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX mo: <http://purl.org/ontology/mo/> PREFIX sim: <http://purl.org/ontology/similarity/> SELECT DISTINCT ?level ?artist_name ?similar_artist_name WHERE { ?blank a sim:Similarity; sim:element ?one; sim:element ?two; sim:weight ?level . ?one a mo:MusicArtist; foaf:name ?artist_name . ?two a mo:MusicArtist; foaf:name ?similar_artist_name .
};
However, nothing is returned... is there by any chance a sparql query validator?! haha
On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> Hello Everyone!
> I have just started learning about ontologies and am a bit confused as to > how to go about implementing actual applications that utilize the music > ontology and the Similarity ontology in order to find musical similarities > between users. I'm collecting user's music likes (in the form of the > artist's/band's name). Here is where it gets a bit fuzzy. > Is the next next to create an RDF file for each artist/band stating their > genre and similar artists/bands and then through the Jena API (I would like > to code in Java if possible) query the knowledge base, meaning that if I > enter a user's music preferences I would be able to output users with > similar musical preferences.
On Fri, Sep 14, 2012 at 8:10 PM, nomush <naomiya...@gmail.com> wrote:
> Hi Kurt,
> That validator is extremely helpful :) thanks! Since the rdf file changed
> from the previous format, the sparql query above will need to change to the
> following:
> PREFIX foaf: <http://xmlns.com/foaf/0.1/>
> PREFIX mo: <http://purl.org/ontology/mo/>
> PREFIX sim: <http://purl.org/ontology/similarity/>
> SELECT DISTINCT ?level ?artist_name ?similar_artist_name
> WHERE {
> ?blank a sim:Similarity;
> sim:element ?one;
> sim:element ?two;
> sim:weight ?level .
> ?one a mo:MusicArtist;
> foaf:name ?artist_name .
> ?two a mo:MusicArtist;
> foaf:name ?similar_artist_name .
> };
> However, nothing is returned...
> is there by any chance a sparql query validator?! haha
> On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
>> Hello Everyone!
>> I have just started learning about ontologies and am a bit confused as to
>> how to go about implementing actual applications that utilize the music
>> ontology and the Similarity ontology in order to find musical similarities
>> between users. I'm collecting user's music likes (in the form of the
>> artist's/band's name). Here is where it gets a bit fuzzy.
>> Is the next next to create an RDF file for each artist/band stating their
>> genre and similar artists/bands and then through the Jena API (I would like
>> to code in Java if possible) query the knowledge base, meaning that if I
>> enter a user's music preferences I would be able to output users with
>> similar musical preferences.
> To post to this group, send email to
> music-ontology-specification-group@googlegroups.com.
> To unsubscribe from this group, send email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/music-ontology-specification-group?hl=en.
> and see if that at least works. can you dump the N3 you've input to > pastebin?
> On Fri, Sep 14, 2012 at 8:10 PM, nomush <naomi...@gmail.com <javascript:>> > wrote: > > Hi Kurt,
> > That validator is extremely helpful :) thanks! Since the rdf file > changed > > from the previous format, the sparql query above will need to change to > the > > following: > > PREFIX foaf: <http://xmlns.com/foaf/0.1/> > > PREFIX mo: <http://purl.org/ontology/mo/> > > PREFIX sim: <http://purl.org/ontology/similarity/> > > SELECT DISTINCT ?level ?artist_name ?similar_artist_name > > WHERE { > > ?blank a sim:Similarity; > > sim:element ?one; > > sim:element ?two; > > sim:weight ?level . > > ?one a mo:MusicArtist; > > foaf:name ?artist_name . > > ?two a mo:MusicArtist; > > foaf:name ?similar_artist_name . > > }; > > However, nothing is returned... > > is there by any chance a sparql query validator?! haha
> > On Wednesday, September 12, 2012 10:39:41 PM UTC-7, nomush wrote:
> >> Hello Everyone!
> >> I have just started learning about ontologies and am a bit confused as > to > >> how to go about implementing actual applications that utilize the music > >> ontology and the Similarity ontology in order to find musical > similarities > >> between users. I'm collecting user's music likes (in the form of the > >> artist's/band's name). Here is where it gets a bit fuzzy. > >> Is the next next to create an RDF file for each artist/band stating > their > >> genre and similar artists/bands and then through the Jena API (I would > like > >> to code in Java if possible) query the knowledge base, meaning that if > I > >> enter a user's music preferences I would be able to output users with > >> similar musical preferences.
> >> Thanks in advance, > >> Naomi
> > -- > > You received this message because you are subscribed to the Google > Groups > > "Music Ontology Specification Group" group. > > To view this discussion on the web visit
> > To post to this group, send email to > > music-ontology-specification-group@googlegroups.com <javascript:>. > > To unsubscribe from this group, send email to > > music-ontology-specification-group+unsubscribe@googlegroups.com<javascript: >.
