Things change
when country A decides to issue eIDs that contain ?¬?rst name,
last name, home address, and blood type packaged in a certain
way and communicated using a custom HTTP message. The eID
from country A will work only with adequate software on the
client machine that is able to read the data from the eID and
inject it in the right stages of the message ?¬‚ow. The targeted
service will also need to be aware of the differences of the approach;
otherwise, it will not be able to make use of the incoming
data. There are no guarantees at all that country B will adopt
the same system or will even be willing to create services that
are A-eID aware. There is really no judgment implied about
whether the eID from A is better than the one from B. They can
both have exceptional technical merits and solve beautifully the
problems they were designed to address. Unfortunately, the
sheer fact that they are so different is a problem when considered
from a global-scale perspective. This, added to the wide
variations in form factors and requirements, is a sure recipe for
complete incompatibility. Should the hard token idea, as described
so far, be truly successful, you would witness rather
bizarre scenarios.
Pages:
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135