This page to be located at https://rd-alliance.org/groups/process-and-criteria-rda-recommendations.html
Criteria for RDA Recommendations
This document describes the criteria for RDA Recommendations, a specific type of Output from a Working or Interest Group. For an overview of RDA Working Group Goals and Outcomes, see https://www.rd-alliance.org/groups/goals-and-outcomes.html; for a description of RDA outputs , see the RDA Outputs and Intellectual Property Policy.
RDA Recommendations are typically documents, but they may include more complex files such as schemas, ontologies, and data models. Recommendations must:
- Advance the mission of RDA.
- Be approved according to the procedure outlined in the RDA Working Group Goals and Outputs page.
- Have demonstrated application or users and supportive community consensus.
- Reference appropriate other documents and community practice.
- Be available under the default RDA Creative Commons Attribution Only 4.0 license (CC-BY) or the Creative Commons CC0 1.0 Public Domain Waiver (CC0).
- RDA seeks for Recommendations to be publicly useable and useful with reasonable credit going to RDA and its members. Given the potential diversity of Recommendations, alternative open licenses or waivers may be more appropriate if approved by the TAB and Council. The proposing Group must include a detailed justification for using a license or waiver other than the default that shows how the alternative better advances the mission, principles, or goals of RDA.
- Have a controlled versioning method and be versioned.
- Provide sufficient citation information within the Recommendation, including:
- Enough information to register a Persistent Identifier [With CrossRef, DataCite, other?].
- Appropriate, defined authorship. While Groups can be listed as authors, individuals should be specified as appropriate. All members of a Group should be given the opportunity to be listed as supporting or endorsing authors.
- Research Data Alliance listed as "publisher" or equivalent.
- Require ongoing maintenance and versioning, i.e. they are not static or must be periodically reviewed or generally need to be kept current to be persistently useful.
- Be simple in form and be readily preserved and shared. The intent of this criterion is to allow Recommendations more complex or esoteric than basic documents but not to require significant user support or major attention to long-term operational considerations like changes in computer operating systems, configurations, libraries, etc.
- Include a short maintenance and retirement plan that identifies:
- who will ensure the Recommendation is kept current. A demonstrated community interested in the Recommendation is especially desirable. Possibilities for a maintenance group could include an RDA IG, an affiliate organisation, an ad hoc group that (re)convenes on a periodic schedule (e.g. annually), a special WG, etc.
- how the Recommendation would be superseded or retired, if appropriate.
- suggestions on the status of the Recommendation if RDA ceases to exist.