Skip to content

Latest commit

 

History

History
460 lines (399 loc) · 22 KB

README.md

File metadata and controls

460 lines (399 loc) · 22 KB

... Public

2024

...

2023 quickLinks

  • https://github.com/HwWobbe/DefinitiveData-DeltaAlerts#-2023-07
    • review the server offer
      • do this as quickly as possible to gain architectural insights
        • produce a merged document from working with JrH
      • then: consider the relative merits of yet another TiddlyHost wiki
  • try making this block of text into a separate file
    • (auto)merge when possible
      • review the avialable tutorials

2023

  • ...
  • make the SoW.HotTo available throughout DataFix, after a GsdT review
    • run this by DelDf first, perhaps as a basis for a Job Description for a Co-Op with Derrick.
      • Devs should share "onBoarding" tasks
  • Define and Conduct some Code Reviews
    • ...

-09-

  • AssertiveWIFM additions for RichardC

    • ...

  • Suggest our "limited preferred scope" (Movers Maintenance) to Richard.

    • incorporate whatever presentation / leave/Behind material that can be crafted
      • review draft #1
        • is this summarized as effectively as possible
          • send V1.0.2 to Richard
          • ask about Ernest
            • proposal writing - idf a contractor - perhaps unsolicited
              • confirm Gsd aggres since he may leak to smartmatic
      • distribute this to at least Andrea and perhaps Ls, but not necessarily Lz at this time

  • start documenting Docker considerations

    • link this to CoOp recruitment
      • build Staff Expertise retention > Ownership paths

  • try building as much as possible in XememexH - but "spit-balls" belong in XmmXH (public/private)

-08-

...

-08-/GitHub

  • test a port of this material into:

    • GitHub wikis (WikiPedia syntax)
    • TwH repositories

  • review and extend the creation of Issues

    • Define and Conduct some Code Reviews
      • ...
      • level-up Data-Integrity

  • Architectural issues need consideration as part of a 20th anniversary splash in 2024-09

  • remove Deferred content to a trailing SymbolsH page that can be reached via quickLinks

    • an alternatative could be to refert to just Numeric titles

  • start to identify more Issues only as the emerge.

    • this needs to be added to the formal EdD notes to reinforce Methodology
    • Confirm links to headings in deeper files in this (and other) repos. Then remove.
      • improve use of Breadth

  • review and extend the creation of Issues

    • ...

  • a leading .../.mo(nth) heading should be useful

    • this could expand to include all of the timePeriods
      • try -08-

-07-

-07-31
F.C.R.

  • confirmed 6 heading levels ####### level 7 is a FAIL

  • find the assigned SymbolsH instances

    • (Queue) .ye.m0.da
      • ...

  • expand the existing explanations of Significance-Precision

    • then start adding the .mi.ce.de.ye levels and their symbols

2024:

  • ㋀㋁㋂㋃㋄㋅㋆㋇㋈㋉㋊㋋ extend with the .ye values

2024-12:

2023.c(alendar) v. 2023.f(iscal)

2023-08:

  • Can Notion be more useful with the Marketing team?

    • discuss this with LzH
      • then direct AJo
      • test this technology with LsH too

  • review the GitHub/ Packages / Docker material that can be accessed from the main Profile

    • csyW activities might be interTwingled

  • review https://tids-to-table.tiddlyhost.com/

    • remove this block to ...wip...

  • engage more thru GitHub starting with the Real Estate schemas which I want to present as an Address Maintenance component

    • the clear intent should be to build towards MyData and use of the emerging government components

  • consider the extent to which GitHub may be useful in crafting content that is destined for TiddlyHost

    • try moving GitHub content into a DiigoH outliner
      • this could make it easier to re-arrange to show the relative priorities
      • furthermore, TransClusion van be used in TW environments to create more informative sub-contexts

  • relative coloring may appear to cause unexpected changes in the higher levels

    • code mirror could be useful
      • this may only be effective if non-code shemes cab implemented

  • track the evolution of the 4th repo

  • foreign travel preparations - that are likely to need two weeks late August or early Septemder

  • try using DiigoH to "outline" the proposed trip

  • remove content to /2022/...

  • craft a " DeferedForNow / DeferredUntil " page

