This guide explains the questions and process used to assess an open standard proposal before it is sent to the Open Standards Board.
All open standards that are considered for adoption across government must be assessed by the GDS open standards team and the challenge owner before they can be formally proposed. Read more about the open standards selection process.
Challenge owner responsibilities
Together with the Open Standards team, you must:
- use the list of core assessment questions below to assess the proposed standard(s)
- answer the questions with yes or no, and explain your answer
Open Standards team responsibilities
The Open Standards team will:
- provide support to you and access to the online forms you will need to fill in
- publish the agreed assessment criteria for the proposal
- collect and publish questions suggested by you as a resource for other Challenge Owners
Assessment questions for the challenge owner
- Does it address and aid interoperability between public administrations?
- Does it address and aid the development of digital services in government?
- Are the functional and non-functional requirements for the use and implementation of the specification clearly defined?
- Is it possible to implement the specification across different domains?
- Is it largely independent from products of single providers, either open source or proprietary?
- Is it largely independent from specific platforms?
- Has the standard been written so that it can be delivered or used with more than one technology (for example XML and JSON)?
- Has the specification been sufficiently developed and existed long enough to overcome most of its initial problems?
- Are there existing or planned mechanisms to assess its conformity and implementation - for example conformity tests, certifications and plugfests?
- Does it have sufficient detail, consistency and completeness for the use and development of products?
Implementation of the formal specification
- Does it provide current implementation guidelines and documentation for the implementation of products?
- Does it provide a reference (or open source) implementation?
- Does it address backwards compatibility with previous versions?
- Are the underlying technologies for implementing it proven, stable and clearly defined?
- Is information on the terms and policies for the establishment and operation of the standardisation organisation publicly available?
- Is participation in the creation process of the formal specification open to all relevant stakeholders (such as organisations, companies or individuals)?
- Is information on the standardisation process publicly available?
- Is information on the decision-making process for approving formal specifications is publicly available?
- Are the formal specifications approved in a decision-making process which aims at reaching consensus?
- Are the formal specifications reviewed using a formal review process with all relevant external stakeholders (such as public consultation)?
- Can all relevant stakeholders formally appeal or raise objections to the development and approval of formal specifications?
- Is relevant documentation of the development and approval process of formal specifications publicly available (such as preliminary results and committee meeting notes)?
Access to the formal specification
- Is the documentation publicly available for implementation and use at zero or low cost?
- Is the documentation of the intellectual property rights publicly available (is there a clear and complete set of licence terms)?
- Is it licensed on a royalty-free basis?
Versatility/flexibility of the proposed standard
- Has the formal specification been used for different implementations by different vendors/suppliers?
- Has the formal specification been used in different industries, business sectors or functions?
- Has interoperability been demonstrated across different implementations by different vendors/suppliers?
End user effect of the formal specification
- Do the products that implement it have a significant market share of adoption?
- Do the products that implement it target a broad spectrum of end-uses?
- Does it have strong support from different interest groups?
- Is there evidence that the adoption of it supports improving efficiency and effectiveness of organisational process?
- Is there evidence that the adoption of it makes it easier to migrate between different solutions from different providers?
- Is there evidence that the adoption of it positively impacts the environment?
- Is there evidence that the adoption of it positively impacts financial costs?
- Is there evidence that the adoption of it positively impacts security?
- Is there evidence that the adoption of it can be implemented alongside enterprise security technologies?
- Is there evidence that the adoption of it positively impacts privacy?
- Is it largely compatible with related (not alternative) formal specifications in the same area of application?
- Is there evidence that the adoption of it positively impacts accessibility and inclusion?
Maintenance of the formal specification
- Does it have a defined maintenance organisation?
- Does the maintenance organisation provide sufficient finance and resource to control short-to-medium-term threats?
- Does the maintenance organisation have a public statement on intention to transfer responsibility for maintenance of it, if the organisation were no longer able to continue?
- Does it have a defined maintenance and support process?
- Does it have a defined policy for version management?
Related European standards
- Is this an existing European standard or an identified technical specification in Europe? (Note: CEN, CENELEC or ETSI are the European standards bodies. Technical specifications provided by organisations other than CEN, CENELEC or ETSI can be under consideration to become a European standard or an identified technical specification in Europe.)
- Does this specification or standard cover an area different from those already identified or currently under consideration as an identified European standard or specification?
Open Standards evaluation
Once you have completed the core assessment questions and published them on GitHub, the open standards community and the Open Standards Board will evaluate your proposal based on your answers to the core assessment and evaluation questions.
- What user needs does the standards profile meet?
- Which organisations or functional areas should refer to this standard’s profile?
- Describe which stakeholder groups and outcomes the standard profile meets and how.
- Why is this the most effective course of action? What is the scope?
- A brief summary of the assessment: what are the main pros and cons relating to applicability, maturity, openness, intellectual property rights, market support, potential and coherence discovered during the assessment?
- Alternatives considered: what other proposals and standards were considered and why are these not being recommended?
- What effect would implementation of this standards profile have on service delivery?
- How does this approach deal with any backwards compatibility issues?
- What might be on the horizon (for example are there any threats relating to this approach or the associated standards)?
- What are the benefits or opportunities relating to this approach or the associated standards (economic, social and environmental)?
- When will implementation begin and when is it likely that it will be completed?
- Are there any non-technical barriers that remain which will need to be addressed before successful implementation could be achieved (such as legal, organisational)?
- What trials have been undertaken? Describe any reference implementations that have been built or tested, and pilot projects or any plugfests.
- List the people involved in the development of the proposal and the assessment of the standards.
- List the main open standards community members involved in the evaluation of this standard’s profile.
- What date should this standards profile be reviewed? Take into account any anticipated changes in technology or standards.
- Was it necessary to notify the European Commission under Directive 2015/1535/EU (which replaced Directive 98/34/EC on 7 October 2015)? If so, what stage has been reached? Is the outcome known?