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.
Example of IMS Record
select id_ims, imsname from ims order by imsname, id_ims select imsname from Ims where id_ims = #NextId# select imsname from Ims where id_ims = #PreviousId# select * from ims where id_ims=#url.id_ims#
Name : #imsname#
| Evaluator : | #Evaluator# |
| Organisation : | #Organism# |
| Date of evaluation : | #dateformat(Dateofevaluation, "dd-mmm-yyyy")# |
| Sources of information : | #Reference# |
| Version : | #Version# |
| Manufacturer : | #Manufacturer# |
| Nature : | #Nature# |
| Country : | #Country# |
| Regions : | #Geogscop# |
| Language : | #Language# |
| State : | #State# |
| Open/Closed : | Open IMS: the identities work with several systems or applications. Closed IMS: the scope of the identities is restricted to the IMS context. |
| Requirements : | #Requirement# |
| Number of users : | #Userbase# |
| Standards : | #Standard# |
| Description of Server - Side components : | #Server# |
| Description of methods : | #Control# |
| Descriptor of Client - Side components : | #Client# |
| Seals : | Yes: Privacy and other seals that certify that the IMS applies to law. No |
| Which seal : | #Whichseal# |
| Third party : | #Val3rdparty# |
| Which third party : | #Which3rd# |
| Features : | #Features# |
| Screenshot picture : |
|
| Flowchart : |
|
| Price : | #Price# |
| Comment to the Cost : | #CostComment# |
| Type of IMS : | Type 1: IMS for account management. Type 2: IMS for profiling of user data by an organisation. Type 3: IMS for user-controlled context-dependent role and pseudonym management. |
| Class of IMS : | Class 1: Pure IMS which main objective is to support or implement identity management functionality. Class 2: Systems/applications with another core functionality. Class 3: Systems/applications which are independent from identity management functionality.
|
| Functionality : | #IMSFunction# |
| Suggestions : | #Suggestions# |
Every effort has been made to check the information shown with the manufacturer. Nevertheless errors may remain. If you would like to change any part of this record, please send your comments to the IMS team. |
27 / 53 |