Skip to main content

Is the IAU Definition of "Planet" A Quality Definition?

In this post we continue to learn lessons from the International Astronomical Union's definition of "planet" in 2006 (http://www.iau.org/public_press/news/detail/iau0603/).  The question tackled here is whether the IAU's definition of "planet" is a quality definition.  After close examination, it seems it is not.

Here is the definition:

'A "planet" [1] is a celestial body that (a) is in orbit around the Sun, (b) has sufficient mass for its self-gravity to overcome rigid body forces so that it assumes a hydrostatic equilibrium (nearly round) shape, and (c) has cleared the neighbourhood around its orbit.

[1] The eight planets are: Mercury, Venus, Earth, Mars, Jupiter, Saturn, Uranus, and Neptune.' 

And here is the analysis of the definition:

(a) The definition is not actually of "planet" but of "planets in our Solar System".  This can be mined out of the text of Resolution 5A, which states: 

"RESOLUTION 5A The IAU therefore resolves that planets and other bodies in our Solar System, except satellites, be defined into three distinct categories in the following way..." 

So the IAU did not define "planet" at all, but merely "planets in our Solar System".  We will need to explore this in a further post, but it is clearly a source of confusion, and hence the definition is of poor quality (definitions are not supposed to cause confusion).

(b) The superordinate genus identified in the definition is "celestial body".  If I look up "celestial body" in Wordnet (http://wordnet.princeton.edu) I get "natural objects visible in the sky".  So, celestial bodies must include planets, stars, comets, asteroids, nebulae, galaxies, and so on.  As such, the genus seems too remote for a quality definition - it is little better than "thing".  There seems to be a strong possibility that it could be divided into genera that are superordinate to "planet", but subordinate to "celestial body".  What are they?  That is not my job - I am not an astronomer.  But I can tell you that a more proximate superordinate genus is required for this to be a quality definition.

(c) The definition contains the phrase "is in orbit around the Sun".  This clearly shows that only our Solar System" is being considered, as we saw above.  Guess what - I could tell from the term "planets in our Solar System" (the definiendum
) that the planets would be orbiting the Sun.  That is part of the definition (or description) of "our Solar System".  The term "Sun" should not have been used in the definition.  It is an essential characteristic of "our Solar System", not "planet".  Another point that shows we do not have a quality definition.

(d) If the IAU chooses to define "planet in our Solar System" it is obliged to define "extrasolar planet" (the coordinate species) and "planet" (the proximate superordinate genus).  At the very least these should have been referenced in Resolution 5A.  There is no such reference in 5A.  Again, an indication of a poor quality definition.

(e) What does "(c) has cleared the neighbourhood around its orbit" actually mean?  What is "neighbourhood" in the celestial context?  It is easily understood as a general (human, non-astronomical) term, but that cannot possibly apply here.  What is it?  Suppose I make the presumption that "cleared" means "to have removed matter".  I really do not have any right to do so, but suppose I do.  Well, the Earth has not absorbed the Moon or ejected the Moon from its proximity.  So is the Earth not a planet?  This is a big failure, because definitions are supposed to make things clear.  Again, we have a poor quality definition.


In defense of the IAU, it is quite difficult to produce definitions in natural science.  There is usually no alternative to them being other than descriptive (as opposed to essential or causal).  However, the IAU could have done better.

Thus, we see that we have a poor quality definition of "planet".  Sorry, I meant to say "planet in our Solar System".

Comments

Popular Posts

Create Your Own Social Networking Site

Create Your Own Social Networking Site JCOW: Ethical Hacking Top 10 reasons to choose Jcow:- 1. Handle more traffic - Clean codes and Dynamic caching can lower the CPU load and  speed up your website. 2 Make your site more interactive - Well designed Jcow applications help you members to connect and communicate with others more effectively. 3 Add questions to the Registration Form - You can add new member fields, which will be displayed to the registration form, profile form, and the member browsing form. 4 Easily share stuff - Within the AJAX sharing Box, your members can publish status,  photos, videos, and blogs. 5 Customize and Extend your Jcow Network - A Jcow network consists of core apps(like "Friends" and "Messages") and optional apps(like "Blogs" and ""Videos"). You can enable/disable optional apps. You can also develop your own apps. 6 Every profile could be Unique - Members can customize their own profile theme and  add music play...

WRITE "I LOVE YOU" ON CMD BY USING NOTEPAD

I had previously posted about   Matrix effect   using Notepad   as well as cool batch file  programs. In this post i will share with you guys  the cool and awesome  Notepad Tricks .  As name suggest you don't require any program other then Notepad.  So lets get started. 1. Open  Notepad   and copy below code. @echo off color 0A :A echo IIIIIII     L      OOOOOO V           V  EEEEEE     Y       Y  OOOOOO  U     U  ping -a .9 >nul echo    I        L      O    O  V         V   E           Y     Y   O    O  U     U  ping -b .9 >nul  echo    I        L      O    O   V       V    E   ...

HL7V2.x to HL7V3.0 Translation Issues Details-2

In continuation of my previous post this post lists the other issues associated with HL7 v2.x to HL7v3 translation Conformance Patterns: The other major issue with the transformation of messages is the behavior of application when a particular information exchange takes place. In HL7V3.0 apart from the trigger events and interactions there exists the notion of application role as senders and receivers. The application role is characterized as the entire set of interactions for which the sender and receiver are responsible for transmitting. HL7V3.0 clearly defines the possible interactions and the application behavior associated these interactions in the form of responses for which the sender and receiver needs to adhere to. The differences in messages between V2.x and V3.0 and absence of clear guidance on V2.x regarding application behavior on receipt of message makes the transformation exercise more difficult. Vocabulary: It is a well known fact that 80% of HL7 V2.x message failu...