Web Experience Management Interoperability TC F2F Meeting in April 2012 Photo by Kevin Clausse - http://flic.kr/p/6M1xa2

Photo by Patricia Drury - http://flic.kr/p/7V5e3g

Introduction: Who is who… and why are you here? Agenda Hashtag? #wemi Introduction: Who is who… and why are you here? Discussions with Gartner (Mick) & Forrester (Steven) Road to WEMI 1.0

Goal of the TC define a simple domain model for WEM and an abstract feature set to be commonly implemented by WCM/WEM System It is a goal to explicitly use existing systems as a point of reference but be open towards extensions that may be generally useful specify a default binding as a lightweight, resource- oriented, HTTP-based protocol http://www.oasis-open.org/committees/wemi/charter.php

Use Cases 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

Roadmap to WEMI V1.0 Spec Stage Expected Date Note Committee Spec Draft July 2012 Committee Public Review Draft min 30days Committee Spec Candidate OASIS Standard September 2012 min 60days review OASIS Standard Nov/Dec 2012 Reference Implementation and Test Suite Approved Errata 6

Break Photo by Wilsonious - http://flic.kr/p/dEa9C

From Thomas Lund Sigdestad <tsi@enonic.com>

Use Cases Display and Mashup Content from a WCM Sitemap(s) to discover content Query content e.g. give me all articles from last months Getting the content a rendition & raw data Providing a context Index Content and Metadata Export all Content / Migration

Page Forms Context Part Sitemap Widget Image Reference Text Tags Terms Page Forms Context Part Sitemap Widget Image Reference Text Tags Article Activity User Folder Content Rendition Layout Template Region

sitemap – list of pages with optional hierarchy information Simple Model sitemap – list of pages with optional hierarchy information has pages has section(s) article.json aside.html section ….

Discovery: Resource Catalog /sitemap.json entry type: page, sitemap url: /iphone/features/ Last Modified timestamp /sitemap.html

Discovery: Query Simple query syntax q=

Page / Section Structure %page%.html fully rendered page/section %page%.json LastModified CreatedDate key = value

Context Pass context from consumer to producer Store in Cookie? Do we need to discover context?

Authentication to service HTTP return codes and authentication

Next Task List Teams? Use Case Collection Next Call(s)? Next week – Wednesday (5pm) Task from the meeting Groups? Next F2F – June? / September