Organize or Participate in an OASIS Interop


Step one...Ask your TC chair if the group is currently evaluating holding an Interop demonstration and/or showcase.

If the answer is no, suggest that the TC consider holding one.  As a reminder -

Interop Demos show interoperability between members’ products, all of which adhere to a set of technical requirements defined by the TC and/or Interop Team. Although Interop Demos require the highest level of planning and coordination among participating members, they offer a greater opportunity for identifying potential implementation and compatibility issues.

Interop Showcases provide a common venue for demonstrating members’ products that support an OASIS Standard or Committee Specification. Because full compliance with a defined demonstration scenario is not required, an Interop Showcase is easier to organize and may be more readily accessible to a broader range of members.

Interop Plugfests offer the opportunity to determine product compliance and interoperability during a public event. Participation in Interop Plugfests is open to both members and non-members of OASIS.

To compare the features of Interop Demos, Showcases, and Plugfests, see Interop Matrix.
> Review OASIS Interop Demonstration Policy

Step two...Organizing an OASIS Interop

  • Get buy-in from the TC. OASIS Interops usually involve one or more TCs and at least three to eight member organizations. The more participants involved, the greater the impact. The decision to host an Interop should be made by the TC, and all TC members should have the option to participate.

  • Determine a venue. Many conferences have long lead times, so it’s never too early to start planning—at least four to six months in advance is ideal, more lead time is advised. If the TC does not have a specific conference in mind, OASIS Staff can help identify appropriate options. TC members may want to get recommendations from their organization’s marketing departments on conferences that offer the best exposure. OASIS Staff will contact conference organizers, confirm availability, negotiate terms, and manage the financial and logistical details associated with the venue.

  • Identify at least three organizations interested in participating.  OASIS Staff will help recruit additional Interop Participants as the planning begins. 
    A participation fee based on projected costs (e.g., booth space, equipment rental, connectivity needs, etc.) and the number of participants will be determined by OASIS Staff.  A reservation form will be provided for each Interop Member.

  • Select an Interop Lead. The Interop Lead will work with OASIS Staff to ensure the event is planned and executed in a fair, vendor-neutral, professional manner. The Interop Lead usually (but not always) represents one of the organizations participating in the demo.  This Interop Lead may be appointed by the TC or selected by the Interop Participants.

  • Discuss requirements. Determine what the Interop will showcase. Consider how best to educate the audience on the standard and its functionality. If appropriate, map out a scenario that will be familiar to the specific attendee base. Decide whether any conformance and/or interoperability criteria will apply or be tested as part of the event. Involve all Interop Participating Organizations and incorporate all associated products. Anticipate any technical requirements (audio/visual equipment, internet connections, etc.). The Interop Lead should provide all these needs and requirements to Staff for review and approval prior to execution.

  • Collaborate. Subscribe at least one representative per Participating Organization to the Interop planning email list, which is created by OASIS Staff. Decide on a schedule of conference calls. Discuss ways the Participating Organizations and TC can provide support throughout the planning process. 

  • Promote. Post information on the Interop via your social and/or corporate networks. 

Step three...Submit an Interop Request Form to OASIS

Ideas for OASIS Interops should be submitted to as early as possible in the planning stage. Long lead times (6 months to a year) are recommended and often necessary to secure space at major conferences.  Requests must be received by OASIS Staff at least 60 days prior to the scheduled Interop  with the final list of confirmed participants received by no later than 30 days prior to the scheduled Interop.  Requests should include as much of the following information as possible:

  • Name of sponsoring OASIS Technical Committee(s)
  • OASIS Standard(s) or OASIS Committee Draft(s) to be demonstrated (including version #)
  • Interop Lead (name, affiliation, contact info)
  • Brief Interop Description (75 words)
  • Full Interop Abstract (500-1000 words)
  • Group Technical Requirements, i.e. audio visual, internet connectivity, routers, computer hardware or other (Note: These technical requirements are for the group and not individual participants. Each Participant will be responsible for bringing their own equipment used in their individual workstation.)
  • Amount of Time Needed for Demonstration
  • Proposed Date (if available)
  • Proposed Venue (if identified)
  • List of Interested Participants

Questions during the request phase may be directed to OASIS Staff.