㋆ 2023-07:

  • inform JrHw re FriDay as an "if possible" time.
    • do this via a XmmxH post (even if that is sent via an email)
      • strive to refine communications
        • discuss Jeremy's preferences: RSS , PmNotes that are triggered via a hared GitHub Comment *
  • consider Tw & MySql
    • a solid AdMan business case is emerging
      • Mover Certification + ...
        • customized Data Augmentation via GeoSpatial sources
      • Identity Device collaboration
        • YOTI ElectOnApp augmentation
          • this should be refactored to share the common text
  • create a new Folder based solely on the Chat response (as a test of ChatGpt)
    • find ChatGpt users on GitHub
      • confirm that one of the versions can actively process GitHub activity
    • manual maintenance is useful
  • http://www.i18nguy.com/index.html
    • needs exploration annotations
  • extending the strainghtSeven streak / highWater
  • 26 /7 was noted and trigged a switch in updates to this secondary Goals file
    • edit will continue here to test the relative relationship with the third file

㋄ 2023-05:

  • Craft an improved archive plan
    • test the gitHub wikis via RstH

Done:

  • leap-frog over the shared HelloWorld
  • observed that the Updates density is a relative effect
    • try to preserve the evidence of this. in spite of the adjustments caused by further Changes
      • proceding carefully ...
        • note the color differences bewteen April and March

㋂ 2023-03:

  • Tweaking Data acquisition methodologies:
    • starting with the development of a set of illustrative prototypes against Known values (as test cases)
    • consider this in a TftDf context
    • explore the relative value of Xememex or a DataEntry.Curbside modification.
      • ...
  • agreed that it is best to re-schedule the Xememex Group presentation until early April.
    • individual focused presentations may be helpful
      • LsH
      • LzH
        • review the shared work
  • ( .tn: record the lowest color breakPoint, .likely > 6 .then. > 12 ... )

㋁ 2023-02:

  • Data provisoning will be delayed by a need to tweak Data acquisition methodologies
    • -24: evident Preliminary improvements are sufficent to proceed.
      • TechTeams are converging on the use of GeoJson.
        • review the goal of extending the use of Open Soource concepts.
          • discuss this with DanG.
    • Address Accuracy processing will be incorporated to optimize Capture.
  • consider expanding Sponsorships
  • ...

㏠# 2023-01:

0.2 (emerging) Contents (via quickLinks)

2022-12:

  • Integrity is an effective Topic for Df Audiences.
    • Expand the recent problem(s) to assess the extent of reactions
      • show how Definitive Data ( DefData ) is a key part of Modernization
        • test thia in the new blog
    • how can AndreaJo aid in clarifying this?
      • Copy-writing
        • team of LS LZ AnJo Kyle
      • opinion survey?

Investigating Teranet (data) Quality, Usefulness and Appeal:

  • Problems are increasingly apparent as:
    • matching algorithms based on Municipal street address
    • incomplete coverage becomes more apparent from increased usage
    • reported errors (and whole classes of types of errors) are not remedied
  • Discuss Data Integration plans & API access possibilities
    • perhaps this should have an initial scope of Ontario
      • consider this in the context of the TFT potential work
    • consider Flickr for global scope.

2022-11-: Due times

  • use PlusCodes in the current EonRh investigation
  • Black/White Hat duesl will persist, especially given the rates of Technological Changes
    • Professional BlackHats are patient enough to nurture a seed attack
      • Penetration productivity suggests "low-hanging fruit" is more vulnerable
  • Discuss TwCommunity newco with Jr

2022-10-: Due times

  • -10-31: priority review(s)

Slack:

  • review -09- Notes

Mehregan:

  • Mehregan productivity continues to compel attention
    • This is likely to be a protracted adoption since it is still Version 0...

