OASIS Web Experience Management Interoperability (WEMI) Technical Committee

The official charter for this Technical Committee is provided below. (For additional information, see the Call for Participation that was issued when this TC was formed.)

  1. Name of the TC

    OASIS Web Experience Management Interoperability (WEMI) Technical Committee

  2. Statement of Purpose

    Web Experience Management (WEM) is a redefinition or evolution of Web Content Management (WCM). Where WCM provides the foundation for collaboration by offering users the ability to manage content, WEM emphasizes the importance of the delivery of the aggregated content into a total Web Experience.

    The purpose of the Web Experience Management Interoperability (WEMI) TC will be to define a simple domain model for WEM and an abstract feature set to be commonly implemented by WCM/WEM Systems. The TC shall also work in a forward looking manner and identify features that are useful but are not available in existing systems. It is a goal to explicitly use existing systems as a point of reference but be open towards extensions that may be generally useful.

    Beyond the domain model and the features set, the TC will also specify a default binding as a lightweight, resource-oriented, HTTP-based protocol that will be focused on ease of consumption from today's web browsers (and web browser-like systems) as well as serversided integration technologies. Based on the evolution of WEM into the mobile space, the WEMI TC will include a particular focus on small processing and network overhead.

  3. Scope of Work

    The TC will accept input from various vendors' existing interfaces and domain models and other contributions for consideration without any prejudice or restrictions. These inputs will be evaluated based on technical merit in so far as they conform to this charter.

    For the initial set of deliverables, the TC will target a very focused set of use cases:

    • Display and Mashup Content from a WCM
    • Index Content and Metadata
    • Export all Content / Migration

    The following use cases are out-of-scope for the initial set of deliverables:

    • Entitlement and Access Control
    • Versioning and Records Management
    • Data Ingestion / Write operations

    Also, this TC will engage in maintenance of the specifications it produces.

    The tasks of the TC include:

    • To articulate the principles of WEMI through formal specifications
    • To assess the relationship of WEMI to related standards and industry efforts including (but not limited to) CMIS, WebDAV, and JCR (JSR-170, JSR-283)
    • To define appropriate specifications for WEMI:
      • Abstract domain model, feature set, and operations
      • Lightweight, resource-oriented HTTP bindings

    The TC shall also support the effort of producing a reference implementation and test suite that validate the specifications, both deliverables will be implemented as community open source projects.


    Once the TC has completed work on a deliverable and it has become an OASIS Standard, the TC will enter "maintenance mode" for the deliverable.

    The purpose of maintenance mode is to provide minor revisions to previously adopted deliverables to clarify ambiguities, inconsistencies, and obvious errors. Maintenance mode is not intended to enhance a deliverable or extend its functionality.

    The TC will collect issues raised against the deliverables and periodically process those issues. Issues that request or require new or enhanced functionality shall be marked as enhancement requests and set aside. Issues that result in the clarification or correction of the deliverables shall be processed. The TC shall maintain a list of these adopted clarifications and shall new minor revision of the deliverables including these updates. After the first set of deliverables has been completed, the TC will continue to work on the next version of the specification. The next version may address new use cases or refine existing ones by extending the domain model and expanding on the feature set.

  4. List of Deliverables

    The initial set of deliverables and projected duration:

    • WEMI Abstract Domain model and feature set specification (September 2012)
    • WEMI resource oriented HTTP binding specification (September 2012)
  5. IPR Mode

    The IP mode for the TC will be RF on Limited Terms

  6. Audience for the TC

    The primary audience for the final output of this TC includes architects from WEM/WCM vendors and implementers, as well as system architects from organizations that use WEM systems.

  7. Language

    The language in which the TC shall conduct business: English