CharterWeb 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 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. OASIS Web Experience Management Interoperability TCWEMITC_781a44e4-134d-11e2-b20b-ae6f97258a28Cedric Hueslerchuesler@adobe.com, Chair Frank van Lankveltf.vanlankvelt@onehippo.com, Secretary Peeter Piegazeppiegaze@adobe.com, SecretaryWeb Content Management VendorsThe 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.Architects from WEM/WCM VendorsThe 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. Architects from WEM/WCM ImplementersArchitects from WEM Systems User OrganizationsDefining a simple domain model for delivering aggregated content into a total Web Experience_781a4700-134d-11e2-b20b-ae6f97258a28To define a simple domain model for WEM and an abstract feature set to be commonly implemented by WCM/WEM Systems._781a47dc-134d-11e2-b20b-ae6f97258a28Use CasesTarget a focused set of use cases_781a487c-134d-11e2-b20b-ae6f97258a281For the initial set of deliverables, the TC will target a very focused set of use cases. 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 Display & MashupDisplay and Mashup Content from a WCM _781a4926-134d-11e2-b20b-ae6f97258a281.1IndexingIndex Content and Metadata _781a49da-134d-11e2-b20b-ae6f97258a281.2Export / MigrationExport all Content / Migration_781a4a8e-134d-11e2-b20b-ae6f97258a281.3Tasks[Undertake the following tasks]_781a4b4c-134d-11e2-b20b-ae6f97258a282PrinciplesArticulate the principles of WEMI through formal specifications _781a4c0a-134d-11e2-b20b-ae6f97258a282.1RelationshipsAssess the relationship of WEMI to related standards and industry efforts including (but not limited to) CMIS, WebDAV, and JCR (JSR-170, JSR-283)_781a4cbe-134d-11e2-b20b-ae6f97258a282.2DefinitionsDefine appropriate specifications for WEMI_781a4d7c-134d-11e2-b20b-ae6f97258a282.3Model, Features & OperationsAbstract domain model, feature set, and operations _781a4e3a-134d-11e2-b20b-ae6f97258a282.3.1HTTP BindingsLightweight, resource-oriented HTTP bindings_781a4f0c-134d-11e2-b20b-ae6f97258a282.3.2Implementation & ValidationProduce a reference implementation and test suite that validate the specifications._781a5074-134d-11e2-b20b-ae6f97258a283The 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. _781a5150-134d-11e2-b20b-ae6f97258a282012-10-10https://www.oasis-open.org/committees/wemi/charter.phpOwenAmburOwen.Ambur@verizon.net