2022-09-: Activities & Notes

  • -09-29: unprecedented DbServerD recovered. Distraction ends.
  • -09-25: re-balancing 'Planning' and 'Doing', mindful of GTD
    • Considering the (less Pulse) use of GISTS
  • Continue to restructure this material into Reports for each group of participants.
    • add more Topics
    • start to incorporate Anki
      • introduce Anki to aid occasional colaborators
        • some Teams types may find this useful
  • -09-19: review https://docs.github.com/en/pages
    • distinguish the uses of GISTS and Repois
  • -09-09:
    • -09-05: testing the new uses of Slack
    • recommend AdManCa hire a couple of interns.
      • structure these evaluation jobs for junior or master levels.
  • spawn a portion of this README as a separate file in the AdManCa repos ; retrieve and incorporate via a PR.
    • confirm or refute: a File is the elemental first-class unit of content for PRs.
    • -09-01: one way of determining any file size limits that might apply is to simply start building larger consolidated files that can be accessed via the prioposed IndeX file
      • it may also be effective to pull the repo down to a desktop and review the files in that environment
    • -08-25: Copyrights & TradeMarks considerations may be needed, in spite of Open Source committments.

2022-09: Topics: Conclusions:

  • GISTS can be used to reduce Pulse noise caused by frequent updates

Slack:

  • Ideally, Slack will help Focus on the most Urgent collaborative activities
    • Summaries will then focus on the most Important
      • more MarkUp use will also help this Focus effort
        • as might more use of Color
        • and inline Links
    • There are prequisite activities:
    • this may be accelarated by the development of a Slack messages prototype
      • -09-05: boot-strapping is underway.
        • it may be time to use Commits as Summary points rather than Activity points
          • review and revise the methodologies for localHost work
          • re-consider GitLab since Slack integration seems to be restricted to Organizations.

4. Introduction: > Background: > DoneTimes: 2022-09: ...

  • started adding Topics to these Notes

  • -09-03: started creating a Slack channel for the AdManCa Team(s)

    • strive to link these as effectively as possible
    • Notion may be an easier initiation path for less-technical collaborators

  • -09-01: ...

    • consider building an Index page that links to appropriate sections of other GotHub file like this
      • a simpler Git page might be more accessible

2022-08:

  • -08-22: a bit of a time crunch has been imposed, so daily Pulse comments may be reduced
  • -08-24: still crunched for the rest of this week

-08-20: checking the new TiddlyHub design

  • This slight changing in the use of titles seems appealing.
    • ( Splash with an image )SwAi? - in order to achieve PoTda ( standardized from PoTd )EdD
      • PoTda - P(icture) o(f the) Tda(y)
      • this type of pseudoCode is becoming more significant now that TW has:
        • SPLIT okperators for improved parsing
        • CASCADE logic rules

-08-21.

  • The use of Hypothesis as a reminder/workflow systemn seems effective.
    • this should still be drived by ( ControlPoint )TwH logic
    • Trying to annotate pages that need attention in a manner similar to that used at DebateGraph.
      • review DynaList too.

-08-16: a BlownAway.ByTiddlyWiki ( BaByTw ) contest is an idea worth exploring.

  • one possible focus is a melding of AdManCa credibility ; Google's OpenSource PlusCodes, YOTI - Your Own Trusted Identity
  • -08-15: Encouraging others to consider my interests in Identity Management products

-08-14:

  • Linking more possible collaborators in order to build out an Adress Management network that is interested in the DefData ("Definitieve Data") aspects of DataIntegrity and Election Integrity.
  • investigate: PRs as a Transclusion, more deeply since this is an obvious capability that should be in a SVC system

-08-11:

  • Considering e-wallet collaborations for Identity apps that need better Address information.
    • this may well fit into the proposed Voting Initiatives Laboratory infrastructure
      • active discussions and deliberations are underway

-08-09:

The majority of the maintenance having been completed, it is finally time to restucture this material for a diverse set of Audiences. Ideally, the use of a proper SVC will make this easy enough, so that it is possible to harvest some benefits from the infrastructure.

