Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Music Ontology Specification Group
Home
+ new post
About this group
Join this group
Message from discussion You need it, you want it, you get it ;) - The Recommendation Ontology
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Alex  
View profile  
 More options Jul 31 2010, 1:12 pm
From: Alex <alexandre.pass...@deri.org>
Date: Sat, 31 Jul 2010 10:12:41 -0700 (PDT)
Local: Sat, Jul 31 2010 1:12 pm
Subject: Re: You need it, you want it, you get it ;) - The Recommendation Ontology
Print | View thread | Show original | Report this message | Find messages by this author
Hi,

On Jul 31, 1:08 pm, z...@elbklang.net wrote:

> Hello again,

> today I modelled a music recommendation[1,2] example with help of the
> Recommendation Ontology. Therefore, I also added new extensions to the
> ontology for testing purpose, these are:

> - rec:RankedRecommendation - a ranked recommendation that includes an
> ordered list of recommendations
> - rec:ranked_recommendation_object - a ranked recommendation object in a
> ranked recommendation

> Please let me know, what do you think about this modelling. With the  help
> of ranked recommendations one is able to create an order re. the
> recommendation object without getting into the details about the
> creation of this order.

In dbrec, I've modeled the LDSD ontology (that should be mapped
further with MuSim and now with this Recommendation Ontology, I'll
email the list about this later).
Instead of ranking the recommendations, each recommendation got a
particular score, so that I can use ORDER / OFFSET in SPARQL to order
the recommendations and limit them to a particular set.
I found that more appropriate than a ranked object, but I guess both
can be combined if needed.

Best,

Alex.

Hence, such a ranked recommendation is more or

> less on its highest level. However, one can also add some background
> information (see the sim:included_association relations), which are the
> hook to the details.
> Furthermore, this modelling should enable the comparison of different
> recommendations/ranked recommendation for someone/something.

> I'm currently a bit unsure, where I should include the subject of a
> recommendation, if it is a personalised recommendation. I thought that
> the user would be related by rec:recommendation (ex:AUser
> rec:recommendation ex:ARecommendation). However, the subject, e.g. seed
> tracks (objects) etc. must be related by included associations then, or?
> Another option would be to relate them directly by sim:subject, but  there
> is also the use case where a recommendation is based on an
> association statement as it is exemplified here[3]. This leads maybe to
> some inconsistency ;)

> Any suggestions? (Kurt? ;) )

> Cheers,

> Bob

> [1]http://smiy.sourceforge.net/rec/examples/N3/music_rec_-_example.n3[2]http://smiy.sourceforge.net/rec/examples/N3/music_rec_-_example.owl[3]http://purl.org/ontology/ao/associationontology.html#sec-example

> Am 30.07.2010 17:52, schrieb Bob Ferris:> Hello everybody,
> > today I like to announce a first draft of the Recommendation
> > Ontology[1,2,3]. As far as I get an overview, there exists currently no

> ontology, which address this purpose as I intended it.> With this ontology it should be possible to associate a recommendation

> to someone or something. The recommendation itself includes the> recommendation objects and a relation to the recommender, e.g. an

> is:InfoService instance. The association and/or similarity statements,
> which are describing the reasons for a recommendation, can be described
> on the basis of the sim:Association[4] concept, which can be related to
> a sim:association concept by the property ao:included_association[5].
> The aim of the Recommendation Ontology is to serve recommendations from
> different information services to users (or something) by having also
> the opportunity to describe the reasons for the recommendation and
> hence, enable transparency. A use case example, which follows the idea
> of transparency recommendations is dbrec.net[6].> Please let me know, what do you think about this modelling. Comments,

> critics and suggestions are very welcome.> Cheers,
> > Bob
> > [1]http://smiy.sourceforge.net/rec/rdf/recommendationontology.n3[2]

> http://smiy.sourceforge.net/rec/rdf/recommendationontology.owl[3]http://smiy.sourceforge.net/rec/gfx/rec_-_recommendation.gif[4]http://purl.org/ontology/similarity/Association> [5]
> >http://purl.org/ontology/ao/associationontology.html#included_associa...

> [6]http://dbrec.net/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google