RDA Outputs are the technical and social infrastructure solutions developed by RDA Working Groups or Interest Groups that enable data sharing, exchange, and interoperability. These outputs have an important impact in two areas: solving problems, and incorporation and/or adoption in infrastructure environments by individuals, projects and organisations. As an organisation, RDA's goal is to expand awareness and adoption of these Outputs, and hence their impact, within all regions of the world.
RDA Outputs have the following classifications:
- RDA Recommendations
- Supporting Outputs
- Other Outputs
RDA Recommendations are the official, endorsed results of RDA and considered our “flagship” Outputs. They have undergone formal phases of discussion, comment, and decision-making, and can be compared to “specifications” or “standards” created and endorsed by other organisations. They are documents in a very broad sense and may include specifications, taxonomies or ontologies, workflows, schemas, data models, etc. To be endorsed, they met specific criteria, including being made publicly available and usable. The Recommendations endorsement process is described on the Working Group Outputs page.
View RDA Recommendations>>
Supporting Outputs are useful solutions from our RDA Working and Interest Groups, but may not be as clearly adoptable by organisations as our RDA Recommendations. They have undergone a community review, and may include RDA-branded guidelines, brochures and white papers that serve to educate and inform, rather than directly solve a specific data sharing challenge. If you have something you would like to be considered as a Supporting Output, please contact firstname.lastname@example.org.
“Other” Outputs are used to describe resources requested by a Working Group or Interest Group, to be published on the RDA website, but have received no level of endorsement. They could include workshop reports, published articles, survey results, etc. If you have something you would like to be posted as an Other Output, please contact email@example.com.
v. September 2015