Start by:

  • trying to pull a small update into this repo

2022-08-2?:

Demonstrate the value of a modern Canadian Address Management infrastructure that can be use as a definitive reference for all possible Canadian Addresses.

DeltaAlerts

DeltaAlerts are being built as an infrastructure based on https://maps.google.com/pluscodes/

  • Investigate the potetial interactions between pulic/private repos via PullRequests ** The end product will be OpenSource, but working teams are likely to need some private Comment areas.

Drive Content creation via PullRequests.

...

2022-07-31:

Started to re-package this for ...Inititives.

① ...DeltaAlerts

2022-06-29: 'main' commit.

  • archiving of older material should be abe to proceed soon.

Lede

  • 2022-06-10: gradual (post Election) resumption
  • 2022-05-07: confirm: switched Master to Main ; Done: -05-01
    • found the Default control, but cannot rename to an already existing Name
      • perhaps now ?
  • 2022-04-07: switch Master to Main
  • 2022-03-25: https://github.com/organizations/Data-Integrity-Group/repositories/new
  • 2022-03-20: Just a bit of progress tracking to let folks know things are progressing (all be it very slowly).
  • 2022-03-05: enhancing pull Requests
  • 2022-02-12: engaged in work-break-downs to distribute proposed solutions more widely
    • Pob is P(lace) o(f) Birth which is expressed in many ways
      • Latitude + Longitude ; PlusCode (publicDomain encoding ) ; IATA code + vector ; Municipal Address ; postal Code ; WhatThreeWords (proprietary) ; ...
  • 2021-12-2?: starting work on legal aspects and considerations of Privacy for AddressManagement based on GeoCodes ...
    • particularly Open Source PlusCodes
  • 2021-12-18: hiHo, hiHo: ... it's back to work I go (if only for the imminent holidays)
  • It's more than time to re-focus this repository.
    • this is an opportunity to generalize the "5 minute rule"
  • TiddlyHost now creates new wikis as V5.2.0
  • re-assessing GitHub wikis
      • consider the very promising Hypothesis interactions
  • CjvCollaboration:
    • 2021.05: DefData source(s) focus
      • 2021-05-21: AddressAlias(es) table is showing progress in a Google Docs environment.
      • 2021-05-19: ...
    • 2021.04.01: Address fields review ; NodeJs idea?
    • 2021.03.15: startup
  • The potential ~rst collaboration on Housing:
    • An effective approach to WBS ( WorkBreakdownSystem ) should maximize the value of our indivdual contributions.
      • 2021.02.01: Confirmed pre-existing CB code will be useful and is readily availabe.
        • 2021.02.03: Received code. Now to try an install.
  • PlusCodes can be use to effectively join many independent databases that have geographic component
    • start to re-structure these notes so that they are more efficient for each specific Audience
    • use Diigo to create tightly focused contexts for this material
  • consider extending Joplin > Dropbox (with shared folders)
  • PlusCodes are very appealing
    • Part of the appeal is that they can be a masterKey to a table of Address Aliases & other tables with an AddressKey
    • a rigorous relativeValue to competing solutions is underway
      • googleMaps ; TeraNet ; ESRI ; What#Words ; ...
      • pricing is obviously set to encourage small, speculative developments
        • caching has a different meaning in this Price context
        • All is based on ApiKeys.
    • The "off-line" and "open source" facets are quite appealing.
    • confirm they are part of the standard API response
      • alternatively, increase latLon capture automation
    • Demos are now being developed
  • Several collaborative opportunities are evident in Canada.
  • review: https://isomorphic-git.org/
  • see https://github.com/HwWobbe/DefinitiveData-DeltaAlerts/blob/master/docs%20folder/Lede.md
    • consider hosting an instance of federati on Azure.
    • select an enthusiastic partner for the Vision 2030s AdManCa initiatives
      • this infrastructure build should strive for OpenSource logic
    • investigate ( JSON ) .../blob/...
  • re-focused on using TwElsWikis for shared Notes and Messages.
    • the merge of CurbSide and TiddlyTables is spurring new NamesRules.
    • expand the use of TiddlyTables
    • set Report esthetics
  • planning to try the Discussions capability

