W3C home > Mailing lists > Public > public-egov-ig@w3.org > August 2014

Re: Linked SDMX Data

From: Gannon Dick <gannon_dick@yahoo.com>
Date: Fri, 15 Aug 2014 10:07:05 -0700
Message-ID: <1408122425.79278.YahooMailBasic@web122905.mail.ne1.yahoo.com>
To: public-lod@w3.org, Sarven Capadisli <info@csarven.ca>
Cc: KevinFord <kefo@loc.gov>, "public-locadd@w3.org" <public-locadd@w3.org>, "public-egov-ig@w3.org" <public-egov-ig@w3.org>, "public-opengov@w3.org" <public-opengov@w3.org>
Hi Sarven,

Yes, I have implemented "Artificial Bureaucracy", a derivative, so to speak, of Artificial Intelligence.  Much more importantly, it was also officially adopted by a reputable *cough* Spook Shop *cough* Authority on June 30, 2014 [1].

The two letter (country/domain) codes are affine [2] with all other systems of similar codes (eg. ISO 3166-1 (2A), ISO 3166-2 (3A), MARC (2A), FIPS (2N), etc..  "Artificial Bureaucracy" is shorthand for:  "There are only 676 names in the hat, draw one and put it back before you draw another one.".  There are many subdivisions, and a RESTful *stovepipe* has an unlimited number of variations, but a RESTful *top level domain* does not.

Display Language Codes (2A), Bibliographic Language Codes (2A or 3A) have the same property, although the US Library of Congress is the ISO Authority and Librarians in general are mean enough to use it on hapless Scholars caught in their web.  I doubt that the scheme has changed much since I linked it two years ago[3].

Anyway, Time Shifting (think: Quarterly Conference Calls with Analysts) and Shape Shifting (think: National Boundaries disputed or not) are part and parcel of the same geometry[4], as I observed yesterday[5], spreadsheets [6].  At all costs you want to avoid "inversion" of the Work-Life-(rest) Balance.  This may be a "deep" question for Finance (money works 24x7), but it is very simple principle for a local Grocery Store (is there somewhere we can send cabbage overnight where it could be sold = will be a performing asset ? Um, no.).

None of this is an attempt to "own" Linked Data in the "Embrace, Extend, Extinguish" sense.  The NGA "Undersea Feature" is <owl:sameAs> the UN-LOCODE "Installations in International Waters".


[1] http://geonames.nga.mil/namesgaz/
[2] http://en.wikipedia.org/wiki/Affine_transformation
[3] http://www.rustprivacy.org/2012/urn/lang/person/
[4] http://en.wikipedia.org/wiki/Pythagorean_theorem
[5] http://lists.w3.org/Archives/Public/public-egov-ig/2014Aug/0003.html
[6] spreadsheets http://lists.w3.org/Archives/Public/public-egov-ig/2014Aug/0001.html

On Fri, 8/15/14, Sarven Capadisli <info@csarven.ca> wrote:

 Subject: Re: Linked SDMX Data
 To: "Gannon Dick" <gannon_dick@yahoo.com>, public-lod@w3.org
 Cc: "KevinFord" <kefo@loc.gov>, "public-locadd@w3.org" <public-locadd@w3.org>, "public-egov-ig@w3.org" <public-egov-ig@w3.org>, "public-opengov@w3.org" <public-opengov@w3.org>
 Date: Friday, August 15, 2014, 4:12 AM
 On 2014-08-11 22:58,
 Gannon Dick wrote:
 > Sorry for the
 Don't be. It is
 a natural thing.
 > Hi
 > I noticed
 you used GeoNames for the "Australian Bureau of
 Statistics Linked Data" hack mentioned below. 
 GeoNames does much useful work ... but everyone in the
 Linked Data business could use a little help.
 > Domains - in theory,
 the countries of the world are a group of (federalized data
 set of ...) (groups of) Court Houses, Jurisdictions, keyed
 with two and three letter acronyms (ISO 3166).  This set
 for all practical purposes is a Unicode Code Page, but
 instead of (16x4)=256 members there are (169x4)=676 Latin
 Alphabet Capital Letters.  Statistical metrics at the
 domain level are manipulated with Linear Algebra and Linear
 Programming. Diacritics (Côte d'Ivoire) or alternate
 forms (Ivory Coast) do nothing semantically useful, the
 acronym is the leveler.
 > So, I rewrote the GeoName table (http://www.geonames.org/countries/) to
 > 1) Unicode compliant for XML (HTML
 entities are HEX escaped)
 > 2) The
 Geo's, Country Profiles, whatever are local links.  I
 left those as is and included/matched the MARC System / US
 Library of Congress Linked Data Service URI's (http://id.loc.gov/vocabulary/countries.html).
 > 3) Finally, I used an SQL RDB to do an
 Outer Join on the Code Set - all 676 possibilities.  Adding
 a three character code "synonym" does not increase
 the code page size.  It is then possible to split this
 "registry" into lists of codes 1) Present, 2)
 Missing and 3) "Slack" (in the Linear Programming
 > 4) Put the files in (FODS -
 (Flat XML) Open Document Spreadsheets format) so that
 European Civil Servants can not whine about data quality
 (got your back, DERI, you too ABS).
 > http://www.rustprivacy.org/2014/balance/gts/geonames_domains.zip
 > Unfortunately, when
 RDF Lists of Place Names are filtered through previously
 written applications the result is often unhelpful
 additions, however these steps should ameliorate the problem
 Thanks Gannon. If
 I understand correctly, you got around to implement 
 your suggestion back in 2012Q1:
 Care to clarify what I should
 make of:
Received on Friday, 15 August 2014 17:07:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:43:32 UTC