140 likes | 227 Views
SCC Workplan. C. Tilton. Press Releases. <boycott> The IDESG announces the availability of the IDESG knowledge base which provides access to a repository of information regarding online identity use cases, terminology, and standards.
E N D
SCC Workplan C. Tilton
Press Releases • <boycott> • The IDESG announces the availability of the IDESG knowledge base which provides access to a repository of information regarding online identity use cases, terminology, and standards. • The IDESG SCC announces the publication of its standards adoption policy. This policy identifies the criteria to be used for the IDESG to adopt a standard as part of its identity ecosystem framework.
Workplan Most internal Most shared
Redundancies • All SCC work items are intended to serve the IDESG as a whole and as such are based on collaboration with other groups. • We WANT other groups to contribute to our work items – • Use cases • Terms & definitions • Standards
Gap • Lead/champion for IDE functional elements/models • SCC is only a contributor here • Other “related” work • IDEF model • TF/Accred models
Gaps (with IDEF model) • Model includes: • Privacy standards • Security standards • “Technical specifications” • We are focusing on technical standards, including those for: • Interoperability
Key attributes • Business model • Liability • User experience • C&A • User-centric • Opt-out • Federation • No passwords • Entice RPs to join • Role-based identity SCC - Supporting Role Only
What we did today & yesterday • Yesterday: SCC Orientation • Today: Workplan, collaboration process • Charter • Tonight: Joint meeting with Security & Financial committees on: • Use cases • More tomorrow • Taxonomy • Terminology recommendations • Top 15 terms – may be related to functional elements • Functional models
Collaboration • What does the collaboration process look like? • Models > inputs solicited • How do we motivate participation and contribution? • “Silo’d” nature of our work groups • Liaisons not working • Chairs group/list not enough • Wiki & discussion forum good, but also may not be sufficient • Push vs pull > notifications • Workshops • Outreach to stakeholder groups • Marketing/advertising • <use of Comms & Outreach committee>
Assign Lead Group Start Inventory Compilation IDEF Work Product • Vocabulary/glossary • Use cases • Adopted standards Draft work product Identify Sources Review & comment Create Format/Template Set Criteria Revise • Solicit Contributions • IDESG groups • IDESG plenary • External Receive needs & requirements Draft for ballot • Identify candidate content • From inventory • Other contributed MC approval Maintain Repository IDESG ballot • e.g., Wiki Compile content Publication IDESG Assess content Subsequent Revision(s) Collaboration (throughout)
Potential Collaboration Process Concept -> draft outline Steward ROW Wiki Existing Sources Advertise Initial/sample content Jumpstart Moderate (format, apply criteria) Contributions Expanded content Review & Comment Refined content Snapshot for Formalization (adoption) From stakeholders (including groups, workshops)
How to revise and update: Option Two, collaborate and moderate Contributors Moderators Wiki Moderators Contributors Moderators Contributors Store content in relatively free-form manner, Supports comments Moderate for quality of format, accuracy of information, etc. Contribute content and discuss other contributions according to their area of expertise
Sketch of a wiki based knowledge base containing Terms, Use Cases, Standards, etc. All of those are Concepts that can be expressed on a wiki page, then each group is a wiki Category.