Case Study Guidelines
To promote the adoption of OASIS Standards and specifications, the Consortium publishes case studies that document meaningful implementation experiences. OASIS case studies are a) authored by OASIS staff or staff-authorized contractors and/or b) initiated, reviewed, and approved as a deliverable of one or more OASIS Committees.
OASIS case studies must conform to the following guidelines for content, approval, publication, acknowledgements, and funding.
- OASIS case studies are objective in nature. They are designed to provide useful information on how an organization has benefited from implementing one or more OASIS Standards or specifications. Case studies may offer factual information on products used without overtly endorsing or promoting those products.
- An executive summary, description of the business problem, and benefits produced by the use of the OASIS Standard or specification must be included as outlined in the OASIS case study template.
- Links to additional information, such as user and supplier web sites and product data sites, may be provided as appropriate.
- Content should be developed with the permission of and input from all major parties involved including the implementing organization and any vendor companies mentioned.
- Content must be approved by OASIS Communications staff. If the case study is a deliverable of one or more OASIS Committees, the members of that Committee must also review and formally approve the content.
- OASIS case studies should be formated using the OASIS case study template.
- Case studies will be published on the OASIS web site and made publicly available for viewing, downloading, and distribution.
- Links to published case studies will be provided from the appropriate OASIS Committee’s public homepage. Members and other parties are encouraged to provide links to OASIS case studies from their web sites and to print and distribute case studies.
- Availability of new case studies will be announced in OASIS News.
Acknowledgements and Funding
- Writing and production costs may be funded or other resources provided by one or more OASIS Foundational Sponsor or Sponsor-level members.
- Those who contribute technically and/or financially to an OASIS case study will be appropriately acknowledged for their support, as defined in the OASIS case study template.
Suggestions for OASIS Case Studies
All interested parties are encouraged to contact firstname.lastname@example.org to recommend implementations of OASIS Standards or specifications that would serve as useful case study subject material.
Case Studies Published by Third Parties
The guidelines above apply to official OASIS-branded case studies only. The Consortium appreciates that organizations may wish to create and brand their own case studies on implementations of OASIS work, and it encourages this practice.
Authors of third-party case studies may promote their work to the OASIS community by contacting email@example.com. OASIS may provide links from XML.org and other appropriate web pages to third-party case studies. OASIS organizational members may also publicize their case studies using the OASIS announce mail list.
Suggestions that improve upon these guidelines are welcomed. Please send comments to firstname.lastname@example.org.