- From: Gannon Dick <gannon_dick@yahoo.com>
- Date: Tue, 16 Jun 2015 11:56:14 -0700
- To: dennis.hamilton@acm.org, Owen Ambur <Owen.Ambur@verizon.net>
- Cc: 'Alejandro Revuelta' <alejandro.revuelta@ximdex.com>, George Bina <george@oxygenxml.com>, 'Robin LaFontaine' <robin.lafontaine@deltaxml.com>, Betsy Fanning <bfanning@aiim.org>, public-change@w3.org, Joe Carmel <joe.carmel@comcast.net>, 'Paul Maassen' <paul.maassen@opengovpartnership.org>, 'miska knapek' <contactmiska@knapek.org>, 'Owen Ambur' <Owen.Ambur@verizon.net>, 'Crispin Butteriss' <crispin@bangthetable.com>, 'keefe murren' <keefemurren@gmail.com>, 'Joseph Foti' <joseph.foti@opengovpartnership.org>
re: XML Change Tracking / Acronyms / Open World Assumption / Semantics My Take ... background ---------------- When Gutenberg invented the Printing Press the commercial innovation which was crucial to acceptance was not the Press, it was the similarity of the font to Illuminated Manuscripts, the only book format available at the time[1]. This presented a commercial challenge to Scribes but not competition to Civil Authority Functions. ----------------- Data Processing for the convenience of Computer Science and IT has outlived its usefulness with respect to data analytics collection. The no-style style of XML requires that "changes" both track and echo originating domain (community) conventions. Governments have government expert friendly conventions which override complete freedom of response in the policy feedback loop (The Open World Assumption). So, analytics suffers, and policy suffers from lack of coherent feedback. It is possible to echo the limited number of coherent responses (user feedback) a domain might expect with XML, but not possible to compile translation tables with semantic methods. For example, many Americans speak English, but speak a basket of 100+ languages in the home. How many different language codes must a domain recognize as a property of coherent feedback ? Three choices at most[2]. For example, http://www.rustprivacy.org/2015/stratml/eckode/ These two tables for language codes are complete for every two and three letter code in the ISO 639 Specification. Mouse over the entry to see details. These tables could be used for anonymous compliance with domain conventions. This is something different than user anonymity and does not involve user identity protection; encryption, user accounts, etc.. Data analytics are facilitated by the lower table - reply in (any) known language. This amounts to a raster scan of the "code keyboard". The upper table is a vector scan of the same keyboard. The resolution method is general ... with this caveat: When you see one keyboard, you are seeing 26 different name spaces. e.g. http://www.rustprivacy.org/2015/stratml/eckode/CommunityVector.xml ... and each keyboard has 676 keys per name space http://www.rustprivacy.org/2015/stratml/eckode/Community.xml This is for the "_S:" name space - the venerable Dewey Decimal System (Base 26) - for the convenience of Record Keepers and Feedback Readers. --Gannon [1] Although this is a work of Fiction, "at the end of the day" it must have happened something like that way ... http://www.gutenbergsapprentice.com/ [2] Experts need translation services, but the other drivers on the Information Superhighway all speak "horn".
Received on Tuesday, 16 June 2015 18:56:43 UTC