We’re all accustomed to the BCE or CE suffixes on scientific publications. All of which invariably use the Gregorian Calendar. I believe this to be inherently intellectually dishonest.
Let’s face it, those people know exactly what “Common Era” entails. Either use the BC and AD suffix or don’t use the Gregorian Calendar at all. I have no objections against it, just the notion that we’re stepping on egg shells when we all know what we’re doing by using said calendar.
What’s the alternative?
There are definite benefits to seperating Months, Years, and Days, but science, more often than not, isn’t about minor conveniences. Science is about precision and repeatability. Hence the often used scientific notation of large numbers.
E.G. 2.5 x 105. It’s probably easier to just say “Two Hundred and Fifty Thousand”, but that’s an awful lot more characters. Besides, not everyone in the scientific world uses English as their first language. The scientific notation is immediately recognizable, understood and, more importantly, precise in any language.
Let’s do the same for dates and times. Days, Months, Years and even the exact time down to the second can be expressed in one concise datestamp.
E.G. While writing this sentence, the exact date is 213184.108.40.206.
This datestamp is very easy to caclulate. The number in front before the first period is the number of days since January 1st 1950. The second number is 7 by the 24 hour clock. The third is 59 minutes and the last is 2 seconds. Therefore, tomorrow will be 21334 and yesterday was 21332.
Fans of StarTrek would notice a similarity to Stardates used in that fictional universe. Well the premise of that timeline and date is sound, however its execution was less than… um… stellar.
The year 1950 was chosen by scientists as an arbritary measure to reflect timescales in reference to what is considered “Present”. I.E. Any event before 1950 is “Before Present” or “BP”. I think it’s a good idea.
If I were to write this date out in English, it would be May 29th, 2008 7:59:02PM. However this is only “standard” in the United States. Elsewhere the date format is the day first, month second and year last. Some other locals may have the year first month second and day last. By always having the days in front and only in numbers, we avoid all this confusion and it is far more precise. You don’t even have to remember AM or PM since it’s all on the 24 hour clock.
Calculating the days between events also becomes easier as it’s just a matter of subtracting or adding numbers. Much like the scientific notation. What’s more, you can even express the time to the last second if necessary.
All this in a blurb less than 15 characters long (including the periods and assuming two digit seconds) for today’s date. You could even memorize the whole thing down to the last second as it’s no longer than a long distance phone number.
Though the inital reference point for calculating Before Present was based on the Gregorian Calendar, it still defines an arbritary starting point. And hence forth it’s on its own reference point.
This is a constructed international datestamp using an existing reference in much the same way Esperanto and Interlingua are constructed international languages using existing reference languages.
To find out the exact date right now, I wrote a little script to help things go forward. It can also calculate a future or past date. It defaults to today’s date and time based on your computer’s time settings (make sure it’s accurate). Try putting in a value before 1950 and you get a negative date value. No more “Before” or “After” nonsense. It’s all purely numeric.