W3C home > Mailing lists > Public > public-egov-ig@w3.org > October 2010

Re: Is Privacy Dead ? A helpful hint.

From: Gannon Dick <gannon_dick@yahoo.com>
Date: Fri, 8 Oct 2010 15:15:09 -0700 (PDT)
Message-ID: <551284.48070.qm@web112619.mail.gq1.yahoo.com>
To: W3C Egov IG <public-egov-ig@w3.org>
Ref below, for your weekend viewing pleasure ...

[1] A javascript encoder for Australia (from UN LOCODES).
[2] A javascript encoder for the Municipio's of Puerto Rico.  This is the "County" Equivalent.  Puerto Rico is part of US Customs Territory.  It would probably be a good idea to JSONize each state, too.
[3] An XML file with all the Place Names for Puerto Rico including Municipio, Zona Urbana, and Comunidad.  These have been recoded according to "arrival time", so that the types can retain alphabetical and cardinal order.  The "data" in each case is the original County (3) or Place (5) number code (US Census), which is missing the hierarchy - preventing you from distinguishing between a County, City or Town with the same name.

[1] http://www.rustprivacy.org/sun/spookville/australia.html
[2] http://www.rustprivacy.org/sun/spookville/puertorico.html
[3] http://www.rustprivacy.org/sun/spookville/puertorico.xml

--Gannon 
--- On Thu, 10/7/10, Gannon Dick <gannon_dick@yahoo.com> wrote:

Meta Data (e.g. facts) propagate as a wave as well as a particle.  A report released at a "Coordinated Time" does not reflect the habits of human communities trying to reach a consensus. Until everyone has seen a "fact", it's News.  While information travels at the speed of light, *consensus* has a fixed path exactly 24 Hours + 1 Second long.  That means, if you issue a report at time T, exactly 24 Hours + 1 Seconds later the whole world has seen it and a consensus can form.  Meta Data does not travel "through the grapevine", although "normal data" does - when a report is issued in Washington, London sees it as News 4 hours later and sees it as Meta Data 24 Hours + 1 Second after arrival.

It's just arithmetic.  Each Country and each Subdivision has a characteristic "Arrival Time".  This is a constant,
 and unique, for each individual Entity - so the pair (Country Arrival Time, Subdivision Arrival Time) is also unique, even if it does not have any "deeper" meaning itself.  And it does *not* have any deeper meaning after exactly 24 Hours + 1 Second from when the Statistic was issued.  In terms of a Physics, There are a bunch of standing waves, with varying frequencies which all collapse at T + (24 Hours + 1) Second, but since you knew the frequencies you can use them to sort the Entity Names.

For Communities, and Meta Data I think "Consensus Moment" is a good way to put it, but in exactly 24 Hours + 1 Second, I should probably take a poll ;o)

As a practical example of how this might be used, a csv of the group of Entities which comprise NAFTA (US+Canada+Mexico, technically I should exclude some of the Entities or add subdivisions, Palau etc.) is at

http://www.rustprivacy.org/sun/spookville/nafta.txt

If you were
 going to release NAFTA statics, then you would need to have a static (or a null) for every entity.

I also made a javascript calculator to compute the apparent arrival times, one at a time.  I'll post it in a few days.

--Gannon












      


      
Received on Saturday, 9 October 2010 05:35:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 9 October 2010 05:35:06 GMT