Resources
Identity Use Cases & Scenarios.- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- Profiling.
- Forensic Implications.
- HighTechID.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- D1.2: Communication Infrastructure.
- D1.3: Wiki System.
- D8.3: Database on Identity Management Systems and ID Law in the EU.
- D8.5: Report on inter-disciplinary workshops.
- D9.1: A Specification for FIDIS Journal.
- D9.5: 1st FIDIS in-house Journal Issue.
- D15.2: FIDIS International Summer School.
- D15.4: Interdisciplinary FIDIS Doctorial Consortium.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
 |
Title: IDENTIFICATION OF IMS |
 |
This section of the database is for the purpose of providing a general overview. There are some attributes that may relate to later ones, but the objective is to gather all the information that serves to identify the IMS. Users can search by name, by provider, by country or by state of development.
Attribute Label | Definition | Values |
Name | Name of the IMS | Text |
Version number | Version of IMS | Text |
Manufacturer | Main manufacturer or provider of the IMS | Text |
Nation | Nation of the manufacturer’s location | Text |
References | Sources of information, links, etc. and the IMS version number to which references refer, if possible avoiding ‘marketing information’. | Text (including hyperlinks) |
Supported languages |
| Possible values (more than one can be selected): Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Italian, Latvian, Lithuanian, Maltese, Polish, Portuguese, Slovak, Slovene, Spanish, Swedish |
Closed/Open IMS | “Closed IMS” means that the scope of the identities is restricted to the IMS context. “Open IMS” means that the identities work with several systems or applications outside the IMS. | Enumerated: Closed, Open |
Closed/Open Source (*) |
| Enumerated: Closed, Open |
State of deployment | Statement whether the IMS is an available product or a service on the market (Available) or if it is a Prototype, a Suspended prototype, or just a Concept. | Enumerated: Available, Prototype, Suspended prototype, Concept |
Distribution (*) | If the IMS is available, then this field should be filled in to state whether the IMS is sold commercially, distributed through shareware, freeware or is part of the public domain. | Enumerated: Commercial, Shareware, Freeware, Public Domain |
Geographical scope | Regions where the IMS is available | Enumerated: National, European, Global |
Platform and environment
This section would include data allowing users to search by hardware or software solutions and to search for IMS which adhere to a certain standard, e.g. Liberty Alliance.
Attribute Label | Definition | Values |
Hardware / software requirement | Description of the hardware, software, operating system and services the IMS requires | Text |
Installation base IMS | Number of users of the IMS | Text |
Installation, maintenance, use (*) | Brief description of the installation process and use of the system if the system is a commercially available one. | Text |
Modularity (*) | Modularity means that the routines are grouped into independent, distinct blocks (modules) within each service area defined by the system architecture. In addition, each block has a single function and well-defined parameters and interfaces. | Boolean: yes / no + text |
Market availability (*)
| Description of the system availability. The ‘state of deployment’ attribute in section above is described here with text. For example, if the IMS is currently a prototype, this field might provide an estimate of when the system will be available.
| Text |
Interoperability / standards | Description if the IMS can be used with other applications and systems. This could be achieved by using standards like protocols for communication. This field will include the standards that the IMS adheres to, e.g. Liberty Alliance | Text |
Guarantee of trustworthiness (*) | Description of the guarantees for the trustworthiness of the system. This is not obtained to the single functionality, but to the entire system and mainly to the trustworthiness of the manufacturer. Seals of third parties may be described here. | Text |
Legal and contractual framework (*) | Description by providing references of the legal and contractual framework of the IMS and the manufacturers.
| Text |
Server-side component(s) | Description of the server-side-components (data-storage and processing) | Text |
Client-side component(s) | Description of the client-side-components (data-storage and processing) | Text |
Description of Methods | Description of methods (e.g. encryption), how the control of the user over his identity-related data is established with respect to availability, integrity and confidentiality. | Text |
Description of functionality / features (client and server) | What is the characteristic / speciality? Handling of identities? Use of pseudonyms / roles? Support of anonymity? Use of electronic signatures / PKI? Storage of data? Handling of accounts? Password management? Security / encryption, etc.? Data protection? Privacy Enhancing Technologies? Data minimisation? Support of law enforcement? Usability? […] | Text |
Seals | Privacy and other seals that certify that the IMS applies to law. | Boolean: yes / no + text |
Support by third parties | Description of which third party or intermediary support is integrated, e.g., certificate providers, IMS providers, delivery services, payment services, … | Boolean (yes/no) + text |
Nature of provider / distributor | Description of the nature of the provider of the system. (e.g. public, private, regional, national, international) | Text |
Flow chart | Shows how data is processed within the IMS, which parts are involved. | Picture |
Screenshot | One screenshot | Picture |
Cost
Only the first field has been included in the prototype as data is not available on the other fields and it would be difficult to provide reasonable estimates.
Attribute Label | Definition | Values |
Purchase/Licence | Purchase cost in EUR | Real |
Purchase cost comment | Any additional information on the field above | Text |
Deployment (*) | Estimate of deployment costs excluding purchase/licensing costs included above | Real + text to describe costs included in this category |
Maintenance (*) | Estimate of average maintenance costs | Real + text to describe costs included in this category |
Training (*) | Estimate of costs of training users | Real + text to describe costs included in this category |
Technical resource requirements (*) | Description of the technical resources that are necessary, pointing out the number of people needed for operation and the costs. | Text |
| |
   |
|
| 15 / 53 |
