- From: Gannon Dick <gannon_dick@yahoo.com>
- Date: Tue, 8 Apr 2014 15:07:52 -0700 (PDT)
- To: public-html-comments@w3.org, "Jukka K. Korpela" <jukka.k.korpela@kolumbus.fi>, Mark Webley <markw@adobeconsultant.co.uk>
Thanks Mark. Perhaps it's best to solve both of your wants at the same time ... If an event occurs on "Day Zero", then a Consultancy, Strategist, Data Journalist, etc. has reports due monthly, quarterly, etc. afterwards. And if the event revolves around a place or group of places then the ISO 3166 2 Alpha Country Codes can be used. What is not so evident to coders in panic mode is that both a Reporting Schedule and the Code Set "coordinate systems" inter-operate just fine, and there is no real need to "build" anything. It just takes a little math (Polar Coordinates). A Javascript API would be easy, but I did it on a spreadsheet as it was faster. http://www.rustprivacy.org/2014/balance/CountryReports.jpg The Country Codes are a "dust". There are 30 something User-Defined codes you can assign, and also some exclusions. The Reporting Year is quarterly, but the minor ticks are monthly "on or about" due dates. The horizontal distance on the abscissa (x coordinate) is constant for both scales. If you need numbers the "grid" is (26 Letters ^2 = 676) by (1461/16 Quarters = 4 Years), try this: http://www.pagetutor.com/trigcalc/trig.html Curacao (75) and Guernsey (163) are used to show the horizontal distance property. If you want to scale down to the Twitter Time Scale, note that there are 86,400 seconds in 24 hours. Please don't tell Big Data I said anything, it is a cosmic security secret, apparently. So, you have a Country List and a Report Schedule on the same (chart), (page), (graph) etc. and everything is there. As Jukka mentioned, some of the names are rough on political sensibilities, but it is much easier to take "coverage" out of an application than to scale up. --Gannon -------------------------------------------- On Tue, 4/8/14, Mark Webley <markw@adobeconsultant.co.uk> wrote: Subject: Re: Proposal recommendation to Wc3 implimentation To: "Gannon Dick" <gannon_dick@yahoo.com>, public-html-comments@w3.org, "Jukka K. Korpela" <jukka.k.korpela@kolumbus.fi> Date: Tuesday, April 8, 2014, 12:53 PM Hi Guys I understand, but this is why I thought it would be a good idea to include the basic countries, under Europe, Americas, Latin America, Asia, the Orient etc.. than for any other countries needed to be added use the html5 's dataList I think it is called. Then we could even have a data list to remove countries from the list. Do not let boss greed prevent you from prospering :) -- Kind Regards Mark Follow My Professional Profile on: http://www.wisechamber.com/pro/mark-webley On 08/04/2014 17:25, Gannon Dick wrote: -------------------------------------------- On Mon, 4/7/14, Jukka K. Korpela <jukka.k.korpela@kolumbus.fi> wrote: Undoubtedly it is fairly common, and we could present a good argument in favor of it: most country selection controls are faulty one way or another (e.g., missing new countries and displaying countries that have ceased to exist, or wrong names), and the quality might be improved, if they were based on native controls in browsers, updated frequently. ====================== I think the basic problem is that everyone's Boss has assumed dreams of incremental world domination. This leads coders to include the missing and stop when the Boss does not see anything missing. It is not a good way for Consultancies to work. A Strategy Markup Language[1], Data Journalism[2], Linked Data ID Server[3], or a Cloud have to work in a different way. One thing which considerably simplifies the task is to assume unidirectional data flow (either imports or exports). Also, the fine structure of imports in world trade is much more complex than that of exports. The evidence is that "The Silk Road" between Asia and Europe worked so well because the two local naming Authorities on either end made the mid-route secure per force although for practical reasons did not bother with interoperability. http://www.rustprivacy.org/faca/simTLD/ If this all sounds like browser/format wars and Social Networking privacy ills, it should, because the overarching logistics are the same. Pity, really, the ability to launch a Crusade or summon up the Mongol Horde might lead to a much more sane debate about data privacy. I originally named the scheme "The Silk Road" ... a week before a drug ring of the same name was busted. My bad luck :) The new name is simTLD (simulated Top Level Domain) is straightforward - Authority by circularly polarized coordinates. This is IEEE territory not W3C territory. ====================== But I'm afraid the counterarguments are too strong. -- Yucca, http://www.cs.tut.fi/~jkorpela/ ====================== I agree, this is way too ambitious for (every day use) HTML5 as it depends upon external standards for missing items. The possible depends on your definition of "data analytics" not on communication with markup languages. --Gannon [1] http://stratml.hyperbase.com/stratml.html [2] http://semanticommunity.info/ [3] http://id.loc.gov/
Received on Tuesday, 8 April 2014 22:08:20 UTC