Hi (BoKkers) Group, during todays meeting (minutes here <https://kantarainitiative.org/confluence/pages/viewpage.action?pageId=85492564#MeetingMinutesTaxonomy/Bokkers-Meeting20161212>) we decided to discuss the Toplevels and each of their 4 sublevels in more detail. To speed up the process and by triggering the group, I will create 4 Mailthreads for each toplevel to be used for discussion. Each of these Mailthread should, *best by next monday* * have *found a 'leader'* who will take responsibility for the discussion * have found *4 sublevels* (so 4 areas that can be used to further sort processes, terms, knowledge,etc)*within the given toplevel* * have seen a *great level of discussion* For sure the most important part here is to find someone who will lead and drive the discussion, or is even willing to take over one of the areas on his/her own. So if you can spent 1-2 hrs of your available time, it would be much appreciated! The _first mailthread is the one you are reading here right now_, the others will be 'Management', 'Authentication', 'Authorization'. Thnks for your contribution Thorsten Niebuhr
Hi all,
During todays meeting (minutes here <https://kantarainitiative.org/confluence/pages/viewpage.action?pageId=85492564>) we discussed further refinements for the Dart- Board-Model, especially on the 'upper layer' which deals with Identity Management topics only, while relying on the lower three layers for operation,implementation,planning.
Our next goal is to 'slice the cake', to find sublevels to the four TopLevels we decided to start with so far. The sublevels mentioned below (in green) are just examples.
The best case scenario for this would be to find four generic terms within each of the TopLevels.
* Identification Processes around validating identities (digital or physical) and as the 'entry'/'leave' point on a given domain.This does NOT deal with Authentication! o Proof/Verification o Register o De-Register o Data Portability (Transfer) * Management Processes around the management of Identity Data o Enrollment o Dis-Enrollment o Privacy o Federation * Authorization Processes related to Authorization o ... o ... o ... o ... * Authentication Processes related to Authentication o
o ... o ... o ...
Finally, to check the validity of the model, we will investigate typical IAM-Topics if we are able to find appropriate paths to describe the given topic in the model.
here is a quick example on how I think this model could be applied (example used: 'Identity Provider')
* Function of an 'Identity Provider' o Needs to offer functions from 'Identification' to + *validate* a given Identity against real or other digital data + Following *Process* ABC + using *technology* XYZ + ...further definitions on the *lower* layers (Operations, implementations,planning) + (do we need to add a*layer for legal* aspects?) o Management + ... o Authorization + ... o Authentication + ...
So the Task (especially for those who gave their commitment to the BoK/Taxonomy) is to
* Find propper sublevels as described above * exercise typical usecases from the IDM World against the model
Thanks in advance,
for the BoK-Subgroup
Thorsten
--
Thorsten H. Niebuhr tniebuhr@wedacon.net / tniebuhr@wedacon.de <mailto:tniebuhr@wedacon.net>
WedaCon Informationstechnologien GmbH Office: +49 (251) 399 678-22 Fax: +49 (251) 399 678-50 Mobile: +49 (174) 991 257 4 Kroegerweg 29 D-48155 Muenster http://www.wedacon.net
Amtsgericht Muenster HRB 6115 USt.-ID: DE216758544 StNr.: 336/5775/1487 Geschaeftsfuehrender Gesellschafter: Thorsten H. Niebuhr
_______________________________________________ DG-IDPro mailing list DG-IDPro@kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/dg-idpro
