- From: Gannon Dick <gannon_dick@yahoo.com>
- Date: Thu, 10 Feb 2011 18:38:58 -0800 (PST)
- To: "public-egov-ig@w3.org" <public-egov-ig@w3.org>
The *.gov.[xx] domain is a global unique identifier, where [xx] is the ISO 3166-1 "Country Code". A Policy Document also has a global unique identifier in time. That Identifier is (*.gov.[xx], title, (Julian Day|Year, Day of the Year)). This is true for Governments, but not true for all domains, since there is no authoritative list of codes (although .aero.[xxx] where [xxx] is the IANA Airport Code would work.). It's a URI. Some further food for thought ... 1. The javascript conversions back and forth between Julian Day and (Year, Day of the Year) are freely available. 2. The Julian Day is proportional to the area in square meters of all subdivisions too. There is a balance across Federal and Local Government levels just like the pH <-> pOH Chemical (acid-base) scale. 3. When you dial a phone you hear a "Beep" for each number dialed. You are hearing two frequencies. The phone switch sorts out the pair and says "Ah, he dialed a "3". In the same fashion, time has two frequencies, days and years. The "year" frequency (1 leap day in four years), dominates because it adds 86,400 seconds all at one time. An ODF Spreadsheet is here[1] which enables you to vary the year and day length and graphically it sort out. This is why a Date, not a Time Stamp is good enough. 4. Nature splits day and night, the 4 phase day is man-made :o) In fact, any more precision than plus/minus one "day" is a disadvantage. When your boss demands nanosecond transaction times, the correct technical description for him/her is "dummy-pants". Unfortunately, the 4 phase day means that the Seasons of the Year are spin-coupled, and "both" hemispheres share +/- 4*2 (16) Seasons (see the graphs in [1]). --Gannon [1] http://www.rustprivacy.org/2011/phase/standard-day.zip
Received on Friday, 11 February 2011 02:39:32 UTC