Potential solutions


 * Learn from incubation models - moving/supporting community efforts to a state where they might engage with full-blown standards ratification. For example the Apache incubator.
 * Support adoption, community engagement & advocacy throughout the whole lifecycle from incubation to adoption and beyond. Identify criteria for candidacy for incubation and moving from one to the other.
 * Match agility to the goal/stage of the spec process (e.g. XCRI)
 * Ensure resources are available throughout the whole lifecycle
 * Document success and failure stories to identify success and failure criteria
 * raise awareness, and be transparent, about the way we want to move through this multi-dimensional space.
 * Increase effective coordination between the different bodies
 * Improve the understanding of policymakers of the diversity of standards and specifications
 * Manage the expectations of policymakers
 * Identify solutions for the patent and ownership issues with specifications
 * Many bodies should more effectively disseminate within their existing "rules"

Not Agreed

 * Build shared strategies and concepts
 * Publication is important - see lessons learned from Open Web Standards. Needs to be segmented according to audience - marketing
 * Increase participation of all groups, build trust
 * Informal communication (such as these meetings)
 * There should be an attempt to coordinate between the different bodies.
 * Harmonising legal issues (IPR etc.) / OWF licensing frameworks e.g. apache etc.
 * Identify and adopt common license frameworks
 * Russian Oligarch!
 * In the next 10 years we should place more emphasis on development of specifications than on formalisation as standards
 * We need criteria for when something is mature enough (or when it is acceptable) to take a spec forward to standardisation.