To: Paul Fiondella who wrote (27258 ) 7/1/1999 12:17:00 AM From: Scott C. Lemon Read Replies (1) | Respond to of 42771
Hello Paul, There are a couple of issues that need to be considered for this to work, but it is completely possible. > If I store that information in my digitalme identity vault, or if > that is done for me automatically, the first time I register > anywhere, then I'm ready to go to any online trading site and IF > POSSIBLE SKIP THE FORM FILLING, provided I can access the online > site and send them the data in a way they can understand. Enter > XML. There are issues with compatibility with existing web servers, and existing web browsers. I can't comment on what digitalme will or will not do, however for your scenario to work the browser would have to know how to post only the XML data, or a separate client would have to do so. Existing browsers will want to POST the entire filled in form. This is why the ECML chose to first do the "standard naming" approach ... it works with the existing environments. > I go to the online broker site. I go to the registration screen to > open a new account. If my digitalme application recognizes this > site, and can communicate with it in XML, a button pops up --- > register with digitalme. This could be done ... it would require the client application (whether installed or run as an applet) ... > If I click on the button, the data from my digitalme identity vault > is transmitted in response to the XML embedded in the online > brokers registration screen and I skip the form filling. At BrainShare there was a demonstration of technology where the information was pulled from digitalme, and the form was filled in for you. So you would see the form, filled in with your information, allowing you to change or correct, and then you would submit as normal. If the client application talks to the web site directly, then the brokers site would have to be expecting a POST to their web server of XML data. This could also be done ... One of the biggest issues is legacy web sites and browsers. Keeping compatibility during the rollout of new technologies is always going to be an issue ... Scott C. Lemon