Requirements for standards and best practices
An INCF-endorsed standard or best practice:
- Is open and FAIR. Must have open documentation and a permissive license (everyone can read the documentation to implement the standard). Follows the principle of open standards.
- Is citable: Must have a clear way of being cited and has DOI on documents when relevant. How to acknowledge the working group is made clear.
- When relevant has toolings and implementation:
- Must have reference implementation. Example: a standard of an API should have some implementation.
- Has some associated software tools (when relevant) Example: the BIDS standard has a validator, dicom2bids tools, etc.
- Tools and implementation must have open source licenses when these tools are not associated with a specific non-open source platform.
- Must have a governing model document for maintenance and updates compatible with the INCF project governing model document and the open standards principles
- Has a clear description on how and who is maintaining the standard currently. Is actively supported by the community.
- Has community tools for feedback and support (email list, site, etc)
- Has evidence that if adopted, it will be maintained and supported. Some criteria might include:
- Support by an organization rather than an individual graduate student or researcher
- Hosted on community infrastructure, e.g., Github
- Must be adopted and used (if not yet, falls in the category of draft standard/best practice).
- Must have specific and concrete signs of adoption which include:
- A significant number of users outside the group which has developed the standard
- Research products (articles, databases, infrastructures) that have adopted the standard
- Backup by parent organizations (RDA, Elixir, journals, funding bodies, etc)