Skip to main content

Evolution of Definitions – The Problem of Pluto

In early 2006 I had the privilege of seeing NASA’s New Horizon’s mission blast off on its way to Pluto.  At that time, Pluto was a planet.  By August of the same year it was not.

On August 24, 2006, the International Astronomical Union (IAU) publicly defined a planet as "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.".

This raises questions such as:
  • Can definitions change?  Pluto had been called a planet until the IAU changed the boundaries of the definition.
  • What authority has the IAU to define a planet?
  • I still think of Pluto as a planet – am I wrong to do so?
  • The IAU’s new definition seems a bit contrived.  Will it stand up?
  • What motivation did the IAU have to change the definition? 
Definitions can change, and should as we get to know reality better.  Yet the evolution of definitions seems to be little dealt with in the traditional literature on definitions.  It would be nice to have some rules about it, and some thought about how it should be done.

As to the IAU, it is quite free to come up with a definition for any term – just as the Red Queen did in Alice in Wonderland.  And I too am free to have my own definition of a planet.  Whether the IAU’s definition will stand up is a good question.  New research suggests  that extra-solar planetary systems are very diverse.  The IAU’s definition may very well not stand up in the face of future discoveries – but surely such evolution is part of what science is.  As to motivation, that is a discussion for another post – but it often matters for all kinds of reasons.

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...