<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <author>
    <name>Metaweb</name>
    <uri>http://www.freebase.com:80/view/user/metaweb</uri>
  </author>
    <generator uri="http://www.freebase.com/">Freebase Atom Feed Generator</generator>
    <id>http://www.freebase.com:80/view/music/album</id>
    <link rel="self" href="http://www.freebase.com:80/feed/discuss/topic/music/album"/>
    <title>Musical Album</title>
    <updated>2008-05-16T20:45:18Z</updated>
  <entry>
    <author>
    <name>patrick</name>
    <uri>http://www.freebase.com:80/view/user/patrick</uri>
  </author>
    <content type="html">&lt;p&gt;Yep - they sure will. What you can do is create a music review type in your private domain to experiment with this. You can create a private type by going to the "My profile" page and adding the new type to the "types created" list. After adding a new type, click on it to edit its schema. The schema editor is fairly complex, but since this type is private, you can experiment without breaking anything.
&lt;br /&gt;
&lt;br /&gt;
Here's one possible schema for the type Music Review:
&lt;br /&gt;
&lt;br /&gt;
- reviewer [type: Music Reviewer]
&lt;br /&gt;
- review blurb [type: text]
&lt;br /&gt;
- rating (1 = worst, 5=best) [type:integer, or type:float if you want to allow 2.5, 3.5, etc)
&lt;br /&gt;
- reviewed album [type: Musical Album]
&lt;br /&gt;
&lt;br /&gt;
Note that you don't need to add a title field for your review because the display name property is already there on the type you created.
&lt;br /&gt;
&lt;br /&gt;
Once you've created this type, you can create a new instance of it - a review. Give the review a name, fill in the fields, and you're done.
&lt;br /&gt;
&lt;br /&gt;
I've glossed over how to create the type "Music Reviewer," but I hope this gives you enough ideas to start experimenting. Also, look at how other types are structured by editing them. Don't worry about breaking any public schema - since you don't own them, your changes won't be saved in edit mode.
&lt;/p&gt;</content>
    <id>http://www.freebase.comhttp://www.freebase.com:80/view/guid/9202a8c04000641f8000000004f6c19c</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000004f6c19c" title="Musical Album: Review Fields for albums"/>
    <summary type="html">Yep - they sure will. What you can do is create a music review type in your private domain to...</summary>
    <title>Musical Album: Review Fields for albums</title>
    <updated>2007-05-04T23:53:30.0006Z</updated>
  </entry><entry>
    <author>
    <name>mlaurenc</name>
    <uri>http://www.freebase.com:80/view/user/mlaurenc</uri>
  </author>
    <content type="html">&lt;p&gt;Being new to Freebase, I'm not sure how to do this myself (I doubt I can without Admin access), the the Musical Album/Release/Track types should have fields for Reviews... I'm quite sure people will want to read critical praise/flames about albums they are perusing.
&lt;/p&gt;</content>
    <id>http://www.freebase.comhttp://www.freebase.com:80/view/guid/9202a8c04000641f8000000004f4a92a</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000004f4a92a" title="Musical Album: Review Fields for albums"/>
    <summary type="html">Being new to Freebase, I'm not sure how to do this myself (I doubt I can without Admin access), the...</summary>
    <title>Musical Album: Review Fields for albums</title>
    <updated>2007-05-04T15:09:56.0012Z</updated>
  </entry><entry>
    <author>
    <name>danm</name>
    <uri>http://www.freebase.com:80/view/user/danm</uri>
  </author>
    <content type="html">&lt;p&gt;Musical releases are like versions of an album, it will be useful for someone to be able to view a release list for a particular album.
&lt;/p&gt;</content>
    <id>http://www.freebase.comhttp://www.freebase.com:80/view/guid/9202a8c04000641f80000000041f8a7e</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f80000000041f8a7e" title="Musical Album: I've added a link back to Musical Release"/>
    <summary type="html">Musical releases are like versions of an album, it will be useful for someone to be able to view a...</summary>
    <title>Musical Album: I've added a link back to Musical Release</title>
    <updated>2007-03-02T23:19:21.0012Z</updated>
  </entry><entry>
    <author>
    <name>danm</name>
    <uri>http://www.freebase.com:80/view/user/danm</uri>
  </author>
    <content type="html">I agree. I've hidden these properties for now. We can bring them back if they become useful, or garden them out if they don't.</content>
    <id>http://www.freebase.comhttp://www.freebase.com:80/view/guid/9202a8c04000641f8000000003e00de8</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000003e00de8" title="Musical Album: Previous Release?"/>
    <summary type="html">I agree. I've hidden these properties for now. We can bring them back if they become useful, or...</summary>
    <title>Musical Album: Previous Release?</title>
    <updated>2007-02-08T01:05:02.0006Z</updated>
  </entry><entry>
    <author>
    <name>robert</name>
    <uri>http://www.freebase.com:80/view/user/robert</uri>
  </author>
    <content type="html">The "previous release" and "next release" properties don't make sense to me.  First, they encode ordering redundantly -- one can generate a time-ordered list of releases.  Second, they are very unlikely to be filled in (because of the first issue), so they will never be queryable in any meaningful way.&lt;br /&gt;
&lt;br /&gt;
I recommend hiding them as they only clutter the display and will probably not be useful to API users because of data sparseness.</content>
    <id>http://www.freebase.comhttp://www.freebase.com:80/view/guid/9202a8c04000641f8000000003e00c23</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000003e00c23" title="Musical Album: Previous Release?"/>
    <summary type="html">The "previous release" and "next release" properties don't make sense to me. First, they encode...</summary>
    <title>Musical Album: Previous Release?</title>
    <updated>2007-02-08T00:20:03.0011Z</updated>
  </entry>
</feed>