robla

#!/bin/bash

function print_24hr_string () {
  # Wrapper around "date" command for printing 24hr datetime
  # 1: "tzolson": timezone id from the Olson DB
  tzolson="$1"
  # 2: "placename": more relevant timezone label than Olson's choices
  placename="$2"
  # 3: "fdate" is "function date" for date passed to this func
  fdate="$3"

robla

I was heavily involved in the IETF and the W3C back in the late 1990s, when "the web" was new (and when the "W3C" was new). Back then, there was a big debate about the wisdom of "Postel's law", which I strongly suspect was a big part of the rationale for the W3C forking from the IETF. After the failure of HTML 2.0 (published by the IETF) to be published quickly enough to stop the creation of de facto standards by Netscape and Microsoft, since HTML 2.0 doesn't have very many features in it, but Netscape's and Microsoft's browsers had many more features. The W3C went down the path of insisting that compliant implementations should "halt and catch fire" (so to speak) when they published the XML specification in 1997. The "XHTML" experiment proved that organizations don't have that much authority, and that anyone who purports to be a "compliance cop" from one of those or

robla

{"title": "Tennessee capitol example"}
{"description": "Hypothetical example of selecting capitol of Tennessee, frequently used on Wikipedia and electowiki.  The proportion of voters is loosely based on the people who live in the metropolitan areas of the four largest cities in Tennessee, and the numeric ratings are based on crow-flying mileage to the city from the other metro areas."}
# See https://electowiki.org/wiki/Tennessee_example for illustrations
=Memph:[Memphis, TN]
=Nash:[Nashville, TN]
=Chat:[Chattanooga, TN]
=Knox:[Knoxville, TN]
# -------------------------
# Ratings are 400 miles minus crow-flying mileage to city 
42:Memph/400>Nash/200>Chat/133>Knox/45