What about the <a href="http://mars.jpl.nasa.gov/mro/">Mars <span class="featureText"></span></a><a>Reconnaissance Orbiter</a> and other artificial satellites that orbit things besides Earth? I was thinking of Satellite as a very simple and generic type that could include an "Orbiting body" property, reciprocated with "Satellite(s)". Maybe it would have a couple other properties too? Many of the "<a href="http://www.freebase.com/tools/schema/user/spatialed/default_domain/earth_orbiting_satellite">Earth orbiting satellite</a>" properties should probably be split into "Geostationary", "Sun-synchronous" and other <a href="http://en.wikipedia.org/wiki/List_of_orbits">orbiting types</a> so that their orbits can be properly described. Some of these types might be appropriate for any satellite. An "Artificial satellite" type might have a few more properties but would certainly be co-typed with "Spacecraft". Specialty artificial satellite types could then be co-typed depending on whether the satellite was used for observation or other purposes.<br>
<br>Co-typing, naming, and descriptions would be key so that users don't get lost in these minutia when they're just trying to add some basic data to <a href="http://www.freebase.com/view/guid/9202a8c04000641f800000000040e186">Io</a> vs. <a href="http://www.freebase.com/view/en/hubble_space_telescope">Hubble</a> vs. <a href="http://www.freebase.com/view/en/landsat_7">Landsat 7</a> vs. ....<br>
<br>Too complex?<br><br>-Ed<br><br><div class="gmail_quote">On Fri, May 2, 2008 at 10:35 PM, Danny Hillis <<a href="mailto:danny@appliedminds.com">danny@appliedminds.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I like what you suggest about moving Discoverer,etc.<br>
<br>
One issue that we should consider is that almost any celestial object<br>
is orbiting around something, even is it is the black hole at the<br>
center of the galaxy. Maybe the idea of "orbit" is more useful for<br>
this than making the type Satellite too generic. We could keep<br>
Satellite as meaning as earth-orbiting artificial satellite and give<br>
all celestial bodies an orbit and (as you suggest) a set of orbiting<br>
bodies.<br>
<font color="#888888">-Danny<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
On May 2, 2008, at 6:10 PM, Gordon Mackenzie wrote:<br>
<br>
> Metapsyche and I did some work a while back to add more useful<br>
> properties for his exoplanet type and I am considering moving most of<br>
> those properties to Celestial Object and adding planet as a co-type.<br>
> Celestial Object is our workhorse of a generic Astronomical Object<br>
> type that is included by Star, Planet, Natural Satellite, Asteroid,<br>
> Comet types. I'm unsure what specifically to retain within exoplanet,<br>
> pretty much most of the non-celestial object bound properties could be<br>
> placed within the Planet type. Exoplanet could be just a boolean true/<br>
> false for is this planet an exoplanet for that matter.<br>
><br>
> So Celestial Object would have added specifically:<br>
><br>
> Discoverer, Discovery Date, Discovery Method, Discovery status,<br>
> Discovery Institution/organization<br>
><br>
> And then remove/move the data for the related discovery properties in<br>
> Planet/Asteroid/Comet types to the equivalents in Celestial Body.<br>
> Planet type might have both jupiter and earth-based radius and mass<br>
> properties.<br>
><br>
> One question I have is whether Natural Satellites should be<br>
> individually added as a property to Planet and Asteroid types or to<br>
> add as a single property to just Celestial Object. The latter is<br>
> simpler, but the former allows cleaner demarcation of moons of<br>
> planetary bodies and asteroidal moons.<br>
><br>
> ~ Gordon<br>
><br>
> <<< <a href="mailto:gordon@metaweb.com">gordon@metaweb.com</a> >>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Data-modeling mailing list<br>
> <a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a><br>
> <a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">http://lists.freebase.com/mailman/listinfo/data-modeling</a><br>
<br>
_______________________________________________<br>
Data-modeling mailing list<br>
<a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a><br>
<a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">http://lists.freebase.com/mailman/listinfo/data-modeling</a><br>
</div></div></blockquote></div><br>