Group Received: by 10.59.0.226 with SMTP id bb2mr524374ved.30.1347650525481; Fri, 14 Sep 2012 12:22:05 -0700 (PDT) X-BeenThere: music-ontology-specification-group@googlegroups.com Received: by 10.52.156.112 with SMTP id wd16ls50462vdb.6.gmail; Fri, 14 Sep 2012 12:22:05 -0700 (PDT) Received: by 10.52.70.78 with SMTP id k14mr26747vdu.7.1347650525101; Fri, 14 Sep 2012 12:22:05 -0700 (PDT) Received: by 10.52.70.78 with SMTP id k14mr26746vdu.7.1347650525091; Fri, 14 Sep 2012 12:22:05 -0700 (PDT) Return-Path: Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by gmr-mx.google.com with ESMTPS id r14si32307vdu.1.2012.09.14.12.22.05 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Sep 2012 12:22:05 -0700 (PDT) Received-SPF: pass (google.com: domain of kur...@gmail.com designates 209.85.212.44 as permitted sender) client-ip=209.85.212.44; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of kur...@gmail.com designates 209.85.212.44 as permitted sender) smtp.mail=kur...@gmail.com; dkim=pass header...@gmail.com Received: by mail-vb0-f44.google.com with SMTP id fc26so6226511vbb.3 for ; Fri, 14 Sep 2012 12:22:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ylUe74Kg4ICDbgM7zGkTDIopEir7YVGUijgimDfG9bw=; b=NHbVnmDd7ndx9BO9D8O4hFpT1FWk+EijnXRSrONytETl2qGJEJpR76jE6criFIDXzt +6wZLaJOtjin3MJMj9HBMxp/oMYlmkrubsuTTWQIpTvV1bLeb5D5uHT4hl70695rS2Qb yiYLpHqhGU2Rq0+DESPE6RR6pSRv6ZvlidnuDHk5OQDamEKfT/FjkWhN8PQkh5yyL3Hg WNrwUYv62Aamsd1sqQ3rrEfDyqqWDH/lUah6O1PHS4SuyPHLTydeXy1+uUp2cWbj0HgX VPvDG+fINVc57/5sRy7JnTjUVOTVdOe3tGrNio0IMrq7e6d6Pq8L0M0y4sJJF3IRfEEB DOOQ== MIME-Version: 1.0 Received: by 10.52.97.34 with SMTP id dx2mr107293vdb.10.1347650524955; Fri, 14 Sep 2012 12:22:04 -0700 (PDT) Received: by 10.58.181.202 with HTTP; Fri, 14 Sep 2012 12:22:04 -0700 (PDT) In-Reply-To: <25925983-7c27-4772-be96-157901cadd6f@googlegroups.com> References:

<25925983-7c27-4772-be96-157901cadd6f@googlegroups.com> Date: Fri, 14 Sep 2012 15:22:04 -0400 Message-ID: Subject: Re: Using The Music Ontology for Finding Similar Users From: Kurt J To: music-ontology-specification-group@googlegroups.com Content-Type: text/plain; charset=ISO-8859-1 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: :shakira a mo:MusicArtist; foaf:name "Shakira" . :beyonce a mo:MusicArtist; foaf:name "Beyonce". :mysim a sim:Similarity; sim:element :beyonce; sim:element :shakira; sim:weight "" . 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 :) -kurt On Fri, Sep 14, 2012 at 3:07 PM, nomush wrote: > Hi Kurt, > > A quick question about formatting the RDF file using both the music and > similarity ontology. > > I'm not sure how to make the connection between the property mo:similar_to > and the sim:similarity. > > I'm trying to say that Shakira is 0.9 similar to Beyonce. > > I have my MusicArtist object: > > rdf:about="http://zitgist.com/music/artist/bf24ca37-25f4-4e34-9aec-460b94364cfc" > > Shakira > > rdf:resource="http://zitgist.com/music/artist/f4d5cc07-3bc9-4836-9b15-88a08359bc63" > /> > > then would I continue with: > > rdf:resource="http://zitgist.com/music/artist/f4d5cc07-3bc9-4836-9b15-88a08359bc63" > /> > ... > ... > > and so on? > > Thanks for all your help, > Kurt > > On Friday, September 14, 2012 10:31:01 AM UTC-7, kurtjx wrote: >> >> You can find some info on the similarity ontology and some examples >> that might be helpful in my thesis: >> >> http://kurtisrandom.com/pages/connections-in-music >> >> 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 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 >> > >> > https://groups.google.com/d/msg/music-ontology-specification-group/-/gPr03C5XBAkJ. >> > >> > 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. > > -- > 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 > https://groups.google.com/d/msg/music-ontology-specification-group/-/0yxT73M14vsJ. > > 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.