I agree fully with Andrew with respect to deciding what the purpose of the BoK should be. To help with this discussion here are links to the Project Management (PM) and Management Consulting (CMC) Bodies of Knowledge:
PM - https://www.wrike.com/project-management-guide/faq/what-is-pmbok-in-project-management/
MC - http://www.icmci.org/download/?id=17672628& and http://www.icmci.org/download/?id=6972570 and http://www.imcsa.org.za/LinkClick.aspx?fileticket=L3Oanb3yE2g%3D

I provide these two bodies of knowledges as examples of what might be rather than something that should be copied.

Ken


On Fri, Nov 18, 2016 at 3:57 PM Andrew Hughes <andrewhughes3000@gmail.com> wrote:
Hi BoKkers - to follow up on Thorsten’s agenda email for the first meeting...

Due to the limited timeframe we have for this, we need to have a very strict 'scope of work', while the outcome should enable (us) to start the 'real' and detailed work on a BoK. My personal opinion is that a Taxonomy/BoK should be a 'living document', which will never be completed or finished. In analogy to a software product, in the future we might have major versions of a BoK, but also minor updates between them. 
Staying in that analogy, the current subgroup's goal could be to deliver a higl-level view on the 'Product' and suggestions on how to build and maintain it, eg with a BoK-Workgroup in Phase 2.

I think we’ve got to figure out a high level description of what kind of content detail should exist in the BoK during the creation phase.

Are we expecting to see hierarchies of concepts and terms with
- some text that an editor curates?
- a list of reading sources/links?
- citations from specific publications?

We do need to clarify the Purpose as well - is the BoK a compendium of concepts and facts that an ID Professional should know (not everything to all depths, but an identifiable subset); is the BoK a job-practice catalog (things ID Pros know how to do in specified job roles ?); is it a general practices catalog (articles/material that describe common/best practices for subjects)?

Or, what?

Andrew Hughes CISM CISSP 
Independent Consultant
In Turn Information Management Consulting

o  +1 650.209.7542
m +1 250.888.9474
1249 Palmer Road,
Victoria, BC V8P 2H8
AndrewHughes3000@gmail.com 
ca.linkedin.com/pub/andrew-hughes/a/58/682/
Identity Management | IT Governance | Information Security 


On Fri, Nov 18, 2016 at 12:48 PM, Andrew Hughes <andrewhughes3000@gmail.com> wrote:
Sounds good - thanks for getting started quickly.

Everyone, please look here:  http://kantarainitiative.org/confluence/display/idpro/Calendar  for a google calendar for the ID Pro DG meetings. You can also subscribe to it for convenience.

andrew.

Andrew Hughes CISM CISSP 
Independent Consultant
In Turn Information Management Consulting

o  +1 650.209.7542
m +1 250.888.9474
1249 Palmer Road,
Victoria, BC V8P 2H8
AndrewHughes3000@gmail.com 
ca.linkedin.com/pub/andrew-hughes/a/58/682/
Identity Management | IT Governance | Information Security 


On Fri, Nov 18, 2016 at 12:37 PM, Stu Lincoln <stu@stulincoln.com> wrote:
Great, looking forward to working with you. Absolutely agree on the strategy as well.

Stu

On Fri, Nov 18, 2016 at 3:51 AM Thorsten H. Niebuhr [WedaCon GmbH] <tniebuhr@wedacon.net> wrote:

Good Morning everyone!

The BoK /Taxonomy-Subgroup will do its initial Meeting on

November, 21th (Monday) ; 5:30 PM UTC

Stay tuned for the conference details!

May I ask to complete the following before

  • Sign up for Kantara Wiki (and/or Slack)
    • I think it makes sense to have access to the official Kantara Wiki, even if we decide to do stuff in Slack
  • Check out the agenda (some ideas from my side based on the discussions we had so far)
    • final agreement on collaboration tool
    • Discuss Roadmap for the Bok
      • Phase 1 (Feb 2017): Purpose, Audience, Highlevel Knowledge Domains, 'BoK-Workgroup'
      • Phase 2 (tbd): building the required 'infrastructure' for a BoK-Workgroup
      • Phase 3 (tbd): tbd ;)
    • Final Agreement on Meeting Schedule for the SubGroup

Some further thoughts on the 'phase 1':
Due to the limited timeframe we have for this, we need to have a very strict 'scope of work', while the outcome should enable (us) to start the 'real' and detailed work on a BoK. My personal opinion is that a Taxonomy/BoK should be a 'living document', which will never be completed or finished. In analogy to a software product, in the future we might have major versions of a BoK, but also minor updates between them.
Staying in that analogy, the current subgroup's goal could be to deliver a higl-level view on the 'Product' and suggestions on how to build and maintain it, eg with a BoK-Workgroup in Phase 2.


cheers,

Thorsten



--


Thorsten H. Niebuhr
tniebuhr@wedacon.net / tniebuhr@wedacon.de

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

_______________________________________________
DG-IDPro mailing list
DG-IDPro@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-idpro



_______________________________________________
DG-IDPro mailing list
DG-IDPro@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/dg-idpro
--
Kenneth Dagg Independent Consultant Identification and Authentication 613-825-2091 kendaggtbs@gmail.com