Privacy & Technology

Technology leads Legislation and the already large gaps are more likely to grow than shrink, given current trends. Individual Subjects should, therefore, consider their particular needs and views, as well as how to position themselves within the societies they are part of. This is particulary important given the current trends of moving data into the Cloud. After all, Facebook has clearly demonstrated that its approach to data collection is harmful to its users and that the Subjects who do not protect themselves will inevitably be just "collateral damage" to its business model.

Subjects are becoming intolerant of the need to protect themselves from privacy breaches at sites that collect and, when breached, expose Personal data.

In a programmer's view, DefinitiveData is simply the best available data for a particular algorithm. This "best" judgement is, of course, highly context sensitive, with many diverse opinions and vested interests, including those of many DefDataContexts that need reconciliation in order to optimize the value of required investment(s). Consider, for example, ...

  • Canadian Cities as the "owners" of Municipal addresses.

  • Canada Post (since most Canadians, incorrectly, believe Canada Post knows where they live).

  • Government Institutions at all three levels ( & especially the Voting Authorities )

  • Canadian Banks and their K.Y.C (Know Your Customer) needs

  • The National Association of Mail Users ( NAMMU )

  • Mailers ( and their mail services providers )

  • Mail Recipients ( likely a bigger market than Mailers, as junkMail grows and Privacy meeds increase > wikiLink )

  • AdManCa = Ad(dres) Man(agement) Ca(nada) & FirstNations

  • Standardization will be increasingly important as more Devs engage.

    • there is an Organization that sets Real Estate standards.
      • link pending
    • Address Quality issues are more widely recognized given recent ArtificialIntelligence and BigData hyperbole.
      • the American VoteByMail examples and opinions will be informative
        • DebateGraph may be an effective tool in the imminent political Debates.
    • Privacy issues are likely to demand more attention given the impact of CoVid19 on traditional Voting practices.
    • have a secure AWS vault created, that can be assumed via credentials.
      • pick a name
      • consider possible backdoors.

DefinitiveData-DeltaAlerts

The growing availability of data actually appears to be creating demands for even more data, almost as if a cyclone of data gathering forces is engaging to feed into the promise of Artificial Intelligence engines. One result of this whirlwind of activity is a dramatic increase in redundant data acquisition and data matching efforts. ...

  • A national Productivity issue with Identity implications, introduced at ...
  • (https://debategraph.org/Stream.aspx?nid=596285&vt=bubble&dc=focus)
  • Enumerate the fields of endeavour which will be increasingly affected by defData ...
  • ... e.g. Voting, Banking, ... = Identity protection and management ; MyRep ... R(ights) e(ntitlements) p(iviledges)
  • Review "Input Process Output" allocations of 40% 20% 40% respectuvely.
  • Expound the need for EnduringLinks to alleviate Matching problems
  • Discuss various Use Cases. Eventually these should be posted to LinkedIn.
  • GPS = latitude + Longitude, as opposed to (proprietary, per CPC) Postal Code.
  • Benefits need to be confirmed
  • CPC: URM cost savings
  • Discuss the reasons for Changes (Deltas) that should trigger "Alerts".
  • This should likely link to DgH to start and then DocsH
  • Preparing this file for sharing with CPC & NAMMU members.
  • link to gDocs and various documentation files tailored for specified Audiences.
  • debateGraph is being evaluated as a way of vizualizing MicroContent & MicroPortals that include links to Resonator.
  • incorporate (some Labels) examples

T(ime)p(ast)

  • ...
  • test IttyBitty's abilities with more sophisticated CSS and HTML
  • Commits registration confirmed.
    • now being integrated into workflows
  • see tasks:...
  • leaning towards (re)introducing Access for use by the less technical folks interested in participating in this project.

^