<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <author>
    <name>User Administrator</name>
    <uri>http://www.freebase.com:80/view/user/user_administrator</uri>
  </author>
    <generator uri="http://www.freebase.com/">Freebase Atom Feed Generator</generator>
    <id>http://www.freebase.com:80/view/user/slothman</id>
    <link rel="self" href="http://www.freebase.com:80/feed/discuss/watched/user/slothman"/>
    <title>slothman</title>
    <updated>2008-09-06T17:18:08Z</updated>
  <entry>
    <author>
    <name>jeff</name>
    <uri>http://www.freebase.com:80/view/user/jeff</uri>
  </author>
    <content type="html">&lt;p&gt;&lt;p&gt;My understanding of this type is that classes of objects should not be co-typed as &amp;quot;celestial object&amp;quot;. If you see any, feel free to de-type them. As far as its being a very general type, that's by design -- it holds a number of properties that are common to all or most kinds of celestial object, which both saves us from having to include the same properties on a large number of types, and also makes writing queries much easier. (I.e., if you want to know all objects with an absolute magnitude of &amp;gt; 4 or whatever, you only need to query against one type, rather than create separate queries for every type.)&amp;nbsp; &lt;/p&gt;&lt;p&gt;Freebase has a non-hierarchical structure, so &amp;quot;celestial object&amp;quot; is an included type of comet, planet, etc. If you look at the topic for &lt;a href="/view/comet_hale-bopp"&gt;Comet Hale-Bopp&lt;/a&gt;, you can see that it has both the comet and celestial object types, which gives it the full range of properties of both types. &lt;/p&gt;&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006ea9f63</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006ea9f63" title="Celestial Object: Much too general"/>
    <summary type="html">My understanding of this type is that classes of objects should not be co-typed as &amp;quot;celestial...</summary>
    <title>Celestial Object: Much too general</title>
    <updated>2008-01-14T19:06:06.0007Z</updated>
  </entry><entry>
    <author>
    <name>dmehring</name>
    <uri>http://www.freebase.com:80/view/user/dmehring</uri>
  </author>
    <content type="html">&lt;p&gt;&lt;p&gt;This is much too general of a type. Just purusing the list of what is in here already, I see comets, planets, stars, supernova remnants, etc. I also see individual objects (eg, individual comets) as well as classes or types of objects (eg HII regions).&amp;nbsp; You might consider structuring the schema like this:&lt;/p&gt;&lt;p&gt;&amp;nbsp;Celestial Object -&amp;gt; Object Type -&amp;gt; individual Object&lt;/p&gt;&lt;p&gt;&amp;nbsp;eg&lt;/p&gt;&lt;p&gt;&amp;nbsp;Celestial Object -&amp;gt; Comet -&amp;gt; Hale-Bopp&lt;/p&gt;&lt;p&gt;Celestial Object -&amp;gt; Supernova Remant -&amp;gt; Crab Nebula&lt;/p&gt;&lt;p&gt;&amp;nbsp;You will still likely run into issues, but at least things will be classified in a more meaningful way. &lt;/p&gt;&lt;p&gt;(Just an aside, &amp;quot;Nebula&amp;quot; is also a generic (and antiquated) term which can describe vastly different types of objects - Crab Nebula =&amp;gt; supernova remnant, Orion Nebula =&amp;gt; star forming region, Andromeda Nebula =&amp;gt; galaxy).&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006ea74be</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006ea74be" title="Celestial Object: Much too general"/>
    <summary type="html">This is much too general of a type. Just purusing the list of what is in here already, I see comets...</summary>
    <title>Celestial Object: Much too general</title>
    <updated>2008-01-13T11:58:20.0005Z</updated>
  </entry><entry>
    <author>
    <name>slothman</name>
    <uri>http://www.freebase.com:80/view/user/slothman</uri>
  </author>
    <content type="html">&lt;p&gt;The term is "Right Ascension". http://en.wikipedia.org/wiki/Right_Ascension
It's not really appropriate for anything closer than a star unless you want to make properties that are calculated from an algorithm rather than being a static floating point number.&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f80000000054f1121</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f80000000054f1121" title="Celestial Object: Spelling nitpick"/>
    <summary type="html">The term is "Right Ascension". http://en.wikipedia.org/wiki/Right_Ascension
It's not really...</summary>
    <title>Celestial Object: Spelling nitpick</title>
    <updated>2007-07-25T20:14:34.0011Z</updated>
  </entry><entry>
    <author>
    <name>d_leaper</name>
    <uri>http://www.freebase.com:80/view/user/d_leaper</uri>
  </author>
    <content type="html">&lt;p&gt;from earth? solar system? sun? center of containing galaxy?
and since it is moving, i guess it should be either time related (when it was calculated) or average.
&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f80000000054ba444</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f80000000054ba444" title="Celestial Object: Distance (parsecs) - from where?"/>
    <summary type="html">from earth? solar system? sun? center of containing galaxy?
and since it is moving, i guess it...</summary>
    <title>Celestial Object: Distance (parsecs) - from where?</title>
    <updated>2007-07-14T12:39:57.0004Z</updated>
  </entry>
</feed>