John, John Merrells wrote the following on 04/10/2006 11:46 PM: > Based on feedback and contributed text I've revised the > draft use cases document. > > Added: > > 1) More browser based use cases. In particular many examples of 'claims'. > 2) Rob and Lisa's non-bowser based use cases. > 3) Brief introductory section on goals of the group. > > Further comments / contributions are most welcome. It was a good idea to have a use cases document. It makes things clearer for the ongoing discussions.
I have few clarifications/comments on the use cases.. B12 - Where does the agent live? B8 states that the agent is integrated to Operating system. If so, can we expect the agent will be available even in a computer in the internet caf'e? ( or Is it left to the implementation of the agent? ). Where does the agent get Beths identity data? Is it stored remote or something that she can carry around with her? If so, how does she transfer it to the agent? ( usb, smartcard or something simiar? Is it again implementation specific? ) B17. A mention of how identity agent can be administered will be good. For eg. how does she inform the agent if she switches the insurance provider? B19. This is use case suggests that the identity data may be stored remote so that any device can retrieve the data. The same adds a constraint that user needs to have access to online identity data always. This may be difficult if the agent is expected to acquire the claim and present to local applications in her computer ( for eg. local mails ) while she is not connected through her ISP. B27&B28. Not very clear on what we are trying to convey here in the context of identity agent. It appears to be the current problem if the site doesn't store a cookie when Adam visited first time.. ( I may be missing something. ) Thanks --jaimon _______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
