ebXML Registry REST SC

SC Page     Send a comment to this SC


The Subcommittee was closed by OASIS TC Administration on 29 October 2019 at the same time as the parent Technical Committee and is no longer active. Archives of its work remain publicly accessible and are linked from this page.

In keeping with the TC Charter focus on developing future versions of the OASIS ebXML Registry Specifications with consideration of related technologies adopted by other forums - the REST sub-committee will develop a specification document to allow implementers to develop a complimentary optional REST-based interface for Registry (the REST support will follow the REST principles). This will not replace the existing interface - but augment the access methods that Registry can support based on the existing RIM and APIs. The SC will first formalize the scope and use cases to be addressed using REST-based interfacing and then develop formal mechanisms and specification details to implement that. This will be tailored to ensure focus on rapidly attainable results. The goal will be to support a limited common set of use cases, rather than an extended set.

One particular use case will be to support development of AJAX-based user interfaces for registry. If REST is determined to be poorly suited to support a particular interface mechanism then that will be simply documented and noted. Later work may then optionally address this when better understanding and practical experience provide better insights.

Deliverables for the SC:

  • Slide Presentation: Includes, Use cases, Requirements, Motivations, Assumptions and Overview of Technical proposal.
  • Detailed Technical specification on REST-based Interfacing which the sub-committee will deliver for review by the Registry TC.
  • Paper on "REST-based interfacing using the ebXML Registry". Venue for submission of paper will be determined later.

Schedule for the SC:

  • Deliverables due within 6 months from start of the SC effort.

  • Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.