10  EP 1 499 940 B1 9  FIG. 7 shows an illustration of another form to be presented to the user which form is half-fin- ished. FIG. 8 showsa schematic illustration ofan extension of the first or third embodiment allowing au- thenticity of the client application. FIG. 9 shows a schematic illustration of the system where one client application interacts wit several location entities. FIG. 10 shows a schematic illustration of the system where an identity-related information is pro- vided by a further location entity and is ob- tainable bya requestingentityvia the location entity. [0040] The drawings are provided for illustrative pur- pose only and do not necessarily represent practical ex- amples of the present invention to scale. [0041] The following are informal definitions to aid in the understanding of the description. [0042] Person:  An entity whose identity is managed. If the person acts it becomes the user. Typically the per- son or user isan individual,but at least smallbusinesses will often interact with other businesses just like individ- uals, e.g., in travel booking and information gathering. [0043] Requesting entity:  An entity, e.g. an organi- zation represented by a server, who wants to know a name or attributes of a person. Initial organizations will mainly be Internet shops because of the low assurance of any easily deployable registration system. In the long run, organizations include all a person’s communication partners suchas banks, doctors, colleagues, and family. Colleaguesand familyas"organizations" areparticularly relevant if one wants to include contact or location infor- mation in identity management, e.g., instant messaging and calendering. [0044] Location entity:  An entity that stores identity- related information for a person. The location entity is also referred to as wallet. By location entity or wallet is meant a component, typically software, that stores and handles personal information for the person. A location- entity holder may be the person itself or a party trusted byit. Becoming a professional location- entityholder may require preconditions, e.g., privacy and security promis- es and appropriate safeguards. A primary location-entity holder holds a person’s single sign-on password; more generally, it can recognize the person without interven- tion of another entity. Thus a person might have several primary location entities with different types of informa- tion, if he or she can remember several passwords. A local location entity  is on a computer of that person. A remote location entity  is on a computer or server of a [0048] With reference to Fig. 1, the general layout of a communication environment is described in which the invention can be used. In the figures, same reference signs are used to denote the same or like parts. Fig. 1 shows a person P, who acts as a user 20. The user 20 executes a client application 30, e.g. a web browser, on his computer. The client application 30 is connected for application-dependent interactions to a requesting entity 50, e.g. a server of a company or bank which provides services. The client application 30 and the requesting entity 50 are connected via communication lines 5 as they are known in the art. The communication lines 5 are usuallyprovidedthroughanetwork, e.g.the Internet. The client application 30 is further connected to a location entity 40, also referred to as wallet, whereby the location entity 40 can be local, i.e. at the computer of the user 20, or remote, i.e. on an external server or the like. The lo- cation entity 40 is also connectable to the requesting en- tity 50 for the transmission of identity- related information IRI. Under the term identity-related information IRI is un- derstood any information related to a person or user. Identity-related information IRI comprises names, ad- dresses, group memberships, authorization credentials, demographic data, personal preferences, calendar en- tries, medical and financial information, and everything else that may be stored digitally about a person or under a user name. The requesting entity may desire it for ac- cess control, authorization, personalization, authentica- tion, login,commercial, medical, or governmental issues, or any other application operating on identity-related in- formation IRI. The scenario in Fig. 1 is shown to facilitate the description of the following flows for providing the identity-related information IRI tothe requestingentity50. [0049] Fig. 2 shows a schematic illustration of a mes- sage flow of a first embodiment. Therein, the flow be- tweenthe client application 30,the locationentity40, and the requesting entity 50 is depicted with labeled arrows to which respective Roman numbers are assigned. Fur- [0047] The term  computer  includes devices like PCs butalso digitalassistantsandmobile phoneswithbrows- ing facilities. [0046] A legal entity or organization may act in several of the roles as described above. [0045] Federation: By a federation, one typically meansagroupofprofessional location-entityholders and location-entity manufacturers. The group may also con- tain representatives of persons and organizationsto help with generally satisfactory standards, but persons and organizations may be millions, while entities interested in professional location-entity holding might be tens of thousands, e.g., banks, CAs (certificate authorities), ISPs (Internet service providers), and large employers. separate location-entity holder, typically professional. It may be integrated with other location entities residing at that holder. DETAILED DESCRIPTION Glossary 6