Return to Theretical System

The following issues are associated with the theoretical DIDO Identity workflow:

1. There are no Technical or deFacto standards that cover the use of Identities on a DIDO. PII Secure Smart Contract (PIISSC) is theoretical. This doesn't mean that one can not exist and that ll efforts to attain one should be abandoned. Instead, the PIISSC should be used as a starting point. One thing that it is lacking is a direct command interface. Currently, there are two ways to control the PIISSC, using questions and using Rules.
2. No government agencies are currently supporting a PIISC. However, the Trusted Traveler programs could help resolve this quickly by using a DIDO to hold the information rather than a server. Servers are subject to Security Breach, Data Breach, network vulnerabilities such as Denial-of-Service (DoS) or Disconnected, Intermittent and Limited (DIL) environments caused by remotenes, sunspots tr other disruptions to networks.
3. Adding PIISSC to existing Known Traveler programs such as the USA's TSA Pre, Global Entry, Nexus, Sentri or FAST https://github.com/blockchain-etl/ethereum-etl, Germany's EasyPass https://www.cntraveler.com/story/how-to-get-through-european-customs-quickly, the UK's ePassport, Netherlands Fast Low-Risk Universal Crossing (FLUX, Australia's SmartGate System, Korea's Smart Entry Service, Asia-Pacific Economic Cooperation US APEC Business Travel Card Program. ¹⁾
4. Adding PIISSC to existing Loyalty Programs. Wikipedia provides a long list by geographic area of different programs. Having a shared Identity program should help all the participants in Loyalty programs²⁾
5. Many localities have combined access to mass transit (busses, trains). Paris has the https://en.wikipedia.org/wiki/Carte_orange | Orange Card]], London has the Oyster Card, and New York is starting the One Metro New York (OMNY) card https://en.wikipedia.org/wiki/OMNY
6. Ridesharing companies such as Uber and Lift https://en.wikipedia.org/wiki/Ridesharing_company