Loading ...
Sorry, an error occurred while loading the content.

2133RE: [ISO8601] The challenge

Expand Messages
  • tex
    Jun 22, 2007
    • 0 Attachment

      Herman,

       

      Thanks for this. I think the answer is to become more Babbage then Newton . Whereas calculus is effective for some calculations, the digital, mechanical counting mechanisms of the census are much more suitable to event math.

      It’s a little bit like doing Fourier transforms to use frequencies where they are more efficient and then converting back to spatial dimensions for the end results.

       

      Personally, I think it is a mistake to use names like addMonth, AddYear, because the number of seconds you need to add depends on the start value and the number of months or years etc. to be added (or subtracted if negative).

       

      Instead I would think of it as NextMonthlyAnniversary, NextAnniversary, NextWeeklyAnniversary, etc. (“Anniversary” is generalized and not used in the sense of an annual occurrence.)

      So Next month, adds one to the month field which can represent a variable number of seconds of actual time units, since it can be a 28, 29, 30, or 31 day month, it might include a leap second, a change to/from daylight savings, etc.

       

      If the month value exceeds the maximum (12) then of course it wraps to 1 and the year must be upped.

       

      Once you generate the intended anniversary you can convert it to the number of seconds since the time epoch and calculate the actual number of seconds greater than the start event.

       

      Maybe a better analogy than the fourier transform is to consider flying across the surface of the spherical earth.

      You can travel 1 mile south and 1 mile west and 1 mile north, and depending whether your starting point is the north pole or not, you can end up at the same or a different point from the origin.

       

      tex

       


      Time Event Algebraic Notation

       

      The ISO-8601 duration “PnYnMndTnHnMnS” is a brilliant start to time event algebra.

       

      The challenge, be the first to:

      ·          Develop formulas for all the holidays.

      ·          Develop a formula to convert calendar date to ordinal date and back.

      ·          Devlope a formual to convert calendar ate to week date and back.

      ·          Develop improvements to event algebra formulas.

       

      I will program the parsing of the formula to prove them correct!

      Use the following expanded formuals as explained in this article and invent other symbols:

      ±P±nY±nM±nDT±nH±nM±nS±nF            date/time arithmetic

      ±P±nY±nW±nDT±nH±nM±nS±nF     week of year arithmetic

      =P=nY=nM=nDT= nH=nM=nS= nF     set calendar date/time

      =P=nY=nW=nDT= nH=nM=nS= nF set week of years date/time

      Maybe you might become a Babbage or Newton , but probable something less.

      The problem, scheduling software, appointment software, other software, cell phone, PDAs and even watches need a universal method of expressing past and future events.  Past dates require retentions times after the date for update or delete, and future dates require reminder times before the date for notification.   A Web based program should be able to auto-synchronize a server master list with client computer software, the cell phone and a computer or cell phone should be able to synchronize a watch.  The modern electronic age needs a universal standard language to provide descriptions of events (holidays, birthdays, meeting …etc) and that provide for retention and notification in a systematic way.        

    • Show all 9 messages